Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generated values don't work when setting JSON as table #4

Closed
mikeparcewski opened this issue Mar 3, 2019 · 0 comments
Closed

Generated values don't work when setting JSON as table #4

mikeparcewski opened this issue Mar 3, 2019 · 0 comments

Comments

@mikeparcewski
Copy link
Contributor

Describe the bug
When using a table to set the JSON body, faker values are not transformed.

To Reproduce

  @Smoke @Json @GPath @ResponseMatch
  Scenario: Test setting up JSON as table with generation (FT3)
    Given I am a JSON API consumer
      And I am executing test "BSJ2"
     When I request GET "/mirror"
      And I set the JSON body from values
      | users[0].id        | 1                                    |
      | users[0].name      | {{faker::name.firstName,en-US::n}}   |
      | users[0].favorites | 1,2,3                                |
      | users[0].active    | true                                 |
      | users[1].id        | 2                                    |
      | users[1].name      | Bob                                  |
      | users[1].favorites | 4,7,9                                |
      | users[1].active    | false                                |
     Then I should get a status code of 200
      And the response value of "users[0].name" should equal "{{cache::n}}"

In the above, users[0].name is still {{faker::name.firstName,en-US::n}}

Expected behavior
users[0].name should be replaced by a value generated from faker object

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant