Partial Execution

[c2pil]

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

[fmancardi]

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 http://mantis.testlink.org/view.php?id=7492#c27896 ?

regards

[fmancardi]

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.

[c2pil]

Hello,

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.

Regards