Cucumber Feature Report

All Scenarios

24

Passed Scenarios

17

Failed Scenarios

1

Skipped Scenarios

6

Execution Time: 6m 48s 55ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 44s 651ms 10 2

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

Scenario:
The server is healthy

11s 969ms 19

Then "server" should have a FQDN 386ms

And reverse resolution should work for "server" 666ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 472ms 4

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

And reverse resolution should work for "proxy" 312ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 595ms 4

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

And reverse resolution should work for "sle_minion" 461ms

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

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

@build_host

Scenario:
The build host is healthy

3s 955ms 4

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

And reverse resolution should work for "build_host" 253ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 619ms 4

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

And reverse resolution should work for "ssh_minion" 421ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 123ms 4

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

And reverse resolution should work for "rhlike_minion" 186ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 955ms 4

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

And reverse resolution should work for "deblike_minion" 214ms

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

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

@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

669ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

640ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

649ms 1

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

Feature:Very first settings 4m 26s 369ms 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

665ms 1

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

@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

4m 25s 703ms 1

Given I am authorized for the "Admin" section 4m 25s 703ms Show Error +

                                            
 Net::ReadTimeout with #(TCPSocket:(closed)) (Net::ReadTimeout)
./features/step_definitions/navigation_steps.rb:592:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:460:in `/^I am authorized for the "([^"]*)" section$/'
features/core/srv_first_settings.feature:41:in `I am authorized for the "Admin" section'