New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Partial Execution #181

wants to merge 6 commits into
base: testlink_1_9


None yet
3 participants
Copy link

c2pil commented Dec 15, 2018

In response of Issue 0007492, this is the first iteration for the partial execution feature.

syji and others added some commits Dec 14, 2018


This comment has been minimized.

Copy link

fmancardi commented Dec 15, 2018

First thanks for your contribution.
This will not be added soon to stable code
I've a critical question:
does this implementation follows the spec described in ?



This comment has been minimized.

Copy link

fmancardi commented Dec 16, 2018

Please provide technical details of your implementation, or it will be not possible review the code in the right way.
Silly but not for these less important details => double check the code that update the testlink version because testlink 1.9.19 is not Alan Turing.


This comment has been minimized.

Copy link

c2pil commented Dec 18, 2018


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 the step's notes and status.
When a user save a final execution (with a global status), the partial execution is deleted.

So, I choose 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.

There can be only one partial execution by test sheet / test plan / platform / build.

In my implementation, I separated javascript from Smarty's HTML pages.


c2pil added some commits Jan 4, 2019


@c2pil c2pil closed this Jan 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment