For software development in small teams defining and running test-cases could help a lot. Actually we could have used this very well for a project I have just been working on. It would fit very well into strebers concept:
We would have another type of tasks called
Requirement. (The name could change).
For a project we can define any number of:
- TestSuites - Holding a description and a number of requirements to be tested
- TestLogs - Collects the results of a TestSuite ran by a team member at a certain time, version and plattform.
Requirements are listed in a list similar to 'my tasks' and can be grouped into the project folders.
TestSuites are listed like versions in the top navigation of the project. In the view of a
TestSuite you would see a table of the previous test-results and the option to run a new test.
Running a TestSuite:
Form with:
- date (filled automatically)
- version_id
- version (alternative string)
- plattform
- comment
for each requirment form with following options:
- tested: [no, yes, not possible, unclear meaning,...] (not sure if we need this)
- result: [not tested, passed, failed]
- rate: [ excellent, good, ok, sufficient, imperfect, horrible, not existing]
- comment
TestProtokolls could be printed for signing with clients.
Normally you only would create one test suite for a project. But it might be useful to define several e.g. for different project phases or purposes. The good thing is, that this function allows you to add testers to your project and get them to work immediatly. If the requirements are written in plain words, they just start testing. As you probably know, this is not the funniest job, but it has to be done and getting people to do it, is a tremendous help.
Tracking the results over some time could provide important feedback.