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
I think it makes sense that snake cased params are also converted (_ replaced by blank), so the report looks like
Scenario: test params mapping
Given duns lookup service with user "user" password "password"
When service params are set <param and value>
Then service submission params contain <expectedField>
Cases:
| # | param and value | expectedField | Status |
+---+----------------------+-----------------+---------+
| 1 | name/siemens | Name | Success |
| 2 | country_isoAlpha2/DE | Country_Code | Success |
| 3 | city/Mannheim | Town | Success |
| 4 | zipCode/12345 | Post_Code | Success |
| 5 | dunsNumber/12345 | DnB_DUNS_Number | Success |
instead of
Scenario: test params mapping
Given duns lookup service with user "user" password "password"
When service params are set <param_and_value>
Then service submission params contain <expectedField>
Cases:
| # | param_and_value | expectedField | Status |
+---+----------------------+-----------------+---------+
| 1 | name/siemens | Name | Success |
| 2 | country_isoAlpha2/DE | Country_Code | Success |
| 3 | city/Mannheim | Town | Success |
| 4 | zipCode/12345 | Post_Code | Success |
| 5 | dunsNumber/12345 | DnB_DUNS_Number | Success |
What do you think?
The text was updated successfully, but these errors were encountered:
Hi Jan,
I think it makes sense that snake cased params are also converted (_ replaced by blank), so the report looks like
instead of
What do you think?
The text was updated successfully, but these errors were encountered: