|Anonymous | Login | Signup for a new account||2019-12-07 01:43 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007492||TestLink||Test Execute - Step notes & result||public||2016-03-30 11:59||2019-02-22 19:17|
|Product Version||1.9.14 (2015 Q3)|
|Fixed in Version|
|Summary||0007492: Add the ability to keep a partial execution|
|Description||It will be useful to be able to save an execution without achieve it.|
In the case of a long test case, or in case of disruption, it may happen that we start to execute a test case without being able to complete. It will be nice to be able to store the partial execution to be able to retrieve it and terminate later.
|Steps To Reproduce||1- Execute a test case|
2- Fill the first step
3- Keep the second step blank
4- Save execution
5- Click on 'Destkop'
6- Click on the 'Test execution'
7- Select the same test case as in step 1
-> the first step is displayed, we can continue to execute steps
|Tags||No tags attached.|
|QA Team - Task Workflow Status|
|it's not on TestLink logic/architecture|
We plan to develop this "partial execution" mechanism into TestLink.
Our objective is to provide final code to TestLink team.
It will propose 2 functionalities in execution view :
- a "save partial execution" very similar to current save but results won't be taken in account in reports,
- a "edit last partial execution" - including tests steps notes and result - to complete and finish the execution.
We can provide the detailed requirements specs if needed.
We will investigate few solutions (plugin, core) but we haven't yet identify issues that blocks implementation. @fman : 0007492:0024656 says that it's not on TestLink, but could you please confirm that there is no blocking point?
Any suggestion/comment/help will be appreciated. We provide feedback here during implementation
edited on: 2018-09-27 14:59
update : according to fman advice, we'll provide core modification.
Below are our first iteration of user stories to explain our vision of "how it will work". Any suggestion/comment/help will be appreciated.
Some vocabulary :
tester = user with execution rights
partial execution = execution without final status (passed/failed/blocked)
final execution = execution saved during selection of the final status (passed/failed/blocked)
execution testcase context = campaign + PF + version selected in execution page
As a tester, I want to click on the new « save partial execution data » button to save filled data so that I am sure to retrieve information if an outage occurs.
As a user, I want to see “save partial execution data” only if I have execution rights assigned so that I am not disturbed by a button if I’m not able to use it
As a tester, I want TestLink to display execution page filled with saved data just after I clicked on the new « save partial execution data » button so that I am able to continue working without loosing my time to restore just saved data.
As a user, I want “restore partial execution data” button displayed only if I have execution rights assigned so that I am not disturbed by a button if I’m not able to use it
As a tester, I want «restore partial execution data » button displayed only if “partial execution save” data exists for this context so that I am not disturbed by a button if no restoration can be done.
As a tester, I want to access “partial execution data restoration” option if a partial execution save exists, no matters who did the save, so that I can continue execution of a testcase saved by an other tester.
As a tester, I want to click on «restore partial execution data » to restore saved data at the right place in the GUI so that I can understand easily restored data as if I just have written it.
As a tester, I want that restored data to be editable so that I can edit or delete information as if I just have written it.
As a tester, I want that restored data, eventually modified and completed with additional data since restoration, can be saved as a final execution so that I can save data as the final result
As a tester, I want that restored data, eventually modified and additional data added after restoration can be saved as a new partial execution so that I can save testcase execution data during execution progression.
As a tester, I want partial execution data to be automatically deleted during final execution save, event if the partial execution data haven’t been restored, so that I am sure that nobody will restore outdated data
As a tester, during partial execution save, I want the system to overwrite the previous existing partial execution for the same execution context if exists, so I will not have to handle a history of partial executions
As a tester, I want to be able to save a different partial execution for the same testcase if it is used in different TestLink context (campaign + PF + version) so that I can trace different behaviors according to execution context
As a tester, I want TestLink to restore the right data according to the current context if several to save a different partial execution for the same testcase if it is used in different TestLink context (campaign + PF + version) so that I can trace different behaviors according to execution context
As a TestLink user who use reports, I want “partial execution data” to be ignored by TestLink so metrics and reports won’t be impacted by unfinished work
|@Mr Bricodage, going to read. Great Job!!!!|
The first version of our PR has been pushed by @c2pil in github : https://github.com/TestLinkOpenSourceTRMS/testlink-code/pull/181 [^]
The goal is to save the results of steps (notes and status), without a final result. Attachments are intentionally lost.
Partial results can be saved and restored with a new buttons.
When a user restores a partial execution, he can see/edit the step's notes and status.
When a user saves a final execution (with a global status), the partial execution (if exists) is deleted.
We have chosen to separate the data of partial execution and the result of final execution and created a new database "execution_tcsteps_backup".
A partial backup is defined by:
. The steps identifiers (tcstep_id);
. The associated test plan (testplan_id)
. The platform (platformform_id);
. The version (build_id);
. the content of each note;
. The status of each note.
By design, there can be only one partial execution by test sheet / test plan / platform / build.
We’ll update the PR in few days, we will make the following improvements:
. Notes and status will be automatically restored after a partial execution save.
. Before saving a new partial execution, checking if there is at least one note or status filled in
I would like to discuss the need of a new table, because IMHO it not needed.
I would prefer to discuss privately via mail.
do you agree?
|2016-03-30 11:59||atisne||New Issue|
|2016-03-30 17:15||fman||Note Added: 0024656|
|2018-08-31 06:52||Mr.Bricodage||Relationship added||related to 0007629|
|2018-08-31 07:11||Mr.Bricodage||Note Added: 0027794|
|2018-09-27 14:59||Mr.Bricodage||Note Added: 0027896|
|2018-09-27 14:59||Mr.Bricodage||Note Edited: 0027896||View Revisions|
|2018-09-27 15:05||fman||Note Added: 0027897|
|2018-12-18 14:06||Mr.Bricodage||Note Added: 0028336|
|2018-12-18 16:27||fman||Note Added: 0028337|
|2019-02-17 10:03||fman||Issue cloned: 0008569|
|2019-02-17 10:03||fman||Relationship added||related to 0008569|
|Copyright © 2000 - 2019 MantisBT Team|