Testopia:Considerations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Ghendricks (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
'''General''' | |||
# How should midair collisions be handled? | # How should midair collisions be handled? | ||
# What events should trigger notification and to whom? | # What events should trigger notification and to whom? | ||
| Line 9: | Line 10: | ||
# <strike>Should environments be global or restricted by product? by plan?</strike> | # <strike>Should environments be global or restricted by product? by plan?</strike> | ||
#* Decided on Global since otherwise you would have to enforce that the product and version match that of the run but you may not have a run defined before creating the environment. | #* Decided on Global since otherwise you would have to enforce that the product and version match that of the run but you may not have a run defined before creating the environment. | ||
# 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 | # Who should be able to edit test plans | ||
#* Currently members of managetestplans group | #* Currently members of managetestplans group | ||
#**managetestplans inherits edittestcases and runtests | |||
# Who should be able to edit test cases | # Who should be able to edit test cases | ||
#* Currently members of edittestcases group | #* Currently members of edittestcases group | ||
# Who should be able to edit test runs | # 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. | #* 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? | # 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] | #* 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] | ||
Please use the [[Talk:Testopia:Considerations|Discussion]] link to reply or feel free to edit this page to add things we have not considered. | Please use the [[Talk:Testopia:Considerations|Discussion]] link to reply or feel free to edit this page to add things we have not considered. | ||
Revision as of 23:25, 16 June 2006
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
- Currently has the following:
- 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?
Should environments be global or restricted by product? by plan?- Decided on Global since otherwise you would have to enforce that the product and version match that of the run but you may not have a run defined before creating the environment.
- 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
- Currently members of managetestplans group
- 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?
- 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]
Please use the Discussion link to reply or feel free to edit this page to add things we have not considered.