Easily execute test scripts, record progress in a central location, and export the results of test sessions to share with the team. Know exactly what needs to be tested and how.


Once the owner of the project has added you to their project, you will have access to that project’s test scripts. Simply open the project and click “Start Testing”.


Each test case will now be listed with an empty progress bar. Open whichever test case you’d like to start with. You will see the steps in this test case. Each step has an action and a expected reaction. You may also see setup instructions for begin your testing. Follow those instructions and perform the action in the first step.

  • If the result of the action matches the expected result, mark this step as successful by clicking it. You can also use the more menu for this step (three vertical dots icon) to specifically set this step to a specific status.
  • If the result does not match the expected result, mark this step as failed. You can do this by clicking the step twice (first time set it to success, the second time changes it to failed) or the more menu for that step. Add a note explaining what failed about this step or add extra details for the project’s team. You can add a note using the “Add Note” button or the more menu for the step.


Move on to the next step, repeating the testing process until all the steps in this test case have been executed and set to success or failed. Once all the steps in this test case have been executed, go back to the project and select the next test case. Keep going until all the steps in all the test cases for the project have been executed.


Once you are done testing and adding notes, click “End Testing”. Congratulations, you’ve finished the testing! Now, you can share the results by clicking “Report” to download a simplified report summary of the test results. You can also open any test case and use the “Print/PDF” button to export details on any or all test cases.


  • Each failed step should have a note explaining why it failed.
    • If later steps cannot be executed because an earlier step failed, you don’t need to explain that in a note for each later step as long as the note on the first failed test makes it clear that later steps will not be executable.
  • A successful step can also have notes (using the more menu of that step).
  • Steps can have more than one note.
  • By default the note will be an “error” note. You can change the type of note to “info” or “warning” by clicking the note’s type icon. This can be helpful when you want to note suggestions or reminders.
  • After you’ve finished a testing session, you can always get back to it by going to “History”.