Cucumber Feature Report

All Scenarios

24

Passed Scenarios

17

Failed Scenarios

1

Skipped Scenarios

6

Execution Time: 2m 17s 755ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 43s 361ms 10 2

In order to use the product
I want to be sure to use a sane environment

Scenario:
The server is healthy

11s 694ms 19

Then "server" should have a FQDN 392ms

And reverse resolution should work for "server" 632ms

And the clock from "server" should be exact 682ms

And service "apache2" is enabled on "server" 617ms

And service "apache2" is active on "server" 649ms

And service "cobblerd" is enabled on "server" 622ms

And service "cobblerd" is active on "server" 617ms

And service "rhn-search" is enabled on "server" 613ms

And service "rhn-search" is active on "server" 619ms

And service "salt-api" is enabled on "server" 629ms

And service "salt-api" is active on "server" 615ms

And service "salt-master" is enabled on "server" 621ms

And service "salt-master" is active on "server" 619ms

And service "taskomatic" is enabled on "server" 616ms

And service "taskomatic" is active on "server" 658ms

And socket "tftp" is enabled on "server" 639ms

And socket "tftp" is active on "server" 613ms

And service "tomcat" is enabled on "server" 617ms

And service "tomcat" is active on "server" 615ms

@proxy

Scenario:
The proxy is healthy

4s 526ms 4

Then "proxy" should have a FQDN 2s 997ms

And reverse resolution should work for "proxy" 310ms

And "proxy" should communicate with the server using public interface 938ms

And the clock from "proxy" should be exact 280ms

@sle_minion

Scenario:
The minion is healthy

6s 93ms 4

Then "sle_minion" should have a FQDN 4s 217ms

And reverse resolution should work for "sle_minion" 433ms

And "sle_minion" should communicate with the server using public interface 1s 64ms

And the clock from "sle_minion" should be exact 378ms

@build_host

Scenario:
The build host is healthy

3s 646ms 4

Then "build_host" should have a FQDN 2s 349ms

And reverse resolution should work for "build_host" 208ms

And "build_host" should communicate with the server using public interface 876ms

And the clock from "build_host" should be exact 212ms

@ssh_minion

Scenario:
The SSH minion is healthy

6s 103ms 4

Then "ssh_minion" should have a FQDN 4s 285ms

And reverse resolution should work for "ssh_minion" 401ms

And "ssh_minion" should communicate with the server using public interface 1s 40ms

And the clock from "ssh_minion" should be exact 377ms

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 209ms 4

Then "rhlike_minion" should have a FQDN 1s 964ms

And reverse resolution should work for "rhlike_minion" 190ms

And "rhlike_minion" should communicate with the server using public interface 846ms

And the clock from "rhlike_minion" should be exact 207ms

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 121ms 4

Then "deblike_minion" should have a FQDN 4s 800ms

And reverse resolution should work for "deblike_minion" 224ms

And "deblike_minion" should communicate with the server using public interface 875ms

And the clock from "deblike_minion" should be exact 221ms

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

Then it should be possible to reach the test packages 0s

And it should be possible to reach the build sources 0s

And it should be possible to reach the Docker profiles 0s

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

Then it should be possible to use the HTTP proxy 0s

@auth_registry

Scenario:
The registry with authentication is healthy

678ms 1

Then it should be possible to reach the authenticated registry 678ms

@no_auth_registry

Scenario:
The registry without authentication is healthy

657ms 1

Then it should be possible to reach the not authenticated registry 657ms

@custom_download_endpoint

Scenario:
The custom download endpoint is working

628ms 1

Then it should be possible to use the custom download endpoint 628ms

Feature:Very first settings 1s 127ms 1 1 1

In order to use the product
As the admin user
I want to create the organisation, the first users and set the HTTP proxy

Scenario:
Cleanup Salt files

673ms 1

When I run "rm -Rf /srv/salt/*" on "server" 673ms

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

Given I access the host the first time 0s

When I go to the home page 0s

And I enter "SUSE Test" as "orgName" 0s

And I enter "admin" as "login" 0s

And I enter "admin" as "desiredpassword" 0s

And I enter "admin" as "desiredpasswordConfirm" 0s

And I select "Mr." from "prefix" 0s

And I enter "Admin" as "firstNames" 0s

And I enter "Admin" as "lastName" 0s

And I enter "galaxy-noise@localhost" as "email" 0s

And I click on "Create Organization" 0s

Then I am logged in 0s

Scenario:
Log in as admin user

454ms 1

Given I am authorized for the "Admin" section 454ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:591:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:459:in `/^I am authorized for the "([^"]*)" section$/'
features/core/srv_first_settings.feature:41:in `I am authorized for the "Admin" section'