For Squish Test Center 2.0 we have decided to primarily focus our efforts on providing support for manual testing. Since Squish Test Center is all about evaluating the health of your application at any given point in time, we felt that seeing the results of your manual tests right next to the results of your automated UI and unit tests is a natural and logical next step. This also means that all test result analysis features for Squish Test Center that you might already use and be familiar with for your automated tests can now also be applied to your manual tests.
The new manual testing area
We added the new manual testing area right next to the existing result views, so you can easily jump from analyzing results to managing or executing manual tests. Just as for our existing result views the test cycles or batches you are looking at always carry over to the next view to allow for fast transitions.
We have divided the manual testing area into three sections. The
Test Managementsection is for creating and maintaining manual tests. The
Execution Configuration section is for creating and managing a test cycle. The
Execution Overview section is for tracking the state of the current test cycles and as an entry point for the manual test execution.
Creating Manual Tests
We tried to reduce the administration overhead as much as possible to allow for rapid test creation. All information that is required to create manual tests are available on the
Test Management page, so there are no jarring page transitions or hidden setting fields. Creating or maintaining manual tests with Squish Test Center is a very fluent process.
To avoid a cumbersome and frustrating text editing experience we fully focused on plain text editing with markdown support, just like it is available in most modern text editors.
Of course, we also added support for attachments and in-line images, so that your testers have solid references and all available resources they need to complete the manual tests.
Another important tool we added that will ease the creation of new tests are shared steps. You might already know this feature from Squish test automation, where it is very easy to reuse existing automation steps. We adapted this feature for manual tests as well, so that instead of adding new steps you can always also choose to add existing steps. This will be especially useful for setup steps that are required for multiple different manual tests.
Managing a Test Cycle
We also applied the batch concept that is used all throughout Squish Test Center to manual test cycles. This is also what we use as the link between manual and automated tests. Finished manual tests will automatically be added to the result views based on the batch they have been associated with.
Execution Overview page you can get an easy overview of the current test cycle and can quickly see how far along each manual test has progressed. This is also where you can assign or re-assign manual tests based on the availability of testers.
Testers can also use this view to get an overview of all manual tests that are currently assigned to them and to start the manual test execution.
If a test cycle needs to be repeated the
Execution Overview can also be used to look at previous test cycles, and in a few clicks, the test cycle can be fully or partially re-scheduled.
Manual Test Execution
We also carried over the simplicity of the manual test creation to the execution of manual tests. The same text editing tools that are available during the test creation are also available for the test execution.
You can easily add descriptions and attachments to the observed manual test results. So that if a tester encounters a failure they can easily add screenshots or if there is any output that needs to be archived or documented it can simply be added as an attachment.
All test descriptions also become part of your test results, so that when your manual tests change over time the results will always reference the tests at the time of the test execution.
Issue Tracking & Traceability
With Squish Test Center 2.0 we also generally improved our integration with Jira, specifically the creation of issues, where we added a lot more control over the created issues, by adding support for a wide range of custom Jira fields.
For manual testing that means that when testers encounter any bugs they can easily create issues in Jira right within the manual test execution in Squish Test Center. Bugs created will be linked to the manual tests, and will immediately become visible for all other users of the system. Especially for shared steps that means issues found in previous test executions will be visible to other testers as well.
If there are other issue management systems that you would like to see supported please let us know.
Transitioning from other manual testing tools
If you are currently managing your manual tests in Zephyr or Xray then you will be able to transition to Squish Test Centers manual testing in very few configuration steps, thanks to our dedicated API-based import mechanism. There is also an option to import feature files written in the Gherkin language, so if you are documenting your manual tests using gherkin syntax you can make use of this feature to ease the transition. Let us know if you need help migrating from other test management tools.