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
{{ message }}
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.
...so that I can run it and trust the test results
📖 Additional Details
The existing postman test suites are manually curated and updated manually depending on the test datasets and the tested features. We want a complete test suite and proper traceability of the change in the tests depending on the new features tested.
definitely a should-have but also a nice-to-have to ensure sufficient testing. this may be something we build up over time as we continue to improve our I&T
That sounds good, I really created that for the icebox, in case we have 1) an opportunity to work on that (I&T is a good one) or 2) events which reinforce the need for something like that.
💪 Motivation
...so that I can run it and trust the test results
📖 Additional Details
The existing postman test suites are manually curated and updated manually depending on the test datasets and the tested features. We want a complete test suite and proper traceability of the change in the tests depending on the new features tested.
⚖️ Acceptance Criteria
Given
When I perform
Then I expect
⚙️ Engineering Details
That might be useful to generate programatically a postman collection by using http://www.postmanlabs.com/postman-collection/ to cover the different combination of tests with the different API features, see https://docs.google.com/spreadsheets/d/1I68XtU_TPIKURj2rltSVPzHb3IY-Oo38tj76D44cHE4/edit#gid=0
The text was updated successfully, but these errors were encountered: