Testing

These pages are meant to help you move from first setup to reusable test suites without digging through a pile of half-related examples.

Start Here

• Get Started With Regressify Testing for the first local setup, initial installation, and your first working suite.
• Create a test suite for suite structure, grouping scenarios, and suite-level configuration.
• Create a Test Scenario for per-page behavior, actions, and scenario-specific settings.
• Create an action for the click, input, wait, navigation, and element-handling details that usually decide whether a suite feels solid or temperamental.

Build Coverage Faster

• Create a Test Suite for an Entire Site if the site has a sitemap and you want a starter suite without copying URLs one by one.
• Sample: Reuse Scenarios if you want repeated steps to stay maintainable instead of breeding quietly in every file.
• Sample: Form Submission, Sample: File Upload, and Sample: Viewports are good examples when you need a working pattern to copy rather than a blank page and optimism.

Keep The Project Healthy

• Update the Regressify Test Library when your local test tooling has drifted behind.
• Push Local Test Changes to a Remote Repository when the suite is ready to leave your machine and become a shared team asset.
• Change Log when you want to see what changed in the docs and available options without trawling through commit history.

Choose By Task

Use this section by the problem you are solving:

• Use the getting-started guide when you are building a test project from scratch.
• Use the suite, scenario, and action references when a test already exists but needs clearer structure or more reliable behavior.
• Use the sample pages when you need a working example for a common interaction pattern.
• Use the maintenance pages when the library changes, the docs add new capabilities, or the project is ready to be shared with the rest of the team.