Completed

Comma Separated Next Expression doesn't work on SET_VAR command when referencing to LIST

Hasib Rostaiee

July 29, 2022 20:55

Hello,
We have SET_VAR steps that uses Next expression to reference to the LIST elements (which is already defined in the test.) These expressions are comma separated.

After the last upgrade on 7/27/2022 to 9.5.9.2606, the SET_VAR can no longer convert the expressions to the values in the list when it's comma saperated.

Below is the list values:

When using the expression to reference to the list values, it's not getting the values:

This was working fine in previous runs before the upgrade:

Note: If only single expression used in SET_VAR, it will get the value from the list correctly:

The expressions are used according to the guidance of the SET_LIST command:

5 comments

Rex Feizi July 30, 2022 18:06

We are trying to reproduce this. We will get back to you shortly. Meanwhile, could you provide the previous version you were on before the current?

Hasib Rostaiee August 01, 2022 13:10

Thank you Rex,

The previous version was 9.5.7

Joseph Hamdan August 01, 2022 13:33

Hi Hasib,

Thanks for bridging this to our attention. We are working on fixing this issue and will make sure that it does not happen again.

We'll keep you posted once the fix is ready. Have a nice day!

Regards,
Subject7 Team

Joseph Hamdan August 04, 2022 12:49

Hi Hasib,

This issue has been fixed and is targeted to be release by this weekend.

Thanks for reporting it and we appreciate your patience.

Regards,
Subject7 Team

Joseph Hamdan August 10, 2022 09:08

Hi Hasib,

The fix for this issue has been deployed to the latest version currently in production. Once your instance is upgraded, you will be able to generate multiple comma separated values from the lists in Set_Var command. Thank you for reporting this issue, it will be marked as Completed now.

Regards,
Subject7 Team

Please sign in to leave a comment.