As part of the Test Designer, you can track the progress of your test writing requests through the 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 writers through the product itself. All communication regarding these requests, previously done via email, can now be performed in-app itself.

A test can be in one of the following states:

  • In Progress
  • Blocked
  • Completed

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. Once a test is written, passing, 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 completed 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 writer will flag the test and provide information on the issue they encountered. Users will then receive an email notification with information about the blocker.

The blocker information is also displayed through the app, where you can click into the test view and check the blocker information, read the writer’s notes and proceed to unblock the test writer by clicking the Update Status button.

After clicking the update status option, you will be asked to supply additional information to the test writer that resolves the blocker. After unblocking the test, the writers are notified that they are unblocked in-product itself and will continue writing the test with the new information supplied.

You also find blocked tests by navigating to the Test Builder, then select Blocked from the side panel. This is where you’ll discover which tests are in need of attention. This list will include test that are being written or rewritten by test writers. 

Lastly, there are instances when a blocker (i.e. 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.

Similar to test-level status, when all requests are blocked the user can unblock all tests via the product by clicking the Unblock Run button and providing additional information resolving the blocker. This information is relayed back the test writer so they can resume writing the test cases.

Did this answer your question?