Cucumber Feature Report

All Scenarios

24

Passed Scenarios

17

Failed Scenarios

1

Skipped Scenarios

6

Execution Time: 2m 21s 867ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 45s 39ms 10 2

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

Scenario:
The server is healthy

11s 974ms 19

Then "server" should have a FQDN 393ms

And reverse resolution should work for "server" 636ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 668ms 4

Then "proxy" should have a FQDN 3s 57ms

And reverse resolution should work for "proxy" 369ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 615ms 4

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

And reverse resolution should work for "sle_minion" 509ms

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

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

@build_host

Scenario:
The build host is healthy

4s 148ms 4

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

And reverse resolution should work for "build_host" 222ms

And "build_host" should communicate with the server using public interface 1s 137ms

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 214ms 4

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

And reverse resolution should work for "ssh_minion" 441ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 769ms 4

Then "rhlike_minion" should have a FQDN 2s 451ms

And reverse resolution should work for "rhlike_minion" 269ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 694ms 4

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

And reverse resolution should work for "deblike_minion" 206ms

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

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

@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

664ms 1

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

@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 657ms 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

651ms 1

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

@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

5ms 1

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

                                            
 unknown keywords: :log_path, :verbose (ArgumentError)
./features/support/env.rb:116:in `block in capybara_register_driver'
./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'