This is finally fixed :ALM 16.0.1 P2 (What's New in ALM (microfocus.com) )

"When running a manual test, images added to the test step's actual result are not saved to the Test Plan module. For details, see Manual Runner: Step Details Page."

This is finally fixed :ALM 16.0.1 P2 (What's New in ALM (microfocus.com) )

"When running a manual test, images added to the test step's actual result are not saved to the Test Plan module. For details, see Manual Runner: Step Details Page."

This should be addressed. Test runs are used to collect test evidence attachments that should stay with the run only. If a user wants to make an edit to a step to add some clarity, we now have to coach them to wait and do it after the run...so that will never happen. For my latest project, rushed as always, script quality was a concern going in, many updates were processed on the fly, now 1/3 of our scripts have useless screen shots that we have to manually remove before our next test cycle to avoid an audit issue.

Hard to understand why customers would find this to be desirable behaviour. A setting to include attachment or not when user saves changes to the plan would be ideal, let our administrators make the decision.

Hi, is there any update on this?

We also have a similar case where a customer wants to add screenshots under 'Actual' and NOT in 'Steps'.

The issue also is that with screenshots added in 'actual' they do not appear in 'Test Results Detail Report'

’Do you want to save the changes to test planning?’ --> YES

In case changes done also to test steps (description or expected fields) and tester would like to save them, those changes are now stored both to STEP and DESSTEPS tables. And this is like it should be, changes should be stored both to test run/steps and test design steps.

But in Manual Runner the text and print screen attached to Actuals field should be always stored ONLY to STEPS table because that is information related to test execution (not to test planning and DESSTEPS)

• Now the text written to Actuals is stored to STEPS table (ST_ACTUAL field) and not to DESSTEPS (as Actuals is not a concept of test planning, it relates to test execution)
• But the the print screen attached to same Actual field in Manual Runner is store both to STEPS and DESSTEPS and this is wrong.

It is very confusing to the tester to see old test result(s) attached to the test step in Test Plan or during the next test execution run.

If database structure cannot be changed, would it be possible to implement a fix to ALM where attachments/print screens related to step level test execution would not be visible in test design steps? (both in Test Plan and in Manual Runner)

You mentioned  that 'This 'problem' exists in the product from day one', but I need to disagree here. It has not been always possible to attach print screens to Actual field in Manual Runner ;-).  Our customers are heavily demanding a fix to this problem to be delivered, it is not working correctly from ALM testers perspective. The concept of 'Actual' is related only to test execution and runs, and should not effect on test case design.