Overview
This page defines test cases for
NDS-139
-
Getting issue details...
STATUS
.
Global Preconditions
- Kubernetes is running
- NDSLabs API server and GUI are running
- Project has been created
- User is logged in
NDSLabs GUI
Service List
- Preconditions:
- User is logged in to project
- Expected results:
- "Kibana (ELK)" appears in the NDSLabs service list
- Service description appears in tooltip
Add Stack – no existing volumes
- Pre-Conditions
- No existing volumes
- Test Steps
- User selects "Kibana (ELK)" stack from service list, wizard is displayed
- Required services: Kibana, Elastic Search, Logstash, Logspout
- Volumes: ElasticSearch requires a volume
- Expected results
- Stack is created with Kibana, ElasticSearch, Logstash and Logspout
- Stack is in a stopped state
- Volume is created for ElasticSearch service (see Volumes tab)
Add Stack – existing volumes
- Pre-Conditions
- Volume exists from previous ELK stack (see Delete stack – preserve volume)
- Test Steps
- User selects "Kibana (ELK)" stack from service list, wizard is displayed
- Required services: Kibana, Elastic Search, Logstash, Logspout
- Volumes:
- ElasticSearch requires a volume
- Previous volume found: use existing data
- Expected results
- Stack is created with Kibana, ElasticSearch, Logstash and Logspout
- Existing volume is used for ElasticSearch service
- Stack is in a stopped state
- Optional flow – see Restart stack case (volume is reused)
Start Stack
- Pre-Conditions
- Stack has been added
- Stack is stopped
- Test Steps
- Select "Launch Stack"
- Expected results
- All services are started without error (~1 min)
View Container Logs
- Pre-Conditions
- Stack has been started
- Test Steps
- Select "Logs" for each service
- Expected results
- Logs are viewable for each service
- (Logstash logs are empty, which is expected)
View Kibana Interface
- Pre-Conditions
- Stack is started
- Test Steps
- Select endpoint link next to Kibana service name
- Expected results
- Kibana interface is displayed in a new tab or window
- During first use, "Configure an index pattern" page is displayed. Select "Create" button.
- Select discover button > enter search string "logstash" > Save ("Test")
Stop Stack
- Pre-Conditions
- Stack is started
- Test Steps
- Select "Stop Stack"
- Expected results
- All services in stack are stopped (after ~ 1 minute)
- Delete stack and Launch stack buttons are enabled
- Notes:
- You can watch the services terminate via kubectl:
- kubectl --namespace=<ns> get svc,rc,pod
Restart Stack
- Pre-Conditions
- Stack was previously started
- Stack is stopped
- Test Steps
- Select "Launch stack"
- Select "Kibana endpoint"
- Expected results
- Stack is started (~1 minute)
- User is not prompted to "Configure and index pattern"
- Previous data, saved queries, visualizations, etc are available
Delete stack - preserve data
- Pre-Conditions
- Stack is stopped
- Test Steps
- Select "Delete stack"
- Select "Yes, but save the data"
- Expected results
- Stack is deleted, but volume remains (see Volumes tab)
- Optional flow: Add stack – existing volume
Delete stack - delete data
- Pre-Conditions
- Stack is stopped
- Test Steps
- Select "Delete Stack"
- Select "Yes, and delete the data"
- Expected results
- Stack is deleted, volume is removed
Launch stack - Uninitialized image cache
- Pre-Conditions
- All ELK images have been removed from docker image cache
- Test Steps
- Launch stack
- Expected results
- Stack is started without error (~3 min)