Maintenance Mode Feature Testing
This issue covers code review, manual testing and API testing of the maintenance mode feature leading up to the feature's release.
Please see separate issues for automated test planning, and specific testing events on staging.
Note that some earlier manual testing feedback was provided in the automated test planning issue.
Expected behavior of features in maintenance mode are documented here.
When maintenance mode is enabled:
- Admins can perform certain admin-related write functions
- All users can perform read functions available to their access level
- Except for admins performing certain admin functions, no one can perform write functions
- If a disallowed write function is attempted, the user is notified by appropriate messaging that the function did not succeed
- Users are notified that maintenance mode is enabled
- Geo secondary nodes continue to replicate data
Methods of testing:
- Manual testing on dev instances (gdk, GCP instances)
- API testing
- Code review by team members: the engineers familiar with a group's features would be the best at identifying situations where the current maintenance mode code might NOT block a write to the database. Asking the engineers to list particular actions to for us to test would be more efficient than us trying to break a feature we may not be familiar with.
Deliverables:
-
Feedback/issues based on exploratory testing on single-node site Geo deployment -
Feedback/issues exploratory testing on multi-node site Geo deployment (using GET to spin up Geo instance)
Edited by Aakriti Gupta