Figure out how to maintain test NRs for pipeline newman tests
Open
NRO
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Currently NRs are hard coded into pm collections that newman runs.
- this means that when db is refreshed and NRs change that tests will fail
Could have the NR nums put in as globals and test multiple
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the pipeline's Newman tests and the Postman collections where NR values are currently hard-coded. Trace how refreshed database values affect those tests, then define the global-value and multi-NR behavior needed for the suite to remain reliable after a refresh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, postman
- Domain
- ci-cd, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100