|Version 14 (modified by anonymous, 8 years ago) (diff)|
I've developed a test case management tool that uses subversion as the testcase repository and uses the ticket framework in trac to create test runs.
Some of the common problems that any testcase management tool faces are:
- versioning of the testcases (taken care of by subversion)
- reporting (taken care of by trac ticket reports)
- generating specific test runs (taken care of specifically by the plugin)
The advantage of having a testcase management tool in trac is that it removes the need to have yet another system that manages testcases...with all the usual problems of maintaing user account, system upgrades, licensing issues. The other advantage is that it adds more transparency to the testing process as the tool and any testcases are right there for anyone to see.
Test cases are stored in a very simple XML format. And you can specify collection of test cases (for example a smoke test) by specifying which test cases belong to a test template. This information is also specified in an xml file.
Configuration steps required
- create a testcases directory within an existing subvesion project. We typically structure our development projects with a main project directory and then a source and build subdirectory. So when you add the testcases directory you might have something like this:
project/source/ <-- checked into subversion
project/build/ <-- this is not checked in but created when you build the application
project/testcases/ <-- checked into subversion
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
- Add testcases and commit those testcases to your subversion repository using the example format (see attachement)
- Create a testtemplate file and create and testtemplates you might care about (for example the smoketest).
- add to the trac.config file a new section:
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.
- add a new ticket type called testcase
- I also add a custom ticket type in the trac.config file for reporting purposes (although this is not required yet...just really useful)
[ticket-custom] testcase_result=select testcase_result.label= Test Case Result testcase_result.options=pass|fail|incomplete
- enable the plugin either through the trac admin plugin or by modifying the trac.config file:
I've added some helpful debugging/error checking that should help if an error occurs. Probably the most likely error is you'll specify the relative path to the testcases incorrectly.
If you have any issues, create a new ticket.
Download and Install using easy_install
You can use easy install to install the testManagementPlugin by doing this:
If you don't know what easy_install is or don't have it install go to : http://peak.telecommunity.com/DevCenter/PythonEggs
Windows users should add the python2X/scripts directory to their path.
'Running a weekly smoke test.'
'Step 1(Create your test cases)' Take a look at the example test case I attached at the bottom of this page. It's a very simple XML format for specifying what a test case should be.
A test case has an Id (which should be the file name without any extensions), a component (matching a real component in your TRAC project), a summary, a description, and a field for describing the expected results of the test.
'Step 2(Define any required grouping of testcases in the testtemplates.xml file):'
An example grouping with be specifying that tests: test1, test2, and test3 all belong to the smoketest.
Make sure the tests and template file are checked in.
'Step 3 (Creating a test run)' Click on the TestManagement tab on the main trac menu.
Click on the Test Run link
Select users to assign testcases to (these have to be known users to the trac system).
Select the appropriate version, and/or milestone/sprint for this testrun.
Select the testcases, and/or the appropriate test template.
Click the generate test run button.
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.
'Step 4 (Run the testcases)'
Open one of the created tickets and using the testcase_result custom field specify whether the test for this test run passed,failed, or was not run for whatever reason.
Close each ticket in the normal way by setting the ticket to "fixed" (or one of the other appropriate resolved states).
-  by edunne on 2008-09-26 22:29:45
uploading a packaged (egg) version of the latest stable version of the genshi/unicode merge.
-  by edunne on 2008-09-26 19:22:37
creating a tags folder
-  by edunne on 2008-09-26 19:04:39
added some additional error messages, merged the unicode version with the genshi version (also that was in the previous change). Updated the version num in setup.py