Current Cucumber Tests in zmsautomation
This page is generated automatically from zmsautomation/src/test/resources/features. When a .feature file is added, changed, or removed, this documentation is updated automatically.
Loading last scheduled run…
Scenario counts
| Module | Total | booking | customer-call | dldb-special-cases | rebooking | Uncategorized |
|---|---|---|---|---|---|---|
| zmsapi | 10 | 6 | 1 | – | – | 3 |
| zmscitizenapi | 25 | 9 | – | 13 | 3 | – |
| Total | 35 | 15 | 1 | 13 | 3 | 3 |
| Module | Total | booking | configuration | customer-call | customers | dldb-special-cases | opening-hours | queue | rebooking | services |
|---|---|---|---|---|---|---|---|---|---|---|
| zmsadmin | 21 | 5 | 2 | 4 | – | – | 1 | 8 | 1 | – |
| zmscitizenview | 20 | 4 | – | – | – | 15 | – | – | 1 | – |
| zmsstatistic | 2 | – | – | – | 1 | – | – | – | – | 1 |
| zmsticketprinter | 4 | 4 | – | – | – | – | – | – | – | – |
| Total | 47 | 13 | 2 | 4 | 1 | 15 | 1 | 8 | 2 | 1 |
| REST and UI | Total | booking | configuration | customer-call | customers | dldb-special-cases | opening-hours | queue | rebooking | services | Uncategorized |
|---|---|---|---|---|---|---|---|---|---|---|---|
| REST | 35 | 15 | – | 1 | – | 13 | – | – | 3 | – | 3 |
| UI | 47 | 13 | 2 | 4 | 1 | 15 | 1 | 8 | 2 | 1 | – |
| Total | 82 | 28 | 2 | 5 | 1 | 28 | 1 | 8 | 5 | 1 | 3 |
Click a feature to view its Gherkin. Only one feature is expanded at a time. Pick a branch below the search to load that branch's .feature files, status, and run command. The play icon copies a command to start the test on the selected branch and opens zmsautomation. The title status is green only when every browser in the latest published run passed, and red if any browser failed. Expand a feature to see each browser result.
Recommended Feature Pattern
Use ticket tags consistently. Always include a Jira tag like @ZMSKVR-123 on new scenarios/features.
gherkin
@rest @zmsapi @ZMSKVR-123 @smoke
Feature: Example feature with required ticket tag
Scenario: Example scenario
Given the API is available
When I call the endpoint
Then the response status code should be 200(82) All
(35) REST
(47) UI
(21) zmsadmin
(5) booking
(0) cancel
No scenarios yet for this category — add the first
.featurefile here.
(2) configuration
(4) customer-call
(0) customer-search
No scenarios yet for this category — add the first
.featurefile here.
(0) email-templates
No scenarios yet for this category — add the first
.featurefile here.
(1) opening-hours
(0) overall-calendar
No scenarios yet for this category — add the first
.featurefile here.
(0) permissions
No scenarios yet for this category — add the first
.featurefile here.
(8) queue
(1) rebooking
(0) zmscalldisplay
(0) queue
No scenarios yet for this category — add the first
.featurefile here.
(20) zmscitizenview
(0) appointment-variants
No scenarios yet for this category — add the first
.featurefile here.
(4) booking
(0) callouts
No scenarios yet for this category — add the first
.featurefile here.
(0) cancel
No scenarios yet for this category — add the first
.featurefile here.
(0) citizen-login
No scenarios yet for this category — add the first
.featurefile here.
(15) dldb-special-cases
(1) rebooking
(2) zmsstatistic
(0) capacities
No scenarios yet for this category — add the first
.featurefile here.
(1) customers
(0) permissions
No scenarios yet for this category — add the first
.featurefile here.
(1) services
(0) waiting
No scenarios yet for this category — add the first
.featurefile here.