- Test stability - as soon as the Eglish-level description stays true test won't fail
- Collaboration - anyone, including Product Managers, Engineers, Manual Testers, etc. will be able to understand the script and review/contribute to it
- It can be written even before functionality is released
- Minimal maintenance is required. No changes are needed until the specification changes
login
click "Launcher"
enter "Campaigns" into "Search apps"
click "Campaigns" below "Campaigns"
click exactly "New"
generate unique name, then enter into "Campaign Name" and save as "name"
click "Active"
click "Conference"
click "Partners"
click "Planned"
click "Completed"
enter "03/08/2029" into "Start Date"
enter "03/08/2029" into "End Date"
generate from template "1,###", then enter into "Expected Revenue in Campaign" and save as "expected"
generate from template "2,###", then enter into "Budgeted Cost in Campaign" and save as "budgeted"
generate from template "3##", then enter into "Actual Cost in Campaign" and save as "actual"
enter "75" into "Expected Response (%)"
enter "This is a test campaign" into "Description"
click exactly "Save"
check that page contains "created"
click exactly "Details"
check that page contains stored value "name"
check that page contains stored value "expected"
check that page contains stored value "budgeted"
check that page contains stored value "actual"
As you can see, the steps are easy to understand and self-explanatory.
This allows developers to write test cases quickly and efficiently, reducing the time and effort required for testing.
In conclusion, automating testing for Create a Campaign is essential for ensuring the quality and stability of software systems. By using testRigor to write test cases in plain English, anyone can achieve several goals at once, including test stability, collaboration, early testing, and minimal maintenance. If you are interested in trying out testRigor for yourself, you can create a free account and start writing test cases today.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article