Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding test design #16

Merged
merged 1 commit into from
Feb 27, 2018
Merged

Adding test design #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions docs/design/testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# Testing

## Scenario's

The following test scenario's must be covered by automated tests:

- Creating 1 deployment (all modes, all environments, all storage engines)
- Creating multiple deployments (all modes, all environments, all storage engines),
controlling each individually
- Creating deployment with/without authentication
- Creating deployment with/without TLS

- Updating deployment wrt:
- Number of servers (scaling, up/down)
- Image version (upgrading, downgrading within same minor version range (e.g. 3.2.x))
- Immutable fields (should be reset automatically)

- Resilience:
- Delete individual pods
- Delete individual PVCs
- Delete individual Services
- Delete Node
- Restart Node
- API server unavailable

## Test environments

- Kubernetes clusters
- Single node
- Multi node
- Access control mode (RBAC, ...)
- Persistent volumes ...