Version 4 (modified by deyan, 16 years ago) (diff) |
---|
Analysis
(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)
Overview
(The analysis of the first revision of each task should contain a brief overview of the whole task. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)
Task requirements
- Ensure execution of test plans in TestLink is possible by "tester" users.
Task result
(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))
Implementation idea
Filter Test cases a user with tester role can VIEW depending on test execution assignment. 'all' -> all test cases. 'assigned_to_me' -> test cases assigned to logged user. [DEFAULT VALUE] 'assigned_to_me_or_free' -> test cases assigned to logged user or not assigned. - 25 - $tlCfg->exec_cfg->view_mode->tester='assigned_to_me'; Filter Test cases a user with tester role can EXECUTE depending on test execution assignment. 'all' -> all test cases. 'assigned_to_me' -> test cases assigned to the current user. [DEFAULT VALUE] 'assigned_to_me_or_free' -> test cases assigned to logged user or not assigned $tlCfg->exec_cfg->exec_mode->tester='assigned_to_me'; User filter in Test Execution navigator: 'logged_user' -> combo will be set to the current user 'none' -> no filter applied by default [DEFAULT VALUE] $tlCfg->exec_cfg->user_filter_default='none';
Related
How to demo
(In this section you must add instructions for the demo of the task.)
Design
Implementation
(Implementation results should be described and linked here (from the wiki or the repository))
Testing
Comments
(Write comments for this or later revisions here.)