I've tried the following code:

    simplex.goto("github.com/mitchellh")
    num_contribs = simplex.extract_text("blabla")
    print(num_contribs)

It outputs all texts from the page. Is it expected? Maybe it should fail indicating element could not be found?

extract_text returns all the lines of text it finds within an element. Looks like for your case it selected a majority of the page from the description, so it's returning most of the text on the page.

We currently don't return failure cases (just closest match) -- but good suggestion! We'll fine tune on some negative cases and see if we can catch them

Looks interesting. I know about the similar project - https://zerostep.com. Is it basically the same?

Hi HN! I've developed an approach that adds a button to the Playwright HTML report, enabling you to fix failing tests using AI. It works well on the Playwright site tests, but I'm curious how it will behave on other projects. Would appreciate your feedback.

Unfortunately not. GitHub official newsletter only contains trending repositories across all programming languages. So you can't focus on particular language.

> But seems that the issues have been locked and not updated since November without explanation as to why.

GitHub shows issue creation date, not last update.

Thanks for posting this and for the comments!

Before creating this repo I've researched existing solutions and described the comparison here: https://medium.freecodecamp.org/five-ways-of-tracking-trends...

It seems you've looked at the issue open date. The updates to Swift are coming daily: https://github.com/vitalets/github-trending-repos/issues/36#...

I agree. We should consider several criterias. The speed becomes more important for huge number of tests when execution time starts to annoy developers.