get back 1.6.x behaviour of saving results?

[jsm]

Hi,

in 1.6.3 there was a different behaviour of result handling during test execution:
if the whole test plan was selected in execution tree there where only 'save results'-buttons above and below of all testcases. It was possible to add results to some of the testcases and by pressing the save-button, all those results have been saved while the remaining testcases stayed unchanged.
If a single testcase was selected, the save touched only the results belonging to it.

In 1.7.1 I see only save-bottons in each testcase. If I enter results to a number of testcases I have to come back to the page, where I wrote them, and save the results one by one.
Is there a configuration which bring back the possibility to confirm several changes in one action. Of course the state of the other testcases in test plan should stay untouched.

[fman]

On 1.6.3 was possible because the NOT RUN Status was present
On 1.7.x this status has been removed.

Just try using config paramenters con cfg/const*

where you can select what status must be present at UI level.

Try and let us know


regards

[jsm]

I added "not_run" to $g_tc_status_for_ui and changed $g_tc_status_for_ui_default from "blocked" to "not_run" in cfg\const.inc.php.

The state is correctly shown in the UI, but button 'save results' still only affects the testcase it belongs to.

Is there a way to enable a kind of 'save all results' button (for example besides 'print' and 'show complete history' in the header - like it was shown in 1.6.3)?
Or is it possible to change the behaviour of the existing buttons in a way like 'if only one testcase is shown save it's results; if several tc are shown (i.e. all belonging to the selected suite), save results of all those testcases?

[fman]

what about using Bulk controls ? present on top of page ?

[jsm]

aarrrggggl, I never saw them as the section was collapsed.
aches to my head!

It's working as expected - !!GREAT JOB!!