https://github.com/bcpeinhardt/schnauzerui
A human readable scripting language for automated UI tests.
https://github.com/bcpeinhardt/schnauzerui
cucumber cucumber-alternative e2e e2e-testing e2e-tests qa qa-automation selenium selenium-alternative selenium-webdriver testing
Last synced: 10 months ago
JSON representation
A human readable scripting language for automated UI tests.
- Host: GitHub
- URL: https://github.com/bcpeinhardt/schnauzerui
- Owner: bcpeinhardt
- License: mit
- Created: 2022-09-26T18:06:07.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-01-30T07:00:13.000Z (over 2 years ago)
- Last Synced: 2025-08-25T06:14:32.937Z (10 months ago)
- Topics: cucumber, cucumber-alternative, e2e, e2e-testing, e2e-tests, qa, qa-automation, selenium, selenium-alternative, selenium-webdriver, testing
- Language: Rust
- Homepage:
- Size: 28.4 MB
- Stars: 12
- Watchers: 2
- Forks: 0
- Open Issues: 9
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# Schnauzer UI
Schnauzer UI is a DSL for performing browser automation.
Rather than focusing on large automated test suites, Schnauzer UI helps
you write small, easy to understand test scripts.
```schnauzer_ui
# Navigate to the site
url "https://youtube.com"
# Search for Cats
locate "Search" and type "cats" and press "Enter"
```
##### When to use Schnauzer UI vs. other options (Selenium, Cypress, Playwright, etc.)
Schnauzer UI is a bad choice if:
- You want to maintain a large automated test suite with reusable components.
- You have a team of full time software engineers dedicated to QA.
- Your QA and Engineering teams are able to collaborate closely to build software
that is easy to E2E test (you have dedicated test environments, a system for test IDs for elements, etc.).
- You want to build your E2E test suites into CI/CD processes and want good tooling around doing it.
Schnauzer UI is a good choice if:
- You want to be able to easily run stand alone scripts and produce a test report.
- You want to quickly draft tests as needed instead of maintaining a large test suite.
- You want a more robust way to codify Acceptance Criteria / Bug Reproduction Steps on your tickets.
- You want to empower non-programmer QA team members to take advantage of automation.
- You want to build some automation into existing manual process.
To get started, check out the [narrative documentation](https://bcpeinhardt.github.io/schnauzerUI/)