Introduction
Once you have imported your manual tests and associated them with CTP systems, you can collect test status and code coverage data while you perform them and publish it to DTP. The workflow is straightforward:
- Start a manual test session. Sessions are run within environments and will contain all the tests imported into the environment.
- Start a manual test in the session. This activates test data collection. Any number of testers can start manual tests in the session, but each tester can only have one going at a time.
- Perform your manual testing as you normally would for the test you started in step 2. Test data is collected.
- Stop the manual test. CTP will stop collecting data for the test.
- Repeat 2-4 until all the desired manual tests have been completed.
- Stop the session and publish the results to DTP. You can delete the session now as well, if you're done with it.
Starting a Manual Test Session
- Open the Manual Testing module. Your systems and their environments, as defined in the Environment Manager, are listed here alphabetically. Choose the environment for which you want to start a session.
- In the Components table, you will see a list of components in the environment, including the coverage agents they have been configured to use. If a component you will be testing does not have a coverage agent, no coverage data for it will be collected. See Configuring Coverage Agents for Manual Testing for more information about configuring these coverage agents.
- Click Start Session. The Start Session dialog opens.
- Enter a name for the session in the dialog. Note that the session name must be unique within the environment.
- Click Start. A new session will start with your tests.
Starting a Manual Test
When you start a manual test in CTP, test data is collected as you perform the steps in the test. You can publish this data to DTP when you're done testing.
If any of the components in a system under test change to a newer build, you will not be able to start a new manual test in the manual test session. Publish the manual testing results that you have so far and start a new manual testing session for the updated build IDs.
Note: Each tester can only have one manual test running per environment at any time, but multiple users can run tests simultaneously in the same environment if all the coverage agents are running in multi-user mode.
- Open the Manual Testing module. Your systems and their environments, as defined in the Environment Manager, are listed here alphabetically. Navigate to the session with the test you want to start.
- Click the desired test in the Manual Test Results table and click Start Test.
Stopping a Manual Test
Once you're done with your manual testing, stop the test in CTP and indicate the result. Manual tests can only be stopped by the user who started them or by an administrator.
- Open the Manual Testing module. Your systems and their environments, as defined in the Environment Manager, are listed here alphabetically. Navigate to the session with the test you want to stop.
- Click the test in the Manual Test Results table and click Stop Test. The Stop Test dialog opens.
- Click a result (Passed, Failed, or Incomplete) and add notes, if desired. Notes will be published to DTP along with the result and can be helpful, for example, to explain why a test failed or could not be completed.
- You can also abort the test here by clicking Abort Test. This will stop the test without recording a result and delete any coverage data collected. You will be able to restart the test to run it again, if you want.
- Click Finish.
Stopping a Manual Test Session and Publishing the Results to DTP
When you have completed your manual tests, you can stop the session and send the data that was collected to DTP. You will also have the option to use that session as a baseline build for test impact analysis. Be aware that you cannot stop a session that has a manual test running. Stop any test that is running before trying to stop a session.
- Open the Manual Testing module. Your systems and their environments, as defined in the Environment Manager, are listed here alphabetically. Choose the environment that contains the session you want to stop.
- Click Stop Session. The Stop Session dialog opens.
- To publish the session's coverage data to DTP:
- Enable Publish to DTP in the dialog.
- If you want to use this coverage data as a baseline build for test impact analysis, enable Create Baseline and enter a baseline name. See Test Impact Analysis for more information about baseline builds.
You cannot publish the session to DTP after it has been stopped. If you want to publish this data to DTP, it must be done now as part of the process of stopping the session.
- Click Stop.
Deleting a Manual Test Session
When you're done with a session, you might want to delete it. You can only delete sessions that have been stopped.
- Open the Manual Testing module. Your systems and their environments, as defined in the Environment Manager, are listed here alphabetically. Choose the environment that contains the session you want to delete.
- Click Delete Session. A confirmation message appears.
- Click Confirm to delete the session or Cancel to cancel the deletion.