Changes between Version 113 and Version 114 of TestManagerForTracPlugin
- Timestamp:
- Mar 5, 2015, 2:10:03 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TestManagerForTracPlugin
v113 v114 3 3 ''' [ [wiki:TestManagerForTracPlugin Home] | [wiki:TestManagerForTracPluginChangeHistory Latest changes] | [wiki:TestManagerForTracPluginGallery Image gallery] | [http://www.youtube.com/watch?v=BIi3QMT0rT4 Video tutorial on Youtube] | [wiki:TestManagerForTracPluginQuickSetup Quick setup guide] | [http://sourceforge.net/projects/testman4trac Download] | [http://sourceforge.net/projects/testman4trac/files Source] | [wiki:TestManagerForTracPluginBugsFeatures Bugs/Feature requests] ]''' 4 4 5 = Test Manager plugin for Trac - Full test management life-cycle: definition, planning, execution, statistics = 5 = Test Manager plugin for Trac 6 7 A full test management life-cycle: definition, planning, execution, statistics. 8 6 9 [[Image(Carousel.png, link=)]] 7 10 8 == Summary == 11 == Summary 12 9 13 This test management Trac plugin can be used to create '''[wiki:TestManagerForTracPlugin#TestCases Test Cases]''', organize them in [wiki:TestManagerForTracPlugin#TestCatalogs Catalogs] and generate '''[wiki:TestManagerForTracPlugin#TestPlans Test Plans]''' to track their execution status and outcome. 10 14 11 Differently from other test management plugins for Trac that use Tickets as test case holders, this one uses Wiki pages and an additional proprietary data model to store Test Cases. This allows you to not pollute your ticket lists with something that is not a ticket, and at the same time is powered by the Trac search engine and formatting syntax for Wiki pages.15 This plugin uses Wiki pages and an additional proprietary data model to store Test Cases, rather than tickets. This allows you to not pollute your ticket lists with something that is not a test finding, and at the same time is powered by the Trac search engine and formatting syntax for Wiki pages. 12 16 13 17 A set of plugins intercept requests for Wiki pages that match the Test Manager URL namespace and decorate them with additional information stored in the database. 14 18 15 Features include:19 Key features: 16 20 17 21 * '''Defining test cases and organize in test catalogs (test suites)'''. … … 67 71 68 72 == Test Catalogs == 73 69 74 Test Catalogs contain Test Cases and may organize them in sub-catalogs. 70 75 … … 108 113 109 114 === Searching and filtering Test Cases === 115 110 116 A type-ahead, browser-side filtering feature allows for easily locating Test Cases matching a particular naming convention in the title, and/or a particular execution status. 111 117 … … 125 131 126 132 == Test Cases == 133 127 134 Test Cases are the smallest units of test execution. 128 135 … … 163 170 164 171 == Test Plans == 172 165 173 '''Since: 1.1.0''' 166 174 … … 173 181 The Test Cases associated to a Test Plan are called '''Test Cases in a Plan'''. Refer to [#TestCases Test Cases] for details about the additional information carried by these particular artifacts. 174 182 175 [[BR]]'''To create a Test Plan for a catalog''', open the desired Test Catalog (or sub-catalog), enter the name of the new Test Plan in the appropriate text field and click '''Generate a new Test Plan'''. A dialog box will be displayed, as show in the next figure, which lets you choose the characteristics of the Test Plan.183 '''To create a Test Plan for a catalog''', open the desired Test Catalog (or sub-catalog), enter the name of the new Test Plan in the appropriate text field and click '''Generate a new Test Plan'''. A dialog box will be displayed, as show in the next figure, which lets you choose the characteristics of the Test Plan. 176 184 177 185 Available options are: … … 221 229 222 230 == Moving or Copying Test Cases from one catalog to another == 231 223 232 It is also possible to move a single Test Case, or copy multiple Test Cases into a different catalog, with an experience similar to cut&paste. 224 233 … … 226 235 227 236 === Moving a single Test Case === 237 228 238 To move a single Test Case from one catalog into a nother, you: 229 239 … … 236 246 237 247 === Copying multiple Test Cases === 248 238 249 To copy one or more Test Cases, even from different catalogs, and paste them all together into a destination (sub-)catalog, you: 239 250 … … 248 259 249 260 === Organizing the contents of a Test Catalog === 261 250 262 To (re-)organize the contents of a Test Catalog, i.e. moving test cases around and changing their intended execution order, you can click the '''Organize Test Catalogs''' button. The dialog shown in the following figure will pop-up. 251 263 … … 261 273 262 274 == Linking a Ticket to a Test Case == 275 263 276 When viewing a Test Case definition or Test Case in a Plan, you can open a new Ticket by means of the '''Open Ticket on this Test Case''' button. 264 277 … … 321 334 some template text 322 335 }}} 336 323 337 === Showing Tickets related to a Test Case === 338 324 339 While browsing a Test Case, either inside or outside of a Test Plan, you can list all of its related Tickets - i.e. the Tickets that were opened using the above '''Open a Ticket on this Test Case''' button. 325 340 … … 339 354 340 355 == Test Management and Execution Statistics == 356 341 357 '''Since: 1.1.1''' 342 358 … … 354 370 355 371 === Test activity trend chart === 372 356 373 Displays the number of test cases created during time and the trend of the test activity, in terms of test cases to be tested, successful and failed. 357 374 … … 365 382 366 383 === Current test status chart === 384 367 385 Shows the current status of the test activity for all test plans of a specific plan, displaying the number of tests that are successful, failed and yet to be tested. 368 386 … … 372 390 373 391 === Tickets trend chart === 392 374 393 As long as [wiki:TestManagerForTracPlugin#LinkingaTickettoaTestCase tickets have been opened from the context of a test case in a plan], by means of the appropriate '''Open a ticket on this test case''' button, this chart shows the trend in tickets associated with all test plans or a specific plan, displaying the number of total, active (i.e. not closed) and closed tickets. 375 394 … … 711 730 712 731 == Download == 732 713 733 Download the egg files, ready to be installed, from the project site [http://sourceforge.net/projects/testman4trac/files here]. 714 734 715 735 == Source == 736 716 737 You can download the source code from [https://sourceforge.net/projects/testman4trac/files here]. 717 738