Test Suite Organization
Organize and maintain your test suite with ease
Always run the right tests, at the right time, on the right builds. Suites that accommodate every testing need: from basic smoke tests to validation of complex user flows.
View all historical runs and results
Track the evolution of your code over time: monitoring changes in health, problem branches, etc. Easily identify parts of your app that are causing regressions with our comprehensive dashboard view.
Minimize the number of tests required for coverage
Organize tests in folders, chain test components together to reuse what you have already built, and execute runs across multiple device types simultaneously and automatically.
Improve collaboration between QA and Engineering
Waldo provides every user with the same, actionable information. Every existing test case is paired with a comprehensive history of run results and test playback, so your team can have a unified approach resolving bugs and regressions.
Features built by developers for developers
Waldo comes with all the critical features required to support automated testing at scale out of the box.
Take the pain, and wasted time, out of test creation and maintenance
Review and share what you are building in real time
Full video playback of your user flow with network requests
Stop worrying about different results from the same test
Decide when to run each test for efficient results
Share tests with your team through version control
Frequently asked questions
Can’t find the answers you are looking for? Reach out to our team for more help.
What is a test suite?
A test suite is a series or set of test cases you have built to test your mobile application. Typically, these individual tests cover a wide range or use cases from basic to more advanced.
How do you build a test suite?
A test suite is built one test at a time. Build out the test you want to run, outline the dependencies inherent to the test, and continue to iteratively add to your collection over time.
What are the benefits of organizing test suites?
Having an organized testing suite:
- improves visibility into the tests available and any potential gaps
- sets expectations on thorough testing to be done prior to release
- illustrates the relationship between tests when they are grouped together
How do you organize test cases?
How you organize test cases is largely up to you and your team. You can organize based on:
- Test type
- Test function or intent
- Test by feature or app component
- Test complexity
For example: you could organize all the tests regarding functionality in your checkout flow in a single folder.
Or: you could group all your smoke tests together in a single place.