sel2pw-scan

Offline inventory of a Selenium Java test project, for assessing a migration to Python Playwright.

sel2pw-scan reads your .java files and build files and writes a report: which test framework you use, how many tests, page objects and helper classes you have, and how often your code uses Selenium features that need deliberate work in a migration (fixed sleeps, frames, alerts, JavaScript calls, data providers and so on).

It is a scanner only. It does not convert or change any code, uses no AI model and makes no network calls.

Install

Requires Python 3.10 or newer.

pip install sel2pw-scan

Use

sel2pw-scan path/to/selenium-project --out inventory.md

python -m sel2pw_scan ... works the same way.

What the report contains

The Markdown report (--format md) lists:

• the scanned folder path, detected frameworks (TestNG, JUnit 4, JUnit 5), Selenium version and build files
• counts of Java files, test classes, page objects, base and utility classes, and test methods (including disabled ones)
• how often each of 27 Selenium constructs appears, such as fixed_sleep, frames, alerts, javascript_execution, data_provider and selenium_grid
• every test method as ClassName#method, with its file, line, assertion count and constructs
• every class with its role, parent class and the project classes it depends on

It does not contain test code, locator values, string literals or test data. Read it before sharing, and rename anything you consider sensitive, such as class names.

The JSON report (--format json) adds locator values and annotation attributes, so treat it as internal.

Limits

The scan uses pattern matching, not a full Java parser, so counts can be slightly off for unusual code. It finds tests by annotations such as @Test; Cucumber .feature files and Kotlin or Groovy sources are not read.

License

MIT