As part of the Test Designer, you can track the progress of your test writing requests through test level statuses. This allows for increased visibility into the status for each of your individual test requests and enables communication between our customers and the test authors through the product itself. All communication regarding these requests, previously done via email, can now be performed in-app itself.
As a customer, you can see the status of each test in your request as demonstrated in the image below. A test can be in one of the following states:
- In progress
The status of each test request is updated in real-time and can be seen next to each test request in the writing status column.
As the name suggests, a test is “in progress” when it is in the process of being written by our team of test authors. All tests are run in draft mode during the writing process and are published by the test authors when all steps are written and the test is passing green. Once a test is published and successfully returned, the status changes to “completed”. At this point, the test can be organized into your test suite - you do not have to wait until the other tests are completed to start running your test cases.
The third status of test requests is blocked. A test will be in a “blocked” state when a test writer needs more information and cannot proceed with creating and running the test - this can occur if the credentials are wrong, the environment isn’t working, the test outlines are unclear, or we found a bug!
When a request is blocked, the author will flag the test and provide information on the issue they encountered. The user that started the test writing request will then receive an email notification with information about the blocker.
The blocker information is also relayed back to the customer via the app where the user has the ability to click into the test view and check the blocker information, read the writer’s notes and proceed to unblock the test author by clicking the Update Status button.
After clicking the update status option, the user will be asked to supply additional information to the test author that resolves the blocker. Again, after unblocking the test, the authors are notified that they are unblocked in-product itself and will continue writing the test with the new information supplied.
Lastly, there are instances when a blocker (ie environment is down) may affect the entire batch of test requests, therefore, halting writing progress on all requests. In this situation, the product will display a banner on the batch level indicating progress on all tests has been paused until the blocker is addressed.
Similarly to test level status, when all requests are blocked the user can unblock all tests via the product by clicking the unblock button and supplying additional information resolving the said blocker. This information is relayed back the test authors and they will resume writing the test cases.
To see any unresolved blocked test, navigate to the Blocked Tests tab inside the Test Designer. All blocked tests (whether in real-time or after the fact) will appear inside this filter. From this view, you can click on the blocked test badge of any test to take you to the test view.
At the top of the test view, you can review the blocker context. Adjacent to the blocking comment, there is an option to select unblock.
If you resolve the blocker yourself, Rainforest will remove the blocking designation and allow you to publish your test. If you send to Rainforest, the test will remain in a draft state and you will need to provide any helpful context on the blocker resolution as well as any additional instructions for the test author.
Navigate back to the rewrite tab to track the progress of the test you just resolved.
Test writing status significantly improves the workflow of test writing and helps reduce the time spent communicating back and forth between parties. It is generally available to all clients that have purchased Test Designer.