Trending repositories

Ranked by Attention Score: stars gained over the last 180 complete days

Period

Sort order

Tag

Filters

Apply

Filters

Primary language

License

Total stars

Last push

Created

Archived

Clear all filters

6 repositories by Attention Score · May 8, 2026 – Nov 3, 2026 (UTC)

Tag: End-to-end testing

1.microsoft / playwright

Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.

playwright
testing
automation
webkit
firefox
e2e-testing
+9 more

TypeScript APACHE-2.099K total6.8K forks

+11,599 stars

from 87,617 · score 9.36

2.web-infra-dev / midscene

See interfaces like a human. E2E testing in natural language.

testing
browser-use
computer-use
gpt-operator
javascript
phone-use
+2 more

TypeScript MIT15K total1.2K forks

+2,671 stars

from 12,820 · score 7.89

3.mobile-dev-inc / Maestro

Painless E2E Automation for Mobile and Web

android
ios
blackbox-testing
ui-automation

Kotlin APACHE-2.016K total1K forks

+2,471 stars

from 13,833 · score 7.81

4.cypress-io / cypress

Fast, easy and reliable testing for anything that runs in a browser.

cypress
end-to-end-testing
angular-testing-library
component-testing
cypress-cloud
cypress-schematic
+7 more

TypeScript MIT51K total3.6K forks

+1,716 stars

from 49,301 · score 7.45

5.appium / appium

Cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol

appium
webdriver
android
ios
windows
automation
+2 more

TypeScript APACHE-2.022K total6.3K forks

+817 stars

from 21,361 · score 6.71

6.seleniumbase / SeleniumBase

📊 APIs for Web Scraping, Browser Automation, and E2E Testing. CDP Mode & Stealthy Playwright Mode bypass bot-detection/CAPTCHAs.

python
selenium-python
e2e-testing
seleniumbase
web-automation
pytest
+10 more

Python MIT13K total1.6K forks

+707 stars

from 12,516 · score 6.56

Order: Attention Score

Most net stars gained in the window first. The score only puts this gain on a log scale, so the order is the order of the gain.

How the ranking works

Ranked by stars gained in the window. The score is the natural log of one plus that gain, so a repository's rank is exactly its star gain's rank.

score = log1p(net stars gained in the trailing T complete UTC days)

A repository is ranked only when its Star History covers every day of the window and its latest Observation is not missing.

The longest window is 180 days. Star History from the Repository Host goes back at most 180 days before the first daily record that AwesomeRepos made for the repository. A longer window needs more of these daily records first. A repository younger than the window does not rank in it.

The filters select from the same eligible repositories. A repository matches the topics when it has any of them. Total stars is the count now. Last push and creation on the Repository Host count back from the start of today (UTC). The counts beside the languages, licenses, and topics include all ranked repositories in the window. A Tag holds the repositories that have it. See Tags.

Repositories enter the index from the starting dataset of the index, or by gaining stars faster than the published admission threshold, whatever their size. A repository stays in the index after it enters. Thus an archived repository can still rank.

Browse the Repository Index