api-services-portal
api-services-portal copied to clipboard
Namespace to Gateway - Portal testing for new features
Write tests for new features introduced in NS to GW. This work complements #1074 (regression testing).
Test cases which have been identified as part of development work can be logged here and should be reviewed following the completion of #1074.
See https://dpdd.atlassian.net/browse/APS-2681 for a high level summary of changes implemented in NS to GW.
We should decide on a strategy for writing tests - do we continue to write tests around user paths or write tests by component? Or a bit of both? (e.g. adding/updating key user paths, and also adding to component specific pieces like e2e/cypress/tests/16-gwa-cli
)
New feature tests
Gateway details page:
- [ ] Update gateway display name (including invalidation)
Gateway List Page:
- [ ] Created gateway shows up in list
- [ ] Clicking gateway successfully goes to gateway detail page
- [ ] Redirect to Get Started page if user has no gateways
- [ ] Test filter and search functionality separately and together (including no results found)
- [ ] Test Export Gateway Report functionality
- [x] Publishing status shows up correctly
Gateway dropdown selector:
- [ ] Recently used gateway shows up in list
- [ ] Clicking gateway successfully goes to gateway detail page
- [ ] Search returns expected results (or no results)
Gateway Get Started page:
- [ ] If gateways, shows the 'You have Gateways' banner and does not show 'No Gateways' in page
gwa-cli
- [ ]
gateway create
- 4 cases:- [ ] id and display name provided
- [ ] id provided
- [ ] display name provided
- [ ] interactive
- [ ]
generate-config
Service Validation - 4 cases:- [ ] Both interactive and when providing params
- [ ] When service exists and doesn't exist
- [ ]
status --hosts
includes routes - [ ]
gateway list
shows gatewayId and displayName (not yet implemented)