MHR Auth Regression Testing
Open
Assets
MHR
QA Regression
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
With the latest Pay product/payment methods updates going into production on March 5, the Pay team is asking product teams to do some regression testing with regards to how their products interact with Auth.
For the MHR specifically, the Pay team would like to kknow what would happen if a QS were to remove the MHR product from their account and then try to re-add it later.
Any other paths/flows to cover in a regression test?
- [ ] ?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.