34 | | |
35 | | 1. assigning a group of tests to a testing resource(s)...'''a test run''' (this is what the plugin manages) |
36 | | |
37 | | 2. versioning of the test cases (taken care of by subversion...yep even testcases change over time) |
38 | | |
39 | | 3. reporting on results and progress (trac reports/export to excel/etc.) |
40 | | |
41 | | [[BR]] |
42 | | '''So what is a test run?''' |
43 | | |
44 | | - a set of tests |
45 | | |
46 | | - assigned to a specific tester |
47 | | |
48 | | - for a particular product and version |
49 | | |
50 | | '''In more detail...''' |
| 32 | 1. assigning a group of tests to a testing resource(s)...'''a test run''' (this is what the plugin manages) |
| 33 | 1. versioning of the test cases (taken care of by subversion...yep even testcases change over time) |
| 34 | 1. reporting on results and progress (trac reports/export to excel/etc.) |
| 35 | |
| 36 | === So what is a test run? === |
| 37 | * a set of tests |
| 38 | * assigned to a specific tester |
| 39 | * for a particular product and version |
| 40 | |
| 41 | === In more detail... === |
80 | | |
81 | | 1. Create a testcase directory within an existing subversion project. This is where your testcase and testtemplate files go. We typically structure our development projects with a main project directory and then a source and build subdirectory. So when you add the testcase directory you might have something like this: |
82 | | |
83 | | project/source/ <-- checked into subversion [[BR]] |
84 | | project/build/ <-- this is not checked in but created when you build the application [[BR]] |
85 | | project/testcases/ <-- checked into subversion[[BR]] |
86 | | |
87 | | |
88 | | The nice thing about this is you add a lot more transparency to the testing process as testcases are bundled and versioned with the source code. |
89 | | |
90 | | 2. Add testcases and commit those testcases to your subversion repository using the example format (see attachment for correct XML format of testcase files). |
91 | | |
92 | | 3. Create a testtemplate file called testtemplates.xml, then specify which tests belong to which test templates, for example the smoke-test (see attachment for correct XML format of the test templates file). Not all tests have to belong to a template, it's just a convient way to group tests together. This file goes into the same project/testcases directory. |
93 | | |
94 | | 4. Add the following new section to the trac.ini file: |
95 | | |
96 | | {{{ |
97 | | |
| 70 | 1. Create a testcase directory within an existing subversion project. This is where your testcase and testtemplate files go. We typically structure our development projects with a main project directory and then a source and build subdirectory. So when you add the testcase directory you might have something like this: |
| 71 | {{{ |
| 72 | project/source/ <-- checked into subversion |
| 73 | project/build/ <-- this is not checked in but created when you build the application |
| 74 | project/testcases/ <-- checked into subversion |
| 75 | }}} |
| 76 | The nice thing about this is you add a lot more transparency to the testing process as testcases are bundled and versioned with the source code. |
| 77 | 1. Add testcases and commit those testcases to your subversion repository using the example format (see attachment for correct XML format of testcase files). |
| 78 | 1. Create a testtemplate file called testtemplates.xml, then specify which tests belong to which test templates, for example the smoke-test (see attachment for correct XML format of the test templates file). Not all tests have to belong to a template, it's just a convient way to group tests together. This file goes into the same project/testcases directory. |
| 79 | 1. Add the following new section to the trac.ini file: |
| 80 | {{{ |
100 | | |
101 | | }}} |
102 | | |
103 | | This is important because Trac can be set up against subdirectories so you often don't link trac to your root subversion folder, so only specify the full path from the root node if that's how trac was set up. |
104 | | |
105 | | 5. '''[http://trac.edgewall.org/wiki/TracAdmin add a new ticket type] called testcase''' |
106 | | |
107 | | 6. I also add a custom ticket type in the trac.ini file for reporting purposes (although this is not required yet...just really useful) |
108 | | |
| 83 | }}} |
| 84 | This is important because Trac can be set up against subdirectories so you often don't link trac to your root subversion folder, so only specify the full path from the root node if that's how trac was set up. |
| 85 | 1. '''[http://trac.edgewall.org/wiki/TracAdmin add a new ticket type] called testcase''' |
| 86 | 1. I also add a custom ticket type in the trac.ini file for reporting purposes (although this is not required yet...just really useful) |
235 | | ''''Step 3 (Creating a test run)'''' |
236 | | Click on the TestManagement tab on the main trac menu. |
237 | | |
238 | | Click on the Test Run link |
239 | | |
240 | | Select users to assign testcases to (these have to be known users to the trac system). |
241 | | |
242 | | Select the appropriate version, and/or milestone/sprint for this testrun. |
243 | | |
244 | | Select the testcases, and/or the appropriate test template. |
245 | | |
246 | | Click the generate test run button. |
247 | | |
248 | | This will re-direct you to the '''custom ticket reporting page with a pre-built query''' that should show you all the test cases that you just created grouped by user. It will also pick up previously created testcases if they also exactly match the query criteria. |
249 | | |
250 | | ''''Step 4 (Run the testcases)'''' |
251 | | |
| 205 | ==== Step 3 (Creating a test run) ==== |
| 206 | 1. Click on the TestManagement tab on the main trac menu. |
| 207 | 1. Click on the Test Run link |
| 208 | 1. Select users to assign testcases to (these have to be known users to the trac system). |
| 209 | 1. Select the appropriate version, and/or milestone/sprint for this testrun. |
| 210 | 1. Select the testcases, and/or the appropriate test template. |
| 211 | 1. Click the generate test run button. |
| 212 | This will re-direct you to the '''custom ticket reporting page with a pre-built query''' that should show you all the test cases that you just created grouped by user. It will also pick up previously created testcases if they also exactly match the query criteria. |
| 213 | |
| 214 | ==== Step 4 (Run the testcases) ==== |