Difference between revisions of "QA/test automation"
From Apache OpenOffice Wiki
< QA
(Created page with "MUST READ BEFORE WRITING AUTOMATION CODE 1. Don't us random. That makes test uncertain, hard to debug and maintain. Instead of it, prepare enough special test data to cover bound…") |
|||
| Line 1: | Line 1: | ||
| + | {{DISPLAYTITLE: Apache OpenOffice Test Automation}} | ||
| + | [[Category: Quality Assurance]] | ||
| + | [[Category: TestAutomation]] | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
MUST READ BEFORE WRITING AUTOMATION CODE | MUST READ BEFORE WRITING AUTOMATION CODE | ||
1. Don't us random. That makes test uncertain, hard to debug and maintain. Instead of it, prepare enough special test data to cover boundary conditions. | 1. Don't us random. That makes test uncertain, hard to debug and maintain. Instead of it, prepare enough special test data to cover boundary conditions. | ||
2. Name tests properly. "testLoadFileFromServer" is better than "test". | 2. Name tests properly. "testLoadFileFromServer" is better than "test". | ||
3. Clean up in @After/@AfterClass method to avoid affecting other testcases. | 3. Clean up in @After/@AfterClass method to avoid affecting other testcases. | ||
Revision as of 07:52, 10 August 2012
MUST READ BEFORE WRITING AUTOMATION CODE
1. Don't us random. That makes test uncertain, hard to debug and maintain. Instead of it, prepare enough special test data to cover boundary conditions.
2. Name tests properly. "testLoadFileFromServer" is better than "test".
3. Clean up in @After/@AfterClass method to avoid affecting other testcases.
