Changes between Version 115 and Version 116 of TestCaseManagementPlugin
- Timestamp:
- Dec 8, 2015, 6:07:50 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TestCaseManagementPlugin
v115 v116 5 5 == Description 6 6 7 This is a test case management tool that uses subversion as the testcase repository and uses the ticket framework in Trac to create test runs.7 This is a test case management tool that uses Subversion as the testcase repository and uses the ticket framework in Trac to create test runs. 8 8 9 9 Common problems in any testcase management tool are: 10 10 1. assigning a group of tests to a testing resource(s), ie '''a test run''' (this is what the plugin manages) 11 11 1. versioning of the test cases (taken care of by Subversion, because even testcases change over time) 12 1. reporting on results and progress (Trac reports /export to Excel/etc.)12 1. reporting on results and progress (Trac reports, export to Excel, etc.) 13 13 14 14 See also: TestManagerForTracPlugin, [http://www.teamst.org/ Test Link] (provides Trac integration), ManualTestingPlugin, QaTrackerPlugin … … 42 42 === Brief Digression 43 43 44 My personal philosophy is to encourage people to write work flow or task based driven testcases and have the tester use their brains to find issues. I call it script based Exploratory testing. Check out Exploratory testing by James Bach at http://satisfice.com. If they need to look at the UI in very high detail then the test case could simply be "compare the UI to the mockup and here's the link to the screen shot".44 My personal philosophy is to encourage people to write work flow or task based driven testcases and have the tester use their brains to find issues. I call it '''script based exploratory testing'''. Check out Exploratory testing by James Bach at http://satisfice.com. If they need to look at the UI in very high detail then the test case could simply be "compare the UI to the mockup and here's the link to the screen shot". 45 45 46 46 === Grouping testcases together … … 65 65 === Genshi Migration 0.11 66 66 67 You can download the source or preferably use easy_install for the 0.11.x compatible version here : 68 67 You can download the source or preferably use `easy_install` for the Trac 0.11.x compatible version: 69 68 {{{#!sh 70 easy_install.exe http ://trac-hacks.org/svn/testcasemanagementplugin/branches/testManagmentPluginGenshi71 }}} 72 73 If you need easy_install check: http://peak.telecommunity.com/DevCenter/EasyInstall 69 easy_install.exe https://trac-hacks.org/svn/testcasemanagementplugin/branches/testManagmentPluginGenshi 70 }}} 71 72 You can download easy_install from [http://peak.telecommunity.com/DevCenter/EasyInstall here]. 74 73 75 74 === Trac 0.10.x users 76 75 77 0.10.x Trac users should continue to use this version: [[BR]] 78 79 {{{ 80 easy_install.exe http://trac-hacks.org/svn/testcasemanagementplugin/branches/testManagementPlugin0.4.0 76 Trac 0.10.x users should continue to use this version: 77 {{{#!sh 78 easy_install.exe https://trac-hacks.org/svn/testcasemanagementplugin/branches/testManagementPlugin0.4.0 81 79 }}} 82 80 … … 85 83 == Source 86 84 87 You can check out TestCaseManagementPlugin [/svn/testcasemanagementplugin using Subversion], or [source:testcasemanagementplugin browse the source] with Trac.85 You can check out TestCaseManagementPlugin from [/svn/testcasemanagementplugin here] using Subversion, or [source:testcasemanagementplugin browse the source] with Trac. 88 86 89 87 == Configuration … … 104 102 }}} 105 103 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. 106 1. '''[ http://trac.edgewall.org/wiki/TracAdmin Add a new ticket type] called testcase'''.107 1. Add a custom ticket field '''Test Case Result''' in the `trac.ini` file for reporting purposes (optional) 104 1. '''[t:TracAdmin Add a new ticket type] called testcase'''. 105 1. Add a custom ticket field '''Test Case Result''' in the `trac.ini` file for reporting purposes (optional): 108 106 {{{#!ini 109 107 [ticket-custom] … … 118 116 testManagementPlugin.* = enabled 119 117 }}} 120 1. Restrict ticket owners to only known users of the system. You do this by looking for the line restrict_ownerin the `trac.ini` file:118 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: 121 119 {{{#!ini 122 120 restrict_owner = true … … 215 213 216 214 '''Author:''' [wiki:edunneSoftwareTesting@hotmail.com] [[BR]] 217 '''Maintainer:''' ''none''[[BR]]215 '''Maintainer:''' [[Maintainer]] [[BR]] 218 216 '''Contributors:''' A lot of people have stepped up and helped test the plugin so thanks