Hello,
I'm using TestLink 1.9.9 and I would like to remove the platform filter from the Test Execution.
Currently I have to select a platform and it only displays Test Cases that platform. I would like to display all the Test Cases at once and indicating which platform they belong to.
Could you please point me in the right direction? (Which classes would I have to modify? Would be more useful to introduce the "Any" option for that filter instead of removing it?)
Many thanks,
petsparc5
Removing Platform Filter from Test Execution
Moderators: Amaradana, TurboPT, TL Developers
Re: Removing Platform Filter from Test Execution
You are confusion terms: platform is NOT a FILTER but a SETTING same way that test plan and build are settings.
Test plan + build + platform creates an EXECUTION context, and our idea is to work on each test cas in one and only one execution context at a time.
because each execution context will generate ONE EXECUTION result with it's own notes, issues and attachments.
Then ANY is not an option for a setting and IMHO if you want to use it, RIGHT value is 'ALL AVAILABLE'.
If You plan to go in this direction (that will not be part of stable code) you are going to expect lot of work because you need to change
1. how results of previous execution are retrieved and displayed.
2. how to save results.
IMHO it will not be an interesting approach.
If you need to go for massive execution IMHO, best thing to do is create OUTSITE TestLink an XML file with results and import it on testlink using available features.
IMHO it's always better present the use case you want to cover, instead of starting from the end i.e. the solution, because you are going to get more and distintc opinions, ideas, experiences
Test plan + build + platform creates an EXECUTION context, and our idea is to work on each test cas in one and only one execution context at a time.
because each execution context will generate ONE EXECUTION result with it's own notes, issues and attachments.
Then ANY is not an option for a setting and IMHO if you want to use it, RIGHT value is 'ALL AVAILABLE'.
If You plan to go in this direction (that will not be part of stable code) you are going to expect lot of work because you need to change
1. how results of previous execution are retrieved and displayed.
2. how to save results.
IMHO it will not be an interesting approach.
If you need to go for massive execution IMHO, best thing to do is create OUTSITE TestLink an XML file with results and import it on testlink using available features.
IMHO it's always better present the use case you want to cover, instead of starting from the end i.e. the solution, because you are going to get more and distintc opinions, ideas, experiences