51 | | |
52 | | == Bugs/Feature Requests |
53 | | |
54 | | Existing bugs and feature requests for TestCaseManagementPlugin are |
55 | | [report:9?COMPONENT=TestCaseManagementPlugin here]. |
56 | | |
57 | | If you have any issues, create a |
58 | | [/newticket?component=TestCaseManagementPlugin new ticket]. |
59 | | |
60 | | [[TicketQuery(component=TestCaseManagementPlugin&group=type,format=progress)]] |
61 | | |
62 | | == Download |
63 | | |
64 | | Download the zipped source from [export:testcasemanagementplugin here]. |
65 | | |
66 | | == Source |
67 | | |
68 | | You can check out TestCaseManagementPlugin from [/svn/testcasemanagementplugin here] using Subversion, or [source:testcasemanagementplugin browse the source] with Trac. |
69 | | |
70 | | == Installation |
71 | | |
72 | | General instructions on installing Trac plugins can be found on the [TracPlugins#InstallingaTracplugin TracPlugins] page. |
73 | | |
74 | | == Configuration |
75 | | |
76 | | 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: |
77 | | {{{ |
78 | | project/source/ <-- checked into subversion |
79 | | project/build/ <-- this is not checked in but created when you build the application |
80 | | project/testcases/ <-- checked into subversion |
81 | | }}} |
82 | | This way you add transparency to the testing process as testcases are bundled and versioned with the source code. |
83 | | 1. Add testcases and commit those testcases to your Subversion repository using the example format (see attachment for correct XML format of testcase files). |
84 | | 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 convenient way to group tests together. This file goes into the same `project/testcases` directory. |
85 | | 1. Add the following new section to the `trac.ini` file: |
86 | | {{{#!ini |
87 | | [testManagementExtension] |
88 | | SubversionPathToTestCases = /relativePathToTestCasesInYour/Subversion/Repository |
89 | | }}} |
90 | | This is important, because Trac can be set up against subdirectories so you often don't link Trac to your root Subversion folder. Only specify the full path from the root node if that is how Trac is set up. |
91 | | 1. '''[t:TracAdmin Add a new ticket type] called testcase'''. |
92 | | 1. Add a custom ticket field '''Test Case Result''' in the `trac.ini` file for reporting purposes (optional): |
93 | | {{{#!ini |
94 | | [ticket-custom] |
95 | | testcase_result = select |
96 | | testcase_result.label = Test Case Result |
97 | | testcase_result.options = pass|fail|incomplete |
98 | | testcase_result.value = |
99 | | }}} |
100 | | 1. Enable the plugin either through the Trac admin plugin or by modifying the `trac.ini` file: |
101 | | {{{#!ini |
102 | | [components] |
103 | | testManagementPlugin.* = enabled |
104 | | }}} |
105 | | 1. Restrict ticket owners to only known users of the system. You do this by looking for the line `restrict_owner` in the `trac.ini` file: |
106 | | {{{#!ini |
107 | | restrict_owner = true |
108 | | }}} |
109 | | |
110 | | I've added some helpful debugging/error checking that should help if an error occurs. The most likely error is specifying the relative path to the testcases incorrectly. |
| 137 | == Bugs/Feature Requests |
| 138 | |
| 139 | Existing bugs and feature requests for TestCaseManagementPlugin are |
| 140 | [report:9?COMPONENT=TestCaseManagementPlugin here]. |
| 141 | |
| 142 | If you have any issues, create a |
| 143 | [/newticket?component=TestCaseManagementPlugin new ticket]. |
| 144 | |
| 145 | [[TicketQuery(component=TestCaseManagementPlugin&group=type,format=progress)]] |
| 146 | |
| 147 | == Download |
| 148 | |
| 149 | Download the zipped source from [export:testcasemanagementplugin here]. |
| 150 | |
| 151 | == Source |
| 152 | |
| 153 | You can check out TestCaseManagementPlugin from [/svn/testcasemanagementplugin here] using Subversion, or [source:testcasemanagementplugin browse the source] with Trac. |
| 154 | |
| 155 | == Installation |
| 156 | |
| 157 | General instructions on installing Trac plugins can be found on the [TracPlugins#InstallingaTracplugin TracPlugins] page. |
| 158 | |
| 159 | == Configuration |
| 160 | |
| 161 | 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: |
| 162 | {{{ |
| 163 | project/source/ <-- checked into subversion |
| 164 | project/build/ <-- this is not checked in but created when you build the application |
| 165 | project/testcases/ <-- checked into subversion |
| 166 | }}} |
| 167 | This way you add transparency to the testing process as testcases are bundled and versioned with the source code. |
| 168 | 1. Add testcases and commit those testcases to your Subversion repository using the example format (see attachment for correct XML format of testcase files). |
| 169 | 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 convenient way to group tests together. This file goes into the same `project/testcases` directory. |
| 170 | 1. Add the following new section to the `trac.ini` file: |
| 171 | {{{#!ini |
| 172 | [testManagementExtension] |
| 173 | SubversionPathToTestCases = /relativePathToTestCasesInYour/Subversion/Repository |
| 174 | }}} |
| 175 | This is important, because Trac can be set up against subdirectories so you often don't link Trac to your root Subversion folder. Only specify the full path from the root node if that is how Trac is set up. |
| 176 | 1. '''[t:TracAdmin Add a new ticket type] called testcase'''. |
| 177 | 1. Add a custom ticket field '''Test Case Result''' in the `trac.ini` file for reporting purposes (optional): |
| 178 | {{{#!ini |
| 179 | [ticket-custom] |
| 180 | testcase_result = select |
| 181 | testcase_result.label = Test Case Result |
| 182 | testcase_result.options = pass|fail|incomplete |
| 183 | testcase_result.value = |
| 184 | }}} |
| 185 | 1. Enable the plugin either through the Trac admin plugin or by modifying the `trac.ini` file: |
| 186 | {{{#!ini |
| 187 | [components] |
| 188 | testManagementPlugin.* = enabled |
| 189 | }}} |
| 190 | 1. Restrict ticket owners to only known users of the system. You do this by looking for the line `restrict_owner` in the `trac.ini` file: |
| 191 | {{{#!ini |
| 192 | restrict_owner = true |
| 193 | }}} |
| 194 | |
| 195 | I've added some helpful debugging/error checking that should help if an error occurs. The most likely error is specifying the relative path to the testcases incorrectly. |
| 196 | |