Changes between Version 122 and Version 123 of TestManagerForTracPlugin
- Timestamp:
- Feb 9, 2022, 7:02:05 AM (14 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TestManagerForTracPlugin
v122 v123 9 9 This plugin implements a full test management life-cycle: definition, planning, execution, statistics. 10 10 11 This 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.11 This 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. 12 12 13 13 This plugin uses Wiki pages and an additional data model to store Test Cases, rather than tickets. This allows you to separate your tickets from your test findings, while still being powered by the Trac search engine and formatting syntax for Wiki pages. … … 29 29 * Test cases, catalogs and plans can have their own '''custom properties''', defined in `trac.ini` like tickets. All property types are supported: text, text area, listbox, radio buttons, checkbox. 30 30 * Defining '''custom test outcomes (statuses)''', in addition to the built-in "Untested", "Success", "Failed". 31 * Test execution '''statistical charts''', showing the overall testing activity, status of the test plans, statistics on the tickets opened agains all or a specific test plan. '''Exporting the data to CSV'''.31 * Test execution '''statistical charts''', showing the overall testing activity, status of the test plans, statistics on the tickets opened against all or a specific test plan, using [http://www.flotcharts.org/ Flot] (MIT licensed). '''Exporting the data to CSV'''. 32 32 * Choosing between Tree and Tabular view of the test catalogs or test plans, and the contained test cases. 33 33 * In the tabular view, choosing which columns to display, including any custom property, and the ability to add '''calculated rows''', such as sums, averages, min or max. … … 351 351 See the following figure for what happens when you click on the "Show Related Tickets" button from the Test Case shown at the previous section. 352 352 353 Trac plugin developers may be in sterested in the fact that a '''[wiki:TestManagerForTracPluginApi#GettingalltheTicketsrelatedtoaTestCase programmatic Python API]''' is provided to retrieve all of the Tickets opened against a Test Case, in all or in a specific Test Plan.353 Trac plugin developers may be interested in the fact that a '''[wiki:TestManagerForTracPluginApi#GettingalltheTicketsrelatedtoaTestCase programmatic Python API]''' is provided to retrieve all of the Tickets opened against a Test Case, in all or in a specific Test Plan. 354 354 355 355 [[BR]] [[Image(TestCaseInPlan03.png_th.png, link=[wiki:TestManagerForTracPluginGallery#DisplayingtheticketsrelatedtoaTestCaseinaPlan])]] … … 467 467 == Customization and Personalization 468 468 469 The Test Manager plugin allows for a deep customization and personalization. The elements you can customize arethe following:469 The plugin can be customized with the following: 470 470 471 471 * Adding [#CustomFields custom fields] to the test artefacts, ie Test Catalogs, Test Case definitions, Test Plans, Test Case instances. It may be useful, for example, to add a "Test Effort" field to Test Cases, to be able to better plan your testing time and resources. … … 475 475 * Adding [#TestArtefactTemplates Test Artefact Templates] for Test Catalogs and Test Cases, and specifying which default template should be used for new test cases in any particular catalog. 476 476 477 In addition to these, you can personalize several aspects of the Test Manager behavior, by means of the [#TestManagerSettings Test Manager Settings] administration panel.477 Additionally, you can personalize several aspects of the Test Manager behavior, by means of the [#TestManagerSettings Test Manager Settings] administration panel. 478 478 479 479 === Custom fields … … 666 666 ==== Test Statistics default settings 667 667 668 You can personalize the default period of time the statistical charts will display, in terms of historical depth and scale .668 You can personalize the default period of time the statistical charts will display, in terms of historical depth and scale: 669 669 670 670 * Number of days shown by default: determines the historical depth of the charts, in terms of days back from the current date. … … 709 709 == Security 710 710 711 The following new permissions are available to manage the Test Manager security:711 The following new permissions are available: 712 712 713 713 * TEST_VIEW - Ability to view test catalogs and test cases … … 767 767 == Installation 768 768 769 '''Trac 0.12 and 1.4 are supported''', and also '''Python 2.7'''. 769 '''Trac 0.12 and 1.4 are supported''', and also '''Python 2.7'''. Trac 1.5 and above is not supported yet. 770 770 771 771 '''Note:''' If you are using '''MySQL''' or '''PosgreSQL''', the database user must have read access to the `trac.ini` file. … … 829 829 '''Check the permissions on the egg file and on the `trac.ini` file''' 830 830 831 The user user to runTrac (either tracd or Apache) must be able to read the egg files.832 833 It has been reported that for PosgreSQL also its user mustbe able to read the `trac.ini` file.831 The system user running Trac (either tracd or Apache) must be able to read the egg files. 832 833 It has been reported that for PosgreSQL its user must also be able to read the `trac.ini` file. 834 834 835 835 '''Check the log files'''