Testopia:Considerations: Difference between revisions

Latest revision as of 22:34, 28 March 2007

General

How should midair collisions be handled?
What events should trigger notification and to whom?
- Currently has the following:
  - Entire test run completes
  - Test run completes for a tester
  - Test run completes for a component
  - Test case log entry is marked as failed
Should a run be allowed to include test cases that are not associated with the plan the run is for? If so, should they be automatically linked to that plan?

Reports

What kind of standard reports should be included?
- I tend to have quite a few TestRun under a signle TestPlan. It will be nice to have a feature that calculates the percentage of a TestRun (PASS/Total TC * 100%) appended at the end of each TestRun. [llim]
- There should be a way to print/export a test plan document (or subset thereof) in a format that would include the "front matter", all the tests (that fall into the subset), etc. This would be good for projects that require a paper trail, want to hand their acceptance test plan to the customer/user, etc.

Please use the Discussion link to reply or feel free to edit this page to add things we have not considered.

@@ Line 2: / Line 2: @@
 '''General'''
-# Bugzilla versions to support
-#* Current development is on 2.22 and many changes do not back port well due to dependency on Bugzilla objects which are not present in 2.20. I have found that branching for each of the branches significantly increases the work load.
 # How should midair collisions be handled?
 # What events should trigger notification and to whom?
@@ Line 12: / Line 10: @@
 #**	Test case log entry is marked as failed
 # Should a run be allowed to include test cases that are not associated with the plan the run is for? If so, should they be automatically linked to that plan?
-# What kind of time tracking requirements are there?
-# Should a Test Plan be able to clone across to another product? [llim]
-'''Acess Controls'''
-# Who should be able to edit test plans
-#* Currently members of managetestplans group
-#**managetestplans inherits edittestcases and runtests
-# Who should be able to edit test cases
-#* Currently members of edittestcases group
-# Who should be able to edit test runs
-#* Currently members of either managetestplans or edittestcases groups, though there has been a request for an additional group - runtest - who will be able to pass or fail testcases in a run as well as edit other attributes of the run.
 '''Reports'''
 # What kind of standard reports should be included?