You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scenario: validate read access for supplier contact
Given supplier audit which <arg0> for company of supplier contact
And logged in user suma.contact
When user tries to read supplier audit
Then check that object <arg0> exist afterwards
Cases:
| # | arg0 | Status |
+---+--------+---------+
| 1 | is | Success |
| 2 | is not | Success |
Even though the parameters 0 and 1 are the same, I expect arg0 and arg1 to occur since these two parameters are formatted differently.
What I expect:
Scenario: validate read access for supplier contact
Given supplier audit which <arg0> for company of supplier contact
And logged in user suma.contact
When user tries to read supplier audit
Then check that object <arg1> exist afterwards
Cases:
| # | arg0 | arg1 | Status |
+---+--------+----------+---------+
| 1 | is | does | Success |
| 2 | is not | does not | Success |
The text was updated successfully, but these errors were encountered:
That is definitely a bug. Thanks for reporting. Btw. if you compile your test classes with the -parameters option of javac, you will get better placeholder names.
Given the following test
creates the following report:
Scenario: validate read access for supplier contact
Given supplier audit which <arg0> for company of supplier contact
And logged in user suma.contact
When user tries to read supplier audit
Then check that object <arg0> exist afterwards
Cases:
Even though the parameters 0 and 1 are the same, I expect arg0 and arg1 to occur since these two parameters are formatted differently.
What I expect:
Scenario: validate read access for supplier contact
Given supplier audit which <arg0> for company of supplier contact
And logged in user suma.contact
When user tries to read supplier audit
Then check that object <arg1> exist afterwards
Cases:
The text was updated successfully, but these errors were encountered: