The Manual Testing module provides a real-time view of the execution status of each manual test for a given application in a given environment. In the Manual Testing module, click an Environment in the navigation sidebar to see the latest status for each of its manual tests. Executed tests will be marked as impacted if the code has changed since they were run. This information will also be automatically available in any new manual test session you start, making it easy to see any tests that need to be run again in the session due to application changes.
Each test is accompanied by an icon to indicate its status. The icons used and what they represent are shown in the table below.
| Icon | Description |
|---|---|
| Test is in progress |
| Test impacted by code changes and should be rerun |
| Test failed in a previous session |
| Test failed in the current or most recent session |
| Test incomplete in a previous session |
| Test incomplete in the current or most recent session |
| Test passed in a previous session |
| Test passed in the current or most recent session |
| Test has not been run |
Manual testing session views automatically update as you execute tests or whenever the application changes. If the underlying code that is associated with a previously executed manual test changes, views will automatically update the test status to show that it is impacted and needs retesting. With this summary, you can focus your efforts on manual tests that are impacted or haven't been run yet. If a test is shown as passing and is not impacted, you know that you don't need to run the test again, even if the build has been updated since you ran the test.
When you click an Environment in Manual Testing, you will see a real-time view for it as a whole. The most relevant status icon for each test will be shown beside it, with tests requiring the most attention automatically filtering to the top of the list. Hover your mouse over a status icon for more information about it, including the manual testing session the status is coming from.
Status icons are also used in the system tree on the left of the Manual Testing screen. Generally speaking, when a manual testing session is stopped it adopts the status of the test within it that requires the most attention (if any). For example, when a manual testing session is stopped and most manual tests have passed but one is in a failed state, the manual testing session will be flagged as "failed". Be aware that manual testing sessions that are in progress will always show as "in progress" regardless of the status of any of its tests. These statuses "roll up", so environments take the status of the manual testing session that requires the most attention, versions take the status of the environment that needs the most attention, and so on. In this way, it's easy for you to tell from the system tree, at a glance, when there is something that needs your attention and drill down to find what it is.
