Ordered Testing
• Ordered tests are a group of tests that can be run together in a synchronous fashion.
- When the tests are performed, the results show up in the Test Manager or Test Results window as one
row.
- Double-clicking the test results of an ordered test show greater detail of each of the included tests.
- Ordered tests cannot contain load tests.
• You choose tests to be gathered into an ordered test in a dialog similar to the dialog used with selecting
tests for the load test.
- Note the “Continue after failure” checkbox, which allows successive tests to proceed even if a prior test
fails.
- Be aware, if you leave it unchecked and one of the tests fails, none of the remaining tests will run.
Generic Testing
• Generic tests are an extension of Team Tester. They allow separate applications or scripts to perform
testing on our application.
- This allows for a more flexible testing environment.
- Your team may already be using other 3rd party testing tools for QA-ing your applications. Team
Tester can launch these for you.
• You may also want to “roll your own” test tools using .NET, if you’d like finer control over how an
application is tested.
- Perhaps your application has a custom user interface or IDE. You could develop a tool that can
simulate a user interacting with it.
- You also have the option of building the Team Tester function into your test application. Team Tester
and its APIs are completely extensible.
• When you create a generic test pointing to a separate test application (a test harness), that application
will run with your current logon privileges.
- Be sure you trust and know the contents of that test.
• You can also gather code coverage information from generic testing applications.
- However, this is only possible if the generic testing applications were originally developed with
instrumentation to deliver that information.
- See MSDN for more details.
Manual Testing
• Manual testing is humans performing tests that require complete manual interaction.
- Test results are stored in a Text or Word document, depending on what you have access to.
- If part of a group of automated tests, Team Tester will stop and bring up the testing document.
- It will ask the user to perform the steps listed in the document. The user will need to select Pass or Fail
before the other tests and continue.
• The Word document (Word 2003 or newer) looks like this:
• During a test run that contains a manual test, a dialog box appears.
- This dialog informs the user that a manual test halts execution of the test run until the manual test is
completed.
• A dialog box appears with two simple radio buttons (Pass and Fail) and an Apply button, like so:
- Remember, Team Tester has no idea what test(s) you performed. It’s up to you to actually perform the
test(s) and document the results.
• Ordered tests are a group of tests that can be run together in a synchronous fashion.
- When the tests are performed, the results show up in the Test Manager or Test Results window as one
row.
- Double-clicking the test results of an ordered test show greater detail of each of the included tests.
- Ordered tests cannot contain load tests.
• You choose tests to be gathered into an ordered test in a dialog similar to the dialog used with selecting
tests for the load test.
- Note the “Continue after failure” checkbox, which allows successive tests to proceed even if a prior test
fails.
- Be aware, if you leave it unchecked and one of the tests fails, none of the remaining tests will run.
Generic Testing
• Generic tests are an extension of Team Tester. They allow separate applications or scripts to perform
testing on our application.
- This allows for a more flexible testing environment.
- Your team may already be using other 3rd party testing tools for QA-ing your applications. Team
Tester can launch these for you.
• You may also want to “roll your own” test tools using .NET, if you’d like finer control over how an
application is tested.
- Perhaps your application has a custom user interface or IDE. You could develop a tool that can
simulate a user interacting with it.
- You also have the option of building the Team Tester function into your test application. Team Tester
and its APIs are completely extensible.
• When you create a generic test pointing to a separate test application (a test harness), that application
will run with your current logon privileges.
- Be sure you trust and know the contents of that test.
• You can also gather code coverage information from generic testing applications.
- However, this is only possible if the generic testing applications were originally developed with
instrumentation to deliver that information.
- See MSDN for more details.
Manual Testing
• Manual testing is humans performing tests that require complete manual interaction.
- Test results are stored in a Text or Word document, depending on what you have access to.
- If part of a group of automated tests, Team Tester will stop and bring up the testing document.
- It will ask the user to perform the steps listed in the document. The user will need to select Pass or Fail
before the other tests and continue.
• The Word document (Word 2003 or newer) looks like this:
• During a test run that contains a manual test, a dialog box appears.
- This dialog informs the user that a manual test halts execution of the test run until the manual test is
completed.
• A dialog box appears with two simple radio buttons (Pass and Fail) and an Apply button, like so:
- Remember, Team Tester has no idea what test(s) you performed. It’s up to you to actually perform the
test(s) and document the results.
Ordered Testing, Generic Testing
Table of Contents
Copyright (c) 2008. Intertech, Inc. All Rights Reserved. This information is to be used exclusively as an
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Courseware
Training Resources
Tutorials