Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.142	02 wrz 2021, 20:16

	Steps	Scenarios	Features
User	665	1	2	0	0	668	87	1	88	26m 59s 615ms	Failed

Scenario Outline Check if it possible to edit user by my account. User must exist in the system

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" 2s 672ms

When Edit user by my account 1s 649ms

And Wait "2" seconds 2s

Then Check if user details are successfully edited by my account tab 6s 406ms

Scenario Outline Check if it possible to edit user by my account. User must exist in the system

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" 7s 217ms

When Edit user by my account 1s 428ms

And Wait "2" seconds 2s

Then Check if user details are successfully edited by my account tab 3s 779ms

Scenario Outline Check if it possible to edit user by my account. User must exist in the system

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" 2s 273ms

When Edit user by my account 1s 408ms

And Wait "2" seconds 2s

Then Check if user details are successfully edited by my account tab 2s 923ms

Scenario Outline Check if it possible to edit user by my account. User must exist in the system

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "keeeper-admin" 2s 300ms

When Edit user by my account 1s 422ms

And Wait "2" seconds 2s

Then Check if user details are successfully edited by my account tab 3s 928ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 9s 592ms

And Delete invitations with email "automaty@test.pl" 136ms

And Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_CARRIER_INVITATION" 6s 922ms

When Go to "USERS_TAB" 3s 011ms

When Delete user "automaty@test.pl" 6s 164ms

Then Success alert is displayed 100ms

And User "is not" displayed in users list "automaty@test.pl" 16s 514ms

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 437ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-lantmannen" and set token of apiUsername "super-admin-lantmannen" 5s 341ms

And Delete invitations with email "automaty@test.pl" 112ms

And Create and accept invitation by JSON file as "super-admin-lantmannen" for "automaty@test.pl" "CREATE_CARRIER_INVITATION" 5s 039ms

When Go to "USERS_TAB" 2s 743ms

When Delete user "automaty@test.pl" 5s 671ms

Then Success alert is displayed 096ms

And User "is not" displayed in users list "automaty@test.pl" 16s 519ms

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 403ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-pgf" and set token of apiUsername "super-admin-pgf" 6s 118ms

And Delete invitations with email "automaty@test.pl" 095ms

And Create and accept invitation by JSON file as "super-admin-pgf" for "automaty@test.pl" "CREATE_CARRIER_INVITATION" 3s 817ms

When Go to "USERS_TAB" 2s 841ms

When Delete user "automaty@test.pl" 5s 487ms

Then Success alert is displayed 107ms

And User "is not" displayed in users list "automaty@test.pl" 16s 491ms

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 410ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-pgf" and set token of apiUsername "super-admin-pgf" 2s 528ms

And Delete invitations with email "automaty@test.pl" 107ms

And Create and accept invitation by JSON file as "super-admin-pgf" for "automaty@test.pl" "CREATE_SUPPLIER_INVITATION" 3s 647ms

When Go to "USERS_TAB" 1s 440ms

When Delete user "automaty@test.pl" 5s 417ms

Then Success alert is displayed 093ms

And User "is not" displayed in users list "automaty@test.pl" 16s 531ms

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 663ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-adama" and set token of apiUsername "super-admin-adama" 9s 227ms

And Delete invitations with email "automaty@test.pl" 105ms

And Create and accept invitation by JSON file as "super-admin-adama" for "automaty@test.pl" "CREATE_SUPPLIER_INVITATION" 3s 370ms

When Go to "USERS_TAB" 2s 821ms

When Delete user "automaty@test.pl" 5s 386ms

Then Success alert is displayed 096ms

And User "is not" displayed in users list "automaty@test.pl" 16s 528ms

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 440ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 5s 275ms

And Delete invitations with email "automaty@test.pl" 104ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_CARRIER_INVITATION" 4s 574ms

When Go to "USERS_TAB" 3s 012ms

When Delete user "automaty@test.pl" 5s 650ms

Then Success alert is displayed 103ms

And User "is not" displayed in users list "automaty@test.pl" 16s 515ms

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 398ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 539ms

And Delete invitations with email "automaty@test.pl" 096ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_SUPPLIER_INVITATION" 4s 641ms

When Go to "USERS_TAB" 1s 508ms

When Delete user "automaty@test.pl" 5s 669ms

Then Success alert is displayed 105ms

And User "is not" displayed in users list "automaty@test.pl" 16s 552ms

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 409ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 13s 579ms

And Delete invitations with email "automaty@test.pl" 102ms

And Create and accept invitation by JSON file as "super-admin-hochland" for "automaty@test.pl" "CREATE_CARRIER_INVITATION" 7s 716ms

When Go to "USERS_TAB" 3s 231ms

When Delete user "automaty@test.pl" 6s 142ms

Then Success alert is displayed 097ms

And User "is not" displayed in users list "automaty@test.pl" 16s 511ms

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 424ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 006ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 339ms

And Delete invitations with email "automaty@test.pl" 088ms

And Create and accept invitation by JSON file as "super-admin-hochland" for "automaty@test.pl" "CREATE_SUPPLIER_INVITATION" 6s 461ms

When Go to "USERS_TAB" 1s 833ms

When Delete user "automaty@test.pl" 5s 842ms

Then Success alert is displayed 089ms

And User "is not" displayed in users list "automaty@test.pl" 16s 513ms

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 428ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 2s 973ms

And Delete invitations with email "automaty@test.pl" 100ms

And Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_SUPPLIER_INVITATION" 5s 306ms

When Go to "USERS_TAB" 1s 870ms

When Delete user "automaty@test.pl" 5s 633ms

Then Success alert is displayed 080ms

And User "is not" displayed in users list "automaty@test.pl" 16s 531ms

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 430ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login as "super-admin-pgf" and set token of apiUsername "super-admin-pgf" 2s 607ms

And Delete invitations with email "automaty@test.pl" 106ms

And Create and accept invitation by JSON file as "super-admin-pgf" for "automaty@test.pl" "CREATE_ADMIN_INVITATION" 3s 353ms

When Go to "USERS_TAB" 1s 450ms

When Delete user "automaty@test.pl" 5s 377ms

Then Success alert is displayed 091ms

And User "not" displayed in users list "automaty@test.pl" 1s 430ms

Hooks

After Hooks.deleteUserAfterTest() 304ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-pgf" and set token of apiUsername "super-admin-pgf" 2s 442ms

And Delete invitations with email "automaty@test.pl" 097ms

And Create and accept invitation by JSON file as "super-admin-pgf" for "automaty@test.pl" "CREATE_PRODUCER_INVITATION" 3s 159ms

When Go to "USERS_TAB" 1s 452ms

When Delete user "automaty@test.pl" 5s 366ms

Then Success alert is displayed 092ms

And User "not" displayed in users list "automaty@test.pl" 1s 458ms

Hooks

After Hooks.deleteUserAfterTest() 286ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-pgf" and set token of apiUsername "super-admin-pgf" 2s 490ms

And Delete invitations with email "automaty@test.pl" 093ms

And Create and accept invitation by JSON file as "super-admin-pgf" for "automaty@test.pl" "CREATE_WAREHOUSE_MANAGER_INVITATION" 3s 142ms

When Go to "USERS_TAB" 1s 462ms

When Delete user "automaty@test.pl" 5s 408ms

Then Success alert is displayed 089ms

And User "not" displayed in users list "automaty@test.pl" 1s 483ms

Hooks

After Hooks.deleteUserAfterTest() 278ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-pgf" and set token of apiUsername "super-admin-pgf" 2s 466ms

And Delete invitations with email "automaty@test.pl" 099ms

And Create and accept invitation by JSON file as "super-admin-pgf" for "automaty@test.pl" "CREATE_WAREHOUSEMAN_INVITATION" 3s 129ms

When Go to "USERS_TAB" 1s 512ms

When Delete user "automaty@test.pl" 5s 379ms

Then Success alert is displayed 089ms

And User "not" displayed in users list "automaty@test.pl" 1s 468ms

Hooks

After Hooks.deleteUserAfterTest() 292ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-adama" and set token of apiUsername "super-admin-adama" 2s 594ms

And Delete invitations with email "automaty@test.pl" 099ms

And Create and accept invitation by JSON file as "super-admin-adama" for "automaty@test.pl" "CREATE_ADMIN_INVITATION" 3s 755ms

When Go to "USERS_TAB" 1s 582ms

When Delete user "automaty@test.pl" 5s 446ms

Then Success alert is displayed 091ms

And User "not" displayed in users list "automaty@test.pl" 1s 446ms

Hooks

After Hooks.deleteUserAfterTest() 273ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-adama" and set token of apiUsername "super-admin-adama" 2s 687ms

And Delete invitations with email "automaty@test.pl" 101ms

And Create and accept invitation by JSON file as "super-admin-adama" for "automaty@test.pl" "CREATE_PRODUCER_INVITATION" 3s 081ms

When Go to "USERS_TAB" 1s 503ms

When Delete user "automaty@test.pl" 5s 411ms

Then Success alert is displayed 069ms

And User "not" displayed in users list "automaty@test.pl" 1s 433ms

Hooks

After Hooks.deleteUserAfterTest() 310ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-adama" and set token of apiUsername "super-admin-adama" 2s 701ms

And Delete invitations with email "automaty@test.pl" 104ms

And Create and accept invitation by JSON file as "super-admin-adama" for "automaty@test.pl" "CREATE_WAREHOUSEMAN_INVITATION" 2s 851ms

When Go to "USERS_TAB" 1s 555ms

When Delete user "automaty@test.pl" 5s 319ms

Then Success alert is displayed 105ms

And User "not" displayed in users list "automaty@test.pl" 1s 496ms

Hooks

After Hooks.deleteUserAfterTest() 301ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-adama" and set token of apiUsername "super-admin-adama" 2s 574ms

And Delete invitations with email "automaty@test.pl" 097ms

And Create and accept invitation by JSON file as "super-admin-adama" for "automaty@test.pl" "CREATE_BUYER_INVITATION" 2s 877ms

When Go to "USERS_TAB" 1s 563ms

When Delete user "automaty@test.pl" 5s 337ms

Then Success alert is displayed 081ms

And User "not" displayed in users list "automaty@test.pl" 1s 477ms

Hooks

After Hooks.deleteUserAfterTest() 299ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 480ms

And Delete invitations with email "automaty@test.pl" 093ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_ADMIN_INVITATION" 4s 986ms

When Go to "USERS_TAB" 1s 494ms

When Delete user "automaty@test.pl" 5s 702ms

Then Success alert is displayed 086ms

And User "not" displayed in users list "automaty@test.pl" 1s 485ms

Hooks

After Hooks.deleteUserAfterTest() 275ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 459ms

And Delete invitations with email "automaty@test.pl" 096ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_PRODUCER_INVITATION" 4s 756ms

When Go to "USERS_TAB" 1s 485ms

When Delete user "automaty@test.pl" 5s 602ms

Then Success alert is displayed 089ms

And User "not" displayed in users list "automaty@test.pl" 1s 450ms

Hooks

After Hooks.deleteUserAfterTest() 295ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 480ms

And Delete invitations with email "automaty@test.pl" 100ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_GUARD_INVITATION" 4s 463ms

When Go to "USERS_TAB" 1s 512ms

When Delete user "automaty@test.pl" 5s 604ms

Then Success alert is displayed 072ms

And User "not" displayed in users list "automaty@test.pl" 1s 457ms

Hooks

After Hooks.deleteUserAfterTest() 298ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 596ms

And Delete invitations with email "automaty@test.pl" 109ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_TRADESMAN_INVITATION" 4s 532ms

When Go to "USERS_TAB" 1s 593ms

When Delete user "automaty@test.pl" 5s 614ms

Then Success alert is displayed 085ms

And User "not" displayed in users list "automaty@test.pl" 1s 485ms

Hooks

After Hooks.deleteUserAfterTest() 312ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 009ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 446ms

And Delete invitations with email "automaty@test.pl" 102ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_WAREHOUSEMAN_INVITATION" 4s 387ms

When Go to "USERS_TAB" 1s 489ms

When Delete user "automaty@test.pl" 5s 794ms

Then Success alert is displayed 096ms

And User "not" displayed in users list "automaty@test.pl" 1s 499ms

Hooks

After Hooks.deleteUserAfterTest() 314ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 556ms

And Delete invitations with email "automaty@test.pl" 102ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_SORTER_INVITATION" 4s 657ms

When Go to "USERS_TAB" 1s 499ms

When Delete user "automaty@test.pl" 5s 576ms

Then Success alert is displayed 082ms

And User "not" displayed in users list "automaty@test.pl" 1s 454ms

Hooks

After Hooks.deleteUserAfterTest() 278ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 511ms

And Delete invitations with email "automaty@test.pl" 112ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_SQUARE_MANAGER_INVITATION" 4s 393ms

When Go to "USERS_TAB" 1s 483ms

When Delete user "automaty@test.pl" 5s 552ms

Then Success alert is displayed 085ms

And User "not" displayed in users list "automaty@test.pl" 1s 454ms

Hooks

After Hooks.deleteUserAfterTest() 292ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 600ms

And Delete invitations with email "automaty@test.pl" 106ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_OPERATOR_INVITATION" 4s 314ms

When Go to "USERS_TAB" 1s 544ms

When Delete user "automaty@test.pl" 5s 564ms

Then Success alert is displayed 080ms

And User "not" displayed in users list "automaty@test.pl" 1s 475ms

Hooks

After Hooks.deleteUserAfterTest() 304ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 500ms

And Delete invitations with email "automaty@test.pl" 108ms

And Create and accept invitation by JSON file as "super-admin-hochland" for "automaty@test.pl" "CREATE_ADMIN_INVITATION" 8s 672ms

When Go to "USERS_TAB" 1s 884ms

When Delete user "automaty@test.pl" 6s 742ms

Then Success alert is displayed 098ms

And User "not" displayed in users list "automaty@test.pl" 1s 465ms

Hooks

After Hooks.deleteUserAfterTest() 296ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 396ms

And Delete invitations with email "automaty@test.pl" 106ms

And Create and accept invitation by JSON file as "super-admin-hochland" for "automaty@test.pl" "CREATE_BUYER_INVITATION" 6s 889ms

When Go to "USERS_TAB" 1s 832ms

When Delete user "automaty@test.pl" 5s 964ms

Then Success alert is displayed 100ms

And User "not" displayed in users list "automaty@test.pl" 1s 457ms

Hooks

After Hooks.deleteUserAfterTest() 283ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 273ms

And Delete invitations with email "automaty@test.pl" 105ms

And Create and accept invitation by JSON file as "super-admin-hochland" for "automaty@test.pl" "CREATE_GUARD_INVITATION" 7s 727ms

When Go to "USERS_TAB" 1s 772ms

When Delete user "automaty@test.pl" 6s 252ms

Then Success alert is displayed 072ms

And User "not" displayed in users list "automaty@test.pl" 1s 446ms

Hooks

After Hooks.deleteUserAfterTest() 299ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 407ms

And Delete invitations with email "automaty@test.pl" 095ms

And Create and accept invitation by JSON file as "super-admin-hochland" for "automaty@test.pl" "CREATE_LAB_EMPLOYEE_INVITATION" 7s 866ms

When Go to "USERS_TAB" 1s 748ms

When Delete user "automaty@test.pl" 6s 387ms

Then Success alert is displayed 107ms

And User "not" displayed in users list "automaty@test.pl" 1s 483ms

Hooks

After Hooks.deleteUserAfterTest() 276ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 515ms

And Delete invitations with email "automaty@test.pl" 098ms

And Create and accept invitation by JSON file as "super-admin-hochland" for "automaty@test.pl" "CREATE_PRODUCER_INVITATION" 6s 632ms

When Go to "USERS_TAB" 1s 764ms

When Delete user "automaty@test.pl" 5s 847ms

Then Success alert is displayed 073ms

And User "not" displayed in users list "automaty@test.pl" 1s 442ms

Hooks

After Hooks.deleteUserAfterTest() 295ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 533ms

And Delete invitations with email "automaty@test.pl" 096ms

And Create and accept invitation by JSON file as "super-admin-hochland" for "automaty@test.pl" "CREATE_SALES_EMPLOYEE_INVITATION" 6s 405ms

When Go to "USERS_TAB" 1s 732ms

When Delete user "automaty@test.pl" 5s 932ms

Then Success alert is displayed 082ms

And User "not" displayed in users list "automaty@test.pl" 1s 407ms

Hooks

After Hooks.deleteUserAfterTest() 312ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 676ms

And Delete invitations with email "automaty@test.pl" 101ms

And Create and accept invitation by JSON file as "super-admin-hochland" for "automaty@test.pl" "CREATE_SUPPLY_EMPLOYEE_INVITATION" 7s 281ms

When Go to "USERS_TAB" 1s 996ms

When Delete user "automaty@test.pl" 6s 011ms

Then Success alert is displayed 099ms

And User "not" displayed in users list "automaty@test.pl" 1s 491ms

Hooks

After Hooks.deleteUserAfterTest() 294ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 439ms

And Delete invitations with email "automaty@test.pl" 097ms

And Create and accept invitation by JSON file as "super-admin-hochland" for "automaty@test.pl" "CREATE_WAREHOUSE_MANAGER_INVITATION" 8s 062ms

When Go to "USERS_TAB" 1s 798ms

When Delete user "automaty@test.pl" 6s 429ms

Then Success alert is displayed 106ms

And User "not" displayed in users list "automaty@test.pl" 1s 491ms

Hooks

After Hooks.deleteUserAfterTest() 292ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 559ms

And Delete invitations with email "automaty@test.pl" 100ms

And Create and accept invitation by JSON file as "super-admin-hochland" for "automaty@test.pl" "CREATE_WAREHOUSEMAN_INVITATION" 7s 774ms

When Go to "USERS_TAB" 1s 690ms

When Delete user "automaty@test.pl" 6s 496ms

Then Success alert is displayed 098ms

And User "not" displayed in users list "automaty@test.pl" 1s 459ms

Hooks

After Hooks.deleteUserAfterTest() 308ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 371ms

And Delete invitations with email "automaty@test.pl" 097ms

And Create and accept invitation by JSON file as "super-admin-hochland" for "automaty@test.pl" "CREATE_WORKER_WASTE_INVITATION" 5s 882ms

When Go to "USERS_TAB" 1s 708ms

When Delete user "automaty@test.pl" 6s 037ms

Then Success alert is displayed 090ms

And User "not" displayed in users list "automaty@test.pl" 1s 475ms

Hooks

After Hooks.deleteUserAfterTest() 283ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 3s 038ms

And Delete invitations with email "automaty@test.pl" 108ms

And Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_ADMIN_INVITATION" 5s 927ms

When Go to "USERS_TAB" 1s 712ms

When Delete user "automaty@test.pl" 5s 761ms

Then Success alert is displayed 067ms

And User "not" displayed in users list "automaty@test.pl" 1s 437ms

Hooks

After Hooks.deleteUserAfterTest() 308ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 2s 856ms

And Delete invitations with email "automaty@test.pl" 097ms

And Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_GUARD_INVITATION" 5s 432ms

When Go to "USERS_TAB" 1s 566ms

When Delete user "automaty@test.pl" 5s 683ms

Then Success alert is displayed 099ms

And User "not" displayed in users list "automaty@test.pl" 1s 465ms

Hooks

After Hooks.deleteUserAfterTest() 294ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 2s 877ms

And Delete invitations with email "automaty@test.pl" 098ms

And Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_OBSERVER_INVITATION" 4s 198ms

When Go to "USERS_TAB" 1s 527ms

When Delete user "automaty@test.pl" 5s 423ms

Then Success alert is displayed 079ms

And User "not" displayed in users list "automaty@test.pl" 1s 456ms

Hooks

After Hooks.deleteUserAfterTest() 293ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 2s 845ms

And Delete invitations with email "automaty@test.pl" 098ms

And Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_PRODUCER_INVITATION" 5s 492ms

When Go to "USERS_TAB" 1s 597ms

When Delete user "automaty@test.pl" 5s 757ms

Then Success alert is displayed 098ms

And User "not" displayed in users list "automaty@test.pl" 1s 446ms

Hooks

After Hooks.deleteUserAfterTest() 299ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 2s 993ms

And Delete invitations with email "automaty@test.pl" 096ms

And Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_PURCHASING_DEPARTMENT_INVITATION" 4s 879ms

When Go to "USERS_TAB" 1s 526ms

When Delete user "automaty@test.pl" 5s 683ms

Then Success alert is displayed 083ms

And User "not" displayed in users list "automaty@test.pl" 1s 458ms

Hooks

After Hooks.deleteUserAfterTest() 310ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 2s 976ms

And Delete invitations with email "automaty@test.pl" 088ms

And Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_SALES_DEPARTMENT_INVITATION" 4s 928ms

When Go to "USERS_TAB" 1s 545ms

When Delete user "automaty@test.pl" 5s 612ms

Then Success alert is displayed 083ms

And User "not" displayed in users list "automaty@test.pl" 1s 488ms

Hooks

After Hooks.deleteUserAfterTest() 300ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 2s 956ms

And Delete invitations with email "automaty@test.pl" 096ms

And Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_SERVICEMAN_INVITATION" 4s 206ms

When Go to "USERS_TAB" 1s 555ms

When Delete user "automaty@test.pl" 5s 471ms

Then Success alert is displayed 082ms

And User "not" displayed in users list "automaty@test.pl" 1s 455ms

Hooks

After Hooks.deleteUserAfterTest() 294ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 2s 930ms

And Delete invitations with email "automaty@test.pl" 097ms

And Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_TRADESMAN_INVITATION" 5s 241ms

When Go to "USERS_TAB" 1s 797ms

When Delete user "automaty@test.pl" 5s 829ms

Then Success alert is displayed 071ms

And User "not" displayed in users list "automaty@test.pl" 1s 439ms

Hooks

After Hooks.deleteUserAfterTest() 279ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 3s 146ms

And Delete invitations with email "automaty@test.pl" 101ms

And Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_WAREHOUSEMAN_INVITATION" 4s 207ms

When Go to "USERS_TAB" 1s 569ms

When Delete user "automaty@test.pl" 5s 531ms

Then Success alert is displayed 091ms

And User "not" displayed in users list "automaty@test.pl" 1s 458ms

Hooks

After Hooks.deleteUserAfterTest() 306ms

Scenario Outline Check if the carrier has disabled the edition of the notifications

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pla1-carrier" and set token of apiUsername "super-admin-skz" 32s 233ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: Nie udalo sie poprawnie zalogowac pla1-carrier (tried for 20 second(s) with 500 MILLISECONDS interval)
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.checkElementIsVisible(BasePage.java:185)
	at Pages.LoginPage.loginAs(LoginPage.java:42)
	at CucumberTests.BaseTest.loginAs(BaseTest.java:100)
	at CucumberTests.LoginTest.loginAsAndSetTokenOfApiUsername(LoginTest.java:83)
	at ✽.Login as "pla1-carrier" and set token of apiUsername "super-admin-skz"(file:Features/Atom/Users/User.feature:85)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //a[text()='Logout'] | //a[text()='Wyloguj']
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: driver.version: unknown
	at org.openqa.selenium.support.ui.ExpectedConditions.lambda$findElement$0(ExpectedConditions.java:882)
	at java.util.Optional.orElseThrow(Optional.java:290)
	at org.openqa.selenium.support.ui.ExpectedConditions.findElement(ExpectedConditions.java:881)
	at org.openqa.selenium.support.ui.ExpectedConditions.access$000(ExpectedConditions.java:43)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:205)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:201)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208)
	at Pages.BasePage.checkElementIsVisible(BasePage.java:185)
	at Pages.LoginPage.loginAs(LoginPage.java:42)
	at CucumberTests.BaseTest.loginAs(BaseTest.java:100)
	at CucumberTests.LoginTest.loginAsAndSetTokenOfApiUsername(LoginTest.java:83)
	at sun.reflect.GeneratedMethodAccessor221.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaStepDefinition.execute(JavaStepDefinition.java:57)
	at cucumber.runner.PickleStepDefinitionMatch.runStep(PickleStepDefinitionMatch.java:50)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.PickleStepTestStep.run(PickleStepTestStep.java:43)
	at cucumber.runner.TestCase.run(TestCase.java:45)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

When Go to my account details 000ms

Then Verify that user has disabled notification 000ms

@deleteUserAfterTest

Scenario Outline Check if it possible to add queues to user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 2s 702ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_SQUARE_MANAGER_INVITATION" 4s 355ms

When Go to "USERS_TAB" 1s 514ms

And Find user "automaty@test.pl" 3s 647ms

And Add queues to user account "opał" 579ms

And Save user details 1s 573ms

And Click edit button in user details page 178ms

Then Verify that the user is assigned the appropriate queues "opał" 238ms

Hooks

After Hooks.deleteUserAfterTest() 379ms

@deleteUserAfterTest

Scenario Outline Check if user has access to the queues

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 2s 595ms

And Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_SORTER_INVITATION" 4s 439ms

When Go to "USERS_TAB" 1s 505ms

And Find user "automaty@test.pl" 3s 632ms

Then Verify that the user is assigned the appropriate queues "igla. okrągłe HDS;trociny" 415ms

Hooks

After Hooks.deleteUserAfterTest() 398ms

@TmsLink=A-8005

Scenario Outline Check if it is not possible to use the previous password when editing it - my account details [A-8005]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-neuca" 10s 500ms

And Go to my account details 356ms

And Open change password form 469ms

When Fill change user password form in my account settings with "NqsB63f7Oq" 830ms

And Click save user details 370ms

Then Check if alert is displayed "Nowe hasło musi być różne od wcześniej wprowadzonego hasła." 675ms

@cleanUserDetailsAfterTest @TmsLink=A-8005.1

Scenario Outline Check if it is not possible to use the previous password when editing it - remind password [A-8005]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skd" 231ms

And Prepare login page 392ms

And Click remind password button 254ms

And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 023ms

And Send remind password form with email "apolloautomattest@gmail.com" 548ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 33s 299ms

And Extract password from mailgun mail 4s 463ms

And Reset password from link 1s 492ms

Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 232ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 920ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-pgf" and set token of apiUsername "super-admin-pgf" 2s 513ms

And Go to "USERS_TAB" 1s 467ms

When Click add user button 320ms

And Add user "automaty1@test.pl" with "Admin" 2s 182ms

And Click save button 149ms

And Set user id 1s 344ms

Then Success alert is displayed 082ms

And Go to "USERS_TAB" 1s 365ms

And User "is" displayed in users list "automaty1@test.pl" 2s 937ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 199ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-pgf" and set token of apiUsername "super-admin-pgf" 2s 465ms

And Go to "USERS_TAB" 1s 445ms

When Click add user button 306ms

And Add user "automaty1@test.pl" with "Logistyk" 2s 369ms

And Click save button 149ms

And Set user id 1s 069ms

Then Success alert is displayed 066ms

And Go to "USERS_TAB" 1s 341ms

And User "is" displayed in users list "automaty1@test.pl" 2s 992ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 201ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-pgf" and set token of apiUsername "super-admin-pgf" 2s 418ms

And Go to "USERS_TAB" 1s 413ms

When Click add user button 276ms

And Add user "automaty1@test.pl" with "Kierownik magazynu" 2s 273ms

And Click save button 159ms

And Set user id 1s 120ms

Then Success alert is displayed 080ms

And Go to "USERS_TAB" 1s 369ms

And User "is" displayed in users list "automaty1@test.pl" 2s 879ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 207ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-pgf" and set token of apiUsername "super-admin-pgf" 2s 429ms

And Go to "USERS_TAB" 1s 417ms

When Click add user button 286ms

And Add user "automaty1@test.pl" with "Pracownik zaopatrzenia" 2s 360ms

And Click save button 158ms

And Set user id 1s 341ms

Then Success alert is displayed 079ms

And Go to "USERS_TAB" 1s 308ms

And User "is" displayed in users list "automaty1@test.pl" 2s 869ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 214ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-pgf" and set token of apiUsername "super-admin-pgf" 2s 578ms

And Go to "USERS_TAB" 1s 436ms

When Click add user button 345ms

And Add user "automaty1@test.pl" with "Magazyn" 2s 325ms

And Click save button 170ms

And Set user id 1s 109ms

Then Success alert is displayed 076ms

And Go to "USERS_TAB" 1s 377ms

And User "is" displayed in users list "automaty1@test.pl" 2s 890ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 210ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-adama" and set token of apiUsername "super-admin-adama" 2s 655ms

And Go to "USERS_TAB" 1s 768ms

When Click add user button 308ms

And Add user "automaty1@test.pl" with "Admin" 2s 374ms

And Click save button 183ms

And Set user id 1s 841ms

Then Success alert is displayed 095ms

And Go to "USERS_TAB" 1s 393ms

And User "is" displayed in users list "automaty1@test.pl" 2s 993ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 207ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-adama" and set token of apiUsername "super-admin-adama" 2s 758ms

And Go to "USERS_TAB" 1s 525ms

When Click add user button 302ms

And Add user "automaty1@test.pl" with "Logistyk" 2s 403ms

And Click save button 179ms

And Set user id 1s 249ms

Then Success alert is displayed 078ms

And Go to "USERS_TAB" 1s 395ms

And User "is" displayed in users list "automaty1@test.pl" 2s 944ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 203ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-adama" and set token of apiUsername "super-admin-adama" 2s 719ms

And Go to "USERS_TAB" 1s 483ms

When Click add user button 273ms

And Add user "automaty1@test.pl" with "Kupiec" 2s 207ms

And Click save button 168ms

And Set user id 948ms

Then Success alert is displayed 071ms

And Go to "USERS_TAB" 1s 391ms

And User "is" displayed in users list "automaty1@test.pl" 2s 945ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 201ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-adama" and set token of apiUsername "super-admin-adama" 2s 700ms

And Go to "USERS_TAB" 1s 452ms

When Click add user button 283ms

And Add user "automaty1@test.pl" with "Magazyn" 2s 268ms

And Click save button 176ms

And Set user id 954ms

Then Success alert is displayed 069ms

And Go to "USERS_TAB" 1s 356ms

And User "is" displayed in users list "automaty1@test.pl" 2s 907ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 232ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 540ms

And Go to "USERS_TAB" 1s 528ms

When Click add user button 314ms

And Add user "automaty1@test.pl" with "Admin" 2s 429ms

And Click save button 190ms

And Set user id 1s 787ms

Then Success alert is displayed 077ms

And Go to "USERS_TAB" 1s 396ms

And User "is" displayed in users list "automaty1@test.pl" 3s 072ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 200ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 635ms

And Go to "USERS_TAB" 1s 569ms

When Click add user button 331ms

And Add user "automaty1@test.pl" with "Logistyk" 2s 434ms

And Click save button 167ms

And Set user id 1s 753ms

Then Success alert is displayed 074ms

And Go to "USERS_TAB" 1s 405ms

And User "is" displayed in users list "automaty1@test.pl" 3s 010ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 203ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 611ms

And Go to "USERS_TAB" 1s 559ms

When Click add user button 478ms

And Add user "automaty1@test.pl" with "Ochrona / Portier" 2s 272ms

And Click save button 177ms

And Set user id 1s 435ms

Then Success alert is displayed 084ms

And Go to "USERS_TAB" 1s 424ms

And User "is" displayed in users list "automaty1@test.pl" 3s 016ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 222ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 615ms

And Go to "USERS_TAB" 1s 530ms

When Click add user button 349ms

And Add user "automaty1@test.pl" with "Obserwator" 2s 352ms

And Click save button 180ms

And Set user id 1s 429ms

Then Success alert is displayed 085ms

And Go to "USERS_TAB" 1s 439ms

And User "is" displayed in users list "automaty1@test.pl" 2s 943ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 195ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 597ms

And Go to "USERS_TAB" 1s 487ms

When Click add user button 319ms

And Add user "automaty1@test.pl" with "Handlowiec" 2s 483ms

And Click save button 145ms

And Set user id 1s 711ms

Then Success alert is displayed 084ms

And Go to "USERS_TAB" 1s 424ms

And User "is" displayed in users list "automaty1@test.pl" 3s 036ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 207ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 553ms

And Go to "USERS_TAB" 1s 552ms

When Click add user button 338ms

And Add user "automaty1@test.pl" with "Magazyn" 2s 386ms

And Click save button 174ms

And Set user id 1s 444ms

Then Success alert is displayed 075ms

And Go to "USERS_TAB" 1s 422ms

And User "is" displayed in users list "automaty1@test.pl" 2s 974ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 211ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 570ms

And Go to "USERS_TAB" 1s 482ms

When Click add user button 300ms

And Add user "automaty1@test.pl" with "Brakarz" 2s 387ms

And Click save button 171ms

And Set user id 1s 429ms

Then Success alert is displayed 089ms

And Go to "USERS_TAB" 1s 421ms

And User "is" displayed in users list "automaty1@test.pl" 2s 987ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 289ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 627ms

And Go to "USERS_TAB" 1s 529ms

When Click add user button 318ms

And Add user "automaty1@test.pl" with "Operator" 2s 554ms

And Click save button 145ms

And Set user id 1s 453ms

Then Success alert is displayed 085ms

And Go to "USERS_TAB" 1s 405ms

And User "is" displayed in users list "automaty1@test.pl" 3s 016ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 202ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skd" and set token of apiUsername "super-admin-skd" 2s 554ms

And Go to "USERS_TAB" 1s 542ms

When Click add user button 342ms

And Add user "automaty1@test.pl" with "Kierownik Placu" 2s 316ms

And Click save button 177ms

And Set user id 1s 444ms

Then Success alert is displayed 080ms

And Go to "USERS_TAB" 1s 447ms

And User "is" displayed in users list "automaty1@test.pl" 2s 952ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 204ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 336ms

And Go to "USERS_TAB" 2s 176ms

When Click add user button 411ms

And Add user "automaty1@test.pl" with "Admin" 2s 351ms

And Click save button 947ms

And Set user id 6s 702ms

Then Success alert is displayed 079ms

And Go to "USERS_TAB" 1s 658ms

And User "is" displayed in users list "automaty1@test.pl" 3s 260ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 202ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 422ms

And Go to "USERS_TAB" 1s 824ms

When Click add user button 368ms

And Add user "automaty1@test.pl" with "Logistyk" 2s 457ms

And Click save button 260ms

And Set user id 3s 941ms

Then Success alert is displayed 093ms

And Go to "USERS_TAB" 1s 688ms

And User "is" displayed in users list "automaty1@test.pl" 3s 215ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 209ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 567ms

And Go to "USERS_TAB" 1s 723ms

When Click add user button 299ms

And Add user "automaty1@test.pl" with "Ochrona / Portier" 2s 398ms

And Click save button 564ms

And Set user id 5s 467ms

Then Success alert is displayed 067ms

And Go to "USERS_TAB" 1s 598ms

And User "is" displayed in users list "automaty1@test.pl" 3s 268ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 208ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 491ms

And Go to "USERS_TAB" 1s 697ms

When Click add user button 323ms

And Add user "automaty1@test.pl" with "Pracownik zaopatrzenia Węgrów" 2s 519ms

And Click save button 459ms

And Set user id 5s 166ms

Then Success alert is displayed 074ms

And Go to "USERS_TAB" 1s 580ms

And User "is" displayed in users list "automaty1@test.pl" 3s 190ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 206ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 334ms

And Go to "USERS_TAB" 1s 699ms

When Click add user button 336ms

And Add user "automaty1@test.pl" with "Kupiec" 2s 503ms

And Click save button 297ms

And Set user id 4s 276ms

Then Success alert is displayed 079ms

And Go to "USERS_TAB" 1s 652ms

And User "is" displayed in users list "automaty1@test.pl" 3s 156ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 210ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 466ms

And Go to "USERS_TAB" 1s 734ms

When Click add user button 272ms

And Add user "automaty1@test.pl" with "Kierownik magazynu" 2s 395ms

And Click save button 762ms

And Set user id 6s 193ms

Then Success alert is displayed 089ms

And Go to "USERS_TAB" 1s 696ms

And User "is" displayed in users list "automaty1@test.pl" 3s 120ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 206ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 407ms

And Go to "USERS_TAB" 1s 715ms

When Click add user button 297ms

And Add user "automaty1@test.pl" with "Pracownik sprzedaży" 2s 389ms

And Click save button 219ms

And Set user id 3s 559ms

Then Success alert is displayed 079ms

And Go to "USERS_TAB" 1s 870ms

And User "is" displayed in users list "automaty1@test.pl" 3s 200ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 202ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 320ms

And Go to "USERS_TAB" 1s 752ms

When Click add user button 346ms

And Add user "automaty1@test.pl" with "Pracownik zaopatrzenia" 2s 457ms

And Click save button 353ms

And Set user id 4s 623ms

Then Success alert is displayed 087ms

And Go to "USERS_TAB" 1s 643ms

And User "is" displayed in users list "automaty1@test.pl" 3s 194ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 204ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 454ms

And Go to "USERS_TAB" 1s 693ms

When Click add user button 292ms

And Add user "automaty1@test.pl" with "Pracownik odczyt" 2s 440ms

And Click save button 656ms

And Set user id 6s 004ms

Then Success alert is displayed 095ms

And Go to "USERS_TAB" 1s 635ms

And User "is" displayed in users list "automaty1@test.pl" 3s 203ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 207ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 565ms

And Go to "USERS_TAB" 1s 662ms

When Click add user button 321ms

And Add user "automaty1@test.pl" with "Magazyn" 2s 411ms

And Click save button 596ms

And Set user id 5s 835ms

Then Success alert is displayed 101ms

And Go to "USERS_TAB" 1s 639ms

And User "is" displayed in users list "automaty1@test.pl" 3s 185ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 217ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 6s 695ms

And Go to "USERS_TAB" 2s 814ms

When Click add user button 302ms

And Add user "automaty1@test.pl" with "Admin" 2s 318ms

And Click save button 176ms

And Set user id 2s 051ms

Then Success alert is displayed 072ms

And Go to "USERS_TAB" 1s 427ms

And User "is" displayed in users list "automaty1@test.pl" 2s 970ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 208ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 806ms

And Go to "USERS_TAB" 1s 496ms

When Click add user button 339ms

And Add user "automaty1@test.pl" with "Logistyk" 2s 461ms

And Click save button 201ms

And Set user id 2s 061ms

Then Success alert is displayed 078ms

And Go to "USERS_TAB" 1s 368ms

And User "is" displayed in users list "automaty1@test.pl" 2s 960ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 182ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 936ms

And Go to "USERS_TAB" 1s 459ms

When Click add user button 395ms

And Add user "automaty1@test.pl" with "Ochrona / Portier" 2s 342ms

And Click save button 151ms

And Set user id 1s 670ms

Then Success alert is displayed 078ms

And Go to "USERS_TAB" 1s 470ms

And User "is" displayed in users list "automaty1@test.pl" 2s 889ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 221ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 811ms

And Go to "USERS_TAB" 1s 471ms

When Click add user button 291ms

And Add user "automaty1@test.pl" with "Kontroler jakości" 2s 369ms

And Click save button 145ms

And Set user id 1s 630ms

Then Success alert is displayed 086ms

And Go to "USERS_TAB" 1s 391ms

And User "is" displayed in users list "automaty1@test.pl" 2s 952ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 207ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 915ms

And Go to "USERS_TAB" 1s 495ms

When Click add user button 324ms

And Add user "automaty1@test.pl" with "Magazyn" 2s 353ms

And Click save button 177ms

And Set user id 1s 625ms

Then Success alert is displayed 096ms

And Go to "USERS_TAB" 1s 350ms

And User "is" displayed in users list "automaty1@test.pl" 2s 962ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 208ms

@deleteCreatedUserAfterTest

Scenario Outline Check if it is possible to add principal user without using invitations

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 923ms

And Go to "USERS_TAB" 1s 548ms

When Click add user button 319ms

And Add user "automaty1@test.pl" with "Spedytor" 2s 374ms

And Click save button 191ms

And Set user id 2s 124ms

Then Success alert is displayed 071ms

And Go to "USERS_TAB" 1s 375ms

And User "is" displayed in users list "automaty1@test.pl" 2s 946ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 222ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
User	665	1	2	0	0	668	87	1	88	26m 59s 615ms	Failed

Feature Report