Add 'Expected Result' column to ALM Octane's Manual Step & Runner Window

[Prakash Maurya]

Hi Team,

If possible, could you please add the  'Expected Result' column of ALM Octane's Manual Step & Runner Window.

As of now, user only get option to mention: 1) step details & 2) validation point, but there is no option for user to add 'expected result' for manual test steps, whereas post execution test result details window shows columns as: step number, expected result & action result - which contradicts to options available for creating/adding manual test steps.

Thanks & Regards,

Prakash Maurya

[Misty S]

Agreed. This has been a sticking point for our users transitioning from ALM to Octane. We've been recommending that they add comments to their validation test steps to indicate what the expected result should be, but it would be very helpful to have Expected Results as a separate field on the validation steps.

[yael]

@Prakash Maurya @Misty S 
Indeed the model was changed in ALM Octane but we believe that users can achieve the same (and more) with the new approach.
Please take a look at the following post that explains how a test in ALM can be converted to a test in Octane and let us know what you think

https://community.microfocus.com/t5/ALM-Octane-Tips-Information/Manual-test-structure-in-ALM-vs-ALM-Octane/ta-p/2842668

[Prakash Maurya]

@Misty S 

Thanks for sharing your thoughts and link to one of the possible workarounds, but suggested workaround has a flow, that:  for each step in ALM (with step definition and expected result as one step) - there will be 2 steps in Octane (1 step as definition and 2nd step as expected result) and this will increase the overall number of steps for each test case. This will add up to the complexity of test case maintenance.  

[yael]

@Prakash Maurya It is true that the overall number of steps increases, but the total amount of text per test remains the same, so why do you think that the complexity is increased?