Regression testing
The Regression testing step is QA's home for communicating the status of regression testing to the rest of the team. Even for teams without dedicated QA, Runway provides an easy-to-use regression testing script tool that can help to catch feature regressions before they become more costly to fix out in the wild.
Use this dropdown to update the status of regression testing on a specific build. You can choose a status of In progress, Passed, or Failed and specify which build the new status applies to.
Regression testing results can be used to gate submission or release automations, because Runway requires this step to be complete (green) before automatically submitting an update for review to the app stores.
If you've connected a regression testing integration, Runway will surface information about relevant test runs for each release within the Regression testing step.
Runway parses test run names for the presence of a version string (e.g. “2.3.0”) and any keywords specified in your regression testing integration settings in Runway to pull in the right test runs for each release.
Note that the overall Regression testing step status will still rely on the build testing status dropdown, so that you can be explicit about the final testing result.
From the regression testing step, you can put together a script of testing items that need to be checked by QA or other team members. This list lives across releases, so when you add new items to check, they'll show up as testing items on your next release as well.
Testers can mark an item as In progress, Passed, Failed, or Blocked. A tester can also leave an optional comment to provide additional context.
Team members with an assigned role of QA will by default have the ability to update the status of regression testing items, but items can also be assigned specific owners. If a regression item is assigned to a user role, any user with the role can update the status of the item.
Slack reminders can be sent for all incomplete regression items, or individually for specific items to remind owners to update the status of their items.
You can view the list of all existing test items from the initial Summary tab. From here you can Add items to the list or Edit the existing list.
If you click the Edit button, you'll see additional controls to Delete an item, Edit an item's details, or re-order the list. Hit Done when you're finished making changes.
Click the Add button to create a new regression item.
Specify which types of releases (major, minor, point, hotfix) require this test item.
A name for this test item. This appears on the regression testing list itself, as well as notifications related to updates on this item.
Keep this option selected if you want your team to be notified about updates to this testing item during a release cycle. Runway will post in Slack or Teams when this item is marked as Passed, Failed, or Blocked (or was formerly Passed but reverted), as well as who performed the change and when.
Optional - You can add information here that can easily be surfaced in Runway for team members responsible for testing this item. These notes serve as documentation that will be available on every release cycle. Markdown is supported, and there's a built-in viewer.
For example, you might have a state in your app that requires a specific sequence to test. You could leave a note in Additional information that says something like:
Use the coupon code TEST123 to check if the coupon field shows up correctly in the Subtotal table
Optional - Specify users or roles here if a testing item is intended to be evaluated by specific team members or members with particular user roles. This may affect which team members have permission to change this item's status, comment, or to revert a previous status.
Last modified 2mo ago