-
Notifications
You must be signed in to change notification settings - Fork 181
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
QE: Add smoke tests for Grafana in BV
QE: Add the monitoring server variable and client to relevant places QE: Correct minion name on monitoring server feature QE: Correct scenario tag on smoke tests QE: Restructure monitoring server tests to be its own thing, like proxy QE: Address changes in PR QE: Fix caps in monitoring server
- Loading branch information
1 parent
381a1e3
commit 6036888
Showing
11 changed files
with
142 additions
and
34 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
95 changes: 95 additions & 0 deletions
95
testsuite/features/build_validation/init_clients/monitoring_server.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,95 @@ | ||
# Copyright (c) 2022 SUSE LLC | ||
# Licensed under the terms of the MIT license. | ||
|
||
@monitoring_server | ||
Feature: Bootstrap the monitoring server | ||
|
||
Scenario: Clean up sumaform leftovers on the monitoring server | ||
When I perform a full salt minion cleanup on "monitoring_server" | ||
|
||
Scenario: Log in as admin user | ||
Given I am authorized for the "Admin" section | ||
|
||
Scenario: Bootstrap the monitoring server | ||
When I follow the left menu "Systems > Bootstrapping" | ||
Then I should see a "Bootstrap Minions" text | ||
When I enter the hostname of "monitoring_server" as "hostname" | ||
And I enter "22" as "port" | ||
And I enter "root" as "user" | ||
And I enter "linux" as "password" | ||
And I select "1-monitoring_server_key" from "activationKeys" | ||
And I select the hostname of "proxy" from "proxies" if present | ||
And I click on "Bootstrap" | ||
And I wait until I see "Successfully bootstrapped host!" text | ||
And I wait until onboarding is completed for "monitoring_server" | ||
|
||
Scenario: Check the new bootstrapped monitoring server in System Overview page | ||
When I follow the left menu "Salt > Keys" | ||
Then I should see a "accepted" text | ||
And the Salt master can reach "monitoring_server" | ||
|
||
@proxy | ||
Scenario: Check connection from monitoring server to proxy | ||
Given I am on the Systems overview page of this "monitoring_server" | ||
When I follow "Details" in the content area | ||
And I follow "Connection" in the content area | ||
Then I should see "proxy" short hostname | ||
|
||
@proxy | ||
Scenario: Check registration on proxy of monitoring server | ||
Given I am on the Systems overview page of this "proxy" | ||
When I follow "Details" in the content area | ||
And I follow "Proxy" in the content area | ||
Then I should see "monitoring_server" hostname | ||
|
||
Scenario: Check events history for failures on monitoring server | ||
Given I am on the Systems overview page of this "monitoring_server" | ||
Then I check for failed events on history event page | ||
|
||
Scenario: Test Prometheus formula on monitoring server | ||
Given I am on the Systems overview page of this "monitoring_server" | ||
When I follow "Formulas" in the content area | ||
And I check the "prometheus" formula | ||
And I click on "Save" | ||
Then I wait until I see "Formula saved" text | ||
When I follow "Prometheus" in the content area | ||
And I click on "Expand All Sections" | ||
And I enter "admin" as "Username" | ||
And I enter "admin" as "Password" | ||
And I click on "Save Formula" | ||
Then I should see a "Formula saved" text | ||
When I follow "States" in the content area | ||
And I click on "Apply Highstate" | ||
Then I should see a "Applying the highstate has been scheduled." text | ||
And I wait until event "Apply highstate scheduled by admin" is completed | ||
# Visit monitoring endpoints on the minion | ||
When I wait until "prometheus" service is active on "monitoring_server" | ||
And I visit "Prometheus" endpoint of this "monitoring_server" | ||
|
||
Scenario: Test Grafana formula on monitoring server | ||
Given I am on the Systems overview page of this "monitoring_server" | ||
When I follow "Formulas" in the content area | ||
And I check the "grafana" formula | ||
And I click on "Save" | ||
Then I wait until I see "Formula saved" text | ||
When I follow "Grafana" in the content area | ||
And I click on "Expand All Sections" | ||
And I enter "admin" as "Default admin user" | ||
And I enter "admin" as "Default admin password" | ||
And I click on "Save Formula" | ||
When I follow "States" in the content area | ||
And I click on "Apply Highstate" | ||
Then I should see a "Applying the highstate has been scheduled." text | ||
And I wait until event "Apply highstate scheduled by admin" is completed | ||
# Visit monitoring endpoints on the minion | ||
When I wait until "grafana-server" service is active on "monitoring_server" | ||
And I visit "Grafana" endpoint of this "monitoring_server" | ||
|
||
Scenario: Test Grafana dashboards of monitoring server | ||
When I visit the grafana dashboards of this "monitoring_server" | ||
And I wait until I do not see "Loading Grafana" text | ||
# These are the 4 dashboards created by default when enabling the Grafana formula | ||
Then I should see a "Apache2" text | ||
And I should see a "PostgreSQL database insights" text | ||
And I should see a "Client Systems" text | ||
And I should see a "Server" text |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
# This file describes the order of features in a Build Validation test suite run. | ||
|
||
## Init monitoring server BEGIN ### | ||
|
||
- features/build_validation/init_clients/monitoring_server.feature | ||
|
||
## Init monitoring server END ### |