|Anonymous | Login | Signup for a new account||2017-03-28 11:59 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007857||TestLink||New Feature||public||2017-02-22 10:49||2017-03-20 14:45|
|Product Version||1.9.15 (2015 Q4)|
|Fixed in Version|
|Summary||0007857: Enhance configuration support at test plan level|
|Description||Currently, we have following two configurations available at test plan level:|
* Builds / Releases
During testing of embedded systems, one needs to use software and hardware combinations. For example, following are some parameters that will needed to be considered during test execution:
* Product Type/Variant
* Build version, i.e nightly, test/release candidate etc...
* Debug support, i.e JTAG, built-in etc...
* Build configuration, i.e Debug/Release
And there can be many others like these. So, having just current available parameters during execution (Build/Release, Platform), it becomes very difficult to incorporate and maintain the different variations/combinations within the single test plan, if we need to execute generic test cases on the different combinations.
One can use, for example, Host as Platform and Build version as Build/Release, but the other parameters cannot be adjusted appropriately.
Another option is to use separate test plans and incorporate these parameters by creating multiple platforms, but it makes it complex and difficult to maintain, because we will need to create multiple test plans for shared/generic test cases.
The suggestion under this issue is to add more flexibility in configuration support at test plan level so that the complexity of maintaining test cases for different variation can reduce.
There could be different options added at test project level which are similar to Platform (may have to choice to add for a given test plan), i.e Target, Software etc...
Or atleast a very generic option such as "Configuration" can be introduced which behaves similar to current "Platform" option. Having this option would certainly help us reducing the complexity and more filtering.
The new configuration field will need to have same behavior as that of Platform parameter in following areas:
* test plan creation
* test plan execution
|Tags||No tags attached.|
|QA Team - Task Workflow Status||TBD|
If configuration is like platform, then you have the solution already.
More detailed info, usage and examples are needed.
ALso impacts on execution and reports need to be provided
|Okay, I'll add more details here.|
|any news ?|
|Yes, I did not forget about it. I'll provide the details here soon.|
|2017-02-22 10:49||ikhaliq||New Issue|
|2017-02-22 16:36||fman||QA Team - Task Workflow Status||=> TBD|
|2017-02-22 16:36||fman||Severity||major => feature request|
|2017-02-22 16:37||fman||Note Added: 0026015|
|2017-02-22 16:38||fman||Assigned To||=> fman|
|2017-02-22 16:38||fman||Status||new => feedback|
|2017-02-27 10:07||ikhaliq||Note Added: 0026038|
|2017-02-27 10:07||ikhaliq||Status||feedback => assigned|
|2017-03-13 20:38||fman||Note Added: 0026104|
|2017-03-13 20:38||fman||Status||assigned => feedback|
|2017-03-20 12:06||ikhaliq||Note Added: 0026140|
|2017-03-20 12:06||ikhaliq||Status||feedback => assigned|
|2017-03-20 14:45||fman||Assigned To||fman =>|
|Copyright © 2000 - 2017 MantisBT Team|