side by side
lines around each change
Show the changes in full context
White space changes
Feb 8, 2007 11:47:58 PM (
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 ==
1. 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
2. Add testcases and commit those testcases to your subversion repository using the example format (see attachement)
3. Create a testtemplate file and create and testtemplates you might care about (for example the smoketest).
4. add in your 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.
5. add a ticket type called testcase
6. I also add a custom ticket type in the trac.config file for reporting purposes
testcase_result.label= Test Case Result
7. 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.
== Bugs/Feature Requests ==
Hosting sponsored by