Run a Test: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
<<< These are preliminary notes and may not be accurate. >>> | <<< These are preliminary notes and may not be accurate. >>> | ||
Programs should have a simple test to ensure the most basic functions are working. The test should run in a reasonable amount of time on par with the time it takes to build the program. These simple smoke tests need to be fully automated. Additional tests that are more comprehensive can also be provided, but need not be included as part of the automated test system. | |||
# [[How the Test Scripts Work]] | # [[How the Test Scripts Work]] | ||
Revision as of 13:29, 9 January 2009
<<< These are preliminary notes and may not be accurate. >>>
Programs should have a simple test to ensure the most basic functions are working. The test should run in a reasonable amount of time on par with the time it takes to build the program. These simple smoke tests need to be fully automated. Additional tests that are more comprehensive can also be provided, but need not be included as part of the automated test system.
- How the Test Scripts Work
- An overview of the test mechanism.
- Subscribe to Test Results
- Receive summaries of daily test runs or notifications when specific tests fail.
- Run the Project Tests Locally
- Manually run tests or schedule them to be run automatically.
- Add a Test to a Project
- Write tests for a project so they will work with the test driver.