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

Update postman collections to avoid editing data in code and "skipped" tests #370

Open
chiragjn opened this issue Jun 10, 2020 · 0 comments

Comments

@chiragjn
Copy link
Contributor

chiragjn commented Jun 10, 2020

Collection runner is setup in a way that requires

  • forming the data to give to newman collection runner to be compiled in the python code
  • newman's concept of "iteration" is not being used correctly right now which causes a lot of "Skipped" tests
  • Need better error messages in the postman test asserts

Ultimately the ideal case would be to

  • Have a collection of all tests
  • Run the collection by providing it multiple data files (each file contains data for 1 entity) and should need to editing or compilation in the Python code. In fact if we can ditch the python code all together that would be best
  • Nothing should show up as "skipped" - either it should pass or it should fail

Right now I don't know if this ideal structure is even possible, maybe we need to maintain 1 collection per entity?

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

No branches or pull requests

1 participant