Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.143	03 wrz 2021, 07:47

	Steps	Scenarios	Features
User	665	1	2	0	0	668	87	1	88	27m 2s 942ms	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 708ms

When Edit user by my account 1s 800ms

And Wait "2" seconds 2s

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

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 048ms

When Edit user by my account 1s 429ms

And Wait "2" seconds 2s

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

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 145ms

When Edit user by my account 1s 391ms

And Wait "2" seconds 2s

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

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 369ms

When Edit user by my account 1s 365ms

And Wait "2" seconds 2s

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

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

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

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

When Go to "USERS_TAB" 3s 031ms

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

Then Success alert is displayed 090ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 415ms

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

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

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

When Go to "USERS_TAB" 2s 725ms

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

Then Success alert is displayed 091ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 397ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "super-admin-pgf" and set token of apiUsername "super-admin-pgf" 5s 904ms

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 815ms

When Go to "USERS_TAB" 2s 769ms

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

Then Success alert is displayed 093ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 567ms

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

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_SUPPLIER_INVITATION" 3s 696ms

When Go to "USERS_TAB" 1s 385ms

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

Then Success alert is displayed 102ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 401ms

@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" 5s 900ms

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

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

When Go to "USERS_TAB" 2s 824ms

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

Then Success alert is displayed 099ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 534ms

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

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

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

When Go to "USERS_TAB" 2s 924ms

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

Then Success alert is displayed 092ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 435ms

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

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

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

When Go to "USERS_TAB" 1s 475ms

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

Then Success alert is displayed 077ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 419ms

@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" 12s 921ms

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

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

When Go to "USERS_TAB" 3s 231ms

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

Then Success alert is displayed 085ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 399ms

@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" 18s 667ms

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

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

When Go to "USERS_TAB" 1s 842ms

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

Then Success alert is displayed 088ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 404ms

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

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 314ms

When Go to "USERS_TAB" 1s 870ms

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

Then Success alert is displayed 084ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 428ms

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

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

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

When Go to "USERS_TAB" 1s 585ms

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

Then Success alert is displayed 098ms

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

Hooks

After Hooks.deleteUserAfterTest() 291ms

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

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_PRODUCER_INVITATION" 3s 211ms

When Go to "USERS_TAB" 1s 478ms

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

Then Success alert is displayed 073ms

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

Hooks

After Hooks.deleteUserAfterTest() 306ms

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

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

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

When Go to "USERS_TAB" 1s 442ms

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

Then Success alert is displayed 075ms

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

Hooks

After Hooks.deleteUserAfterTest() 287ms

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

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

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

When Go to "USERS_TAB" 1s 468ms

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

Then Success alert is displayed 083ms

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

Hooks

After Hooks.deleteUserAfterTest() 268ms

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

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

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

When Go to "USERS_TAB" 1s 526ms

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

Then Success alert is displayed 080ms

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

Hooks

After Hooks.deleteUserAfterTest() 288ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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_PRODUCER_INVITATION" 3s 175ms

When Go to "USERS_TAB" 1s 511ms

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

Then Success alert is displayed 086ms

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

Hooks

After Hooks.deleteUserAfterTest() 272ms

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

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

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

When Go to "USERS_TAB" 1s 541ms

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

Then Success alert is displayed 072ms

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

Hooks

After Hooks.deleteUserAfterTest() 287ms

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

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

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

When Go to "USERS_TAB" 1s 533ms

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

Then Success alert is displayed 085ms

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

Hooks

After Hooks.deleteUserAfterTest() 306ms

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

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

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

When Go to "USERS_TAB" 1s 536ms

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

Then Success alert is displayed 091ms

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

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 468ms

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_PRODUCER_INVITATION" 4s 742ms

When Go to "USERS_TAB" 1s 468ms

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

Then Success alert is displayed 075ms

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

Hooks

After Hooks.deleteUserAfterTest() 303ms

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

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

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

When Go to "USERS_TAB" 1s 518ms

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

Then Success alert is displayed 093ms

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

Hooks

After Hooks.deleteUserAfterTest() 291ms

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

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_TRADESMAN_INVITATION" 4s 562ms

When Go to "USERS_TAB" 1s 445ms

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

Then Success alert is displayed 077ms

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

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-skd" and set token of apiUsername "super-admin-skd" 2s 414ms

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

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

When Go to "USERS_TAB" 1s 467ms

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

Then Success alert is displayed 096ms

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

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-skd" and set token of apiUsername "super-admin-skd" 2s 617ms

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_SORTER_INVITATION" 4s 545ms

When Go to "USERS_TAB" 1s 489ms

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

Then Success alert is displayed 072ms

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

Hooks

After Hooks.deleteUserAfterTest() 303ms

@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_SQUARE_MANAGER_INVITATION" 4s 371ms

When Go to "USERS_TAB" 1s 516ms

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

Then Success alert is displayed 073ms

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

Hooks

After Hooks.deleteUserAfterTest() 302ms

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

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

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

When Go to "USERS_TAB" 1s 504ms

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

Then Success alert is displayed 080ms

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

Hooks

After Hooks.deleteUserAfterTest() 300ms

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

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

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

When Go to "USERS_TAB" 1s 890ms

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

Then Success alert is displayed 082ms

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

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 430ms

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

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

When Go to "USERS_TAB" 1s 777ms

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

Then Success alert is displayed 091ms

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

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-hochland" and set token of apiUsername "super-admin-hochland" 3s 415ms

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_GUARD_INVITATION" 7s 575ms

When Go to "USERS_TAB" 1s 766ms

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

Then Success alert is displayed 095ms

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

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 275ms

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 927ms

When Go to "USERS_TAB" 1s 756ms

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

Then Success alert is displayed 081ms

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

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 356ms

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

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

When Go to "USERS_TAB" 1s 726ms

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

Then Success alert is displayed 076ms

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

Hooks

After Hooks.deleteUserAfterTest() 306ms

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

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_SALES_EMPLOYEE_INVITATION" 6s 332ms

When Go to "USERS_TAB" 1s 727ms

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

Then Success alert is displayed 085ms

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

Hooks

After Hooks.deleteUserAfterTest() 280ms

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

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

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

When Go to "USERS_TAB" 1s 888ms

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

Then Success alert is displayed 087ms

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

Hooks

After Hooks.deleteUserAfterTest() 287ms

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

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

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

When Go to "USERS_TAB" 1s 754ms

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

Then Success alert is displayed 466ms

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

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 433ms

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_WAREHOUSEMAN_INVITATION" 7s 829ms

When Go to "USERS_TAB" 1s 772ms

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

Then Success alert is displayed 095ms

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

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 299ms

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

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

When Go to "USERS_TAB" 1s 746ms

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

Then Success alert is displayed 078ms

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

Hooks

After Hooks.deleteUserAfterTest() 402ms

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

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

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

When Go to "USERS_TAB" 1s 644ms

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

Then Success alert is displayed 070ms

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

Hooks

After Hooks.deleteUserAfterTest() 284ms

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

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

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

When Go to "USERS_TAB" 1s 550ms

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

Then Success alert is displayed 080ms

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

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-skz" and set token of apiUsername "super-admin-skz" 2s 958ms

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

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

When Go to "USERS_TAB" 1s 577ms

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

Then Success alert is displayed 081ms

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

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-skz" and set token of apiUsername "super-admin-skz" 3s 030ms

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

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

When Go to "USERS_TAB" 1s 519ms

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

Then Success alert is displayed 067ms

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

Hooks

After Hooks.deleteUserAfterTest() 289ms

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

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

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

When Go to "USERS_TAB" 1s 624ms

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

Then Success alert is displayed 090ms

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

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-skz" and set token of apiUsername "super-admin-skz" 2s 907ms

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_SALES_DEPARTMENT_INVITATION" 4s 941ms

When Go to "USERS_TAB" 1s 561ms

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

Then Success alert is displayed 091ms

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

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-skz" and set token of apiUsername "super-admin-skz" 2s 925ms

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 244ms

When Go to "USERS_TAB" 1s 529ms

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

Then Success alert is displayed 068ms

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

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-skz" and set token of apiUsername "super-admin-skz" 2s 775ms

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_TRADESMAN_INVITATION" 5s 134ms

When Go to "USERS_TAB" 1s 726ms

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

Then Success alert is displayed 081ms

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

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 834ms

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 297ms

When Go to "USERS_TAB" 1s 488ms

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

Then Success alert is displayed 084ms

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

Hooks

After Hooks.deleteUserAfterTest() 290ms

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 330ms

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) 000ms

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 420ms

When Go to "USERS_TAB" 1s 501ms

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

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

And Save user details 1s 541ms

And Click edit button in user details page 204ms

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

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 601ms

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

When Go to "USERS_TAB" 1s 490ms

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

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

Hooks

After Hooks.deleteUserAfterTest() 390ms

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

And Go to my account details 311ms

And Open change password form 490ms

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

And Click save user details 333ms

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

@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" 233ms

And Prepare login page 449ms

And Click remind password button 276ms

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

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!" 34s 202ms

And Extract password from mailgun mail 4s 426ms

And Reset password from link 1s 612ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 943ms

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

And Go to "USERS_TAB" 1s 548ms

When Click add user button 325ms

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

And Click save button 166ms

And Set user id 1s 423ms

Then Success alert is displayed 087ms

And Go to "USERS_TAB" 1s 342ms

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

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-pgf" and set token of apiUsername "super-admin-pgf" 2s 450ms

And Go to "USERS_TAB" 1s 404ms

When Click add user button 317ms

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

And Click save button 166ms

And Set user id 1s 112ms

Then Success alert is displayed 084ms

And Go to "USERS_TAB" 1s 363ms

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

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-pgf" and set token of apiUsername "super-admin-pgf" 2s 503ms

And Go to "USERS_TAB" 1s 406ms

When Click add user button 279ms

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

And Click save button 164ms

And Set user id 1s 081ms

Then Success alert is displayed 078ms

And Go to "USERS_TAB" 1s 326ms

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

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) 001ms

Steps

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

And Go to "USERS_TAB" 1s 410ms

When Click add user button 296ms

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

And Click save button 174ms

And Set user id 1s 324ms

Then Success alert is displayed 073ms

And Go to "USERS_TAB" 1s 391ms

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

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-pgf" and set token of apiUsername "super-admin-pgf" 2s 492ms

And Go to "USERS_TAB" 1s 416ms

When Click add user button 267ms

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

And Click save button 163ms

And Set user id 1s 112ms

Then Success alert is displayed 069ms

And Go to "USERS_TAB" 1s 352ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 191ms

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

And Go to "USERS_TAB" 1s 695ms

When Click add user button 287ms

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

And Click save button 209ms

And Set user id 1s 821ms

Then Success alert is displayed 119ms

And Go to "USERS_TAB" 1s 393ms

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

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-adama" and set token of apiUsername "super-admin-adama" 2s 633ms

And Go to "USERS_TAB" 1s 451ms

When Click add user button 262ms

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

And Click save button 162ms

And Set user id 1s 310ms

Then Success alert is displayed 075ms

And Go to "USERS_TAB" 1s 408ms

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

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-adama" and set token of apiUsername "super-admin-adama" 2s 657ms

And Go to "USERS_TAB" 1s 465ms

When Click add user button 267ms

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

And Click save button 161ms

And Set user id 954ms

Then Success alert is displayed 082ms

And Go to "USERS_TAB" 1s 400ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 205ms

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

And Go to "USERS_TAB" 1s 451ms

When Click add user button 279ms

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

And Click save button 147ms

And Set user id 947ms

Then Success alert is displayed 078ms

And Go to "USERS_TAB" 1s 345ms

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

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-skd" and set token of apiUsername "super-admin-skd" 2s 427ms

And Go to "USERS_TAB" 1s 607ms

When Click add user button 353ms

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

And Click save button 175ms

And Set user id 1s 839ms

Then Success alert is displayed 067ms

And Go to "USERS_TAB" 1s 436ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 190ms

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

And Go to "USERS_TAB" 1s 487ms

When Click add user button 294ms

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

And Click save button 159ms

And Set user id 1s 800ms

Then Success alert is displayed 085ms

And Go to "USERS_TAB" 1s 415ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 212ms

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

And Go to "USERS_TAB" 1s 455ms

When Click add user button 309ms

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

And Click save button 148ms

And Set user id 1s 408ms

Then Success alert is displayed 084ms

And Go to "USERS_TAB" 1s 437ms

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

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) 001ms

Steps

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

And Go to "USERS_TAB" 1s 545ms

When Click add user button 383ms

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

And Click save button 174ms

And Set user id 1s 417ms

Then Success alert is displayed 078ms

And Go to "USERS_TAB" 1s 533ms

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

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-skd" and set token of apiUsername "super-admin-skd" 2s 487ms

And Go to "USERS_TAB" 1s 482ms

When Click add user button 352ms

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

And Click save button 184ms

And Set user id 1s 653ms

Then Success alert is displayed 077ms

And Go to "USERS_TAB" 1s 405ms

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

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-skd" and set token of apiUsername "super-admin-skd" 2s 613ms

And Go to "USERS_TAB" 1s 489ms

When Click add user button 386ms

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

And Click save button 176ms

And Set user id 1s 428ms

Then Success alert is displayed 080ms

And Go to "USERS_TAB" 1s 415ms

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

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-skd" and set token of apiUsername "super-admin-skd" 2s 497ms

And Go to "USERS_TAB" 1s 514ms

When Click add user button 344ms

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

And Click save button 186ms

And Set user id 1s 453ms

Then Success alert is displayed 075ms

And Go to "USERS_TAB" 1s 420ms

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

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-skd" and set token of apiUsername "super-admin-skd" 2s 531ms

And Go to "USERS_TAB" 1s 514ms

When Click add user button 283ms

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

And Click save button 155ms

And Set user id 1s 436ms

Then Success alert is displayed 085ms

And Go to "USERS_TAB" 1s 405ms

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

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-skd" and set token of apiUsername "super-admin-skd" 2s 498ms

And Go to "USERS_TAB" 1s 561ms

When Click add user button 359ms

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

And Click save button 171ms

And Set user id 1s 426ms

Then Success alert is displayed 062ms

And Go to "USERS_TAB" 1s 397ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 191ms

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

And Go to "USERS_TAB" 2s 158ms

When Click add user button 604ms

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

And Click save button 905ms

And Set user id 6s 627ms

Then Success alert is displayed 078ms

And Go to "USERS_TAB" 1s 659ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 193ms

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

And Go to "USERS_TAB" 1s 791ms

When Click add user button 274ms

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

And Click save button 255ms

And Set user id 3s 639ms

Then Success alert is displayed 070ms

And Go to "USERS_TAB" 1s 654ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 198ms

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

And Go to "USERS_TAB" 1s 704ms

When Click add user button 274ms

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

And Click save button 539ms

And Set user id 5s 498ms

Then Success alert is displayed 083ms

And Go to "USERS_TAB" 1s 670ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 239ms

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

And Go to "USERS_TAB" 1s 820ms

When Click add user button 295ms

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

And Click save button 557ms

And Set user id 5s 544ms

Then Success alert is displayed 062ms

And Go to "USERS_TAB" 1s 659ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 198ms

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

And Go to "USERS_TAB" 1s 779ms

When Click add user button 696ms

And Add user "automaty1@test.pl" with "Kupiec" 1s 951ms

And Click save button 271ms

And Set user id 4s 176ms

Then Success alert is displayed 083ms

And Go to "USERS_TAB" 1s 663ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 205ms

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

And Go to "USERS_TAB" 1s 683ms

When Click add user button 292ms

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

And Click save button 742ms

And Set user id 5s 979ms

Then Success alert is displayed 091ms

And Go to "USERS_TAB" 1s 610ms

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

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-hochland" and set token of apiUsername "super-admin-hochland" 3s 274ms

And Go to "USERS_TAB" 1s 674ms

When Click add user button 277ms

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

And Click save button 219ms

And Set user id 3s 482ms

Then Success alert is displayed 076ms

And Go to "USERS_TAB" 1s 964ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 180ms

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

And Go to "USERS_TAB" 1s 689ms

When Click add user button 341ms

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

And Click save button 354ms

And Set user id 4s 618ms

Then Success alert is displayed 061ms

And Go to "USERS_TAB" 1s 617ms

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

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 384ms

And Go to "USERS_TAB" 1s 682ms

When Click add user button 292ms

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

And Click save button 700ms

And Set user id 5s 707ms

Then Success alert is displayed 082ms

And Go to "USERS_TAB" 1s 664ms

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

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-hochland" and set token of apiUsername "super-admin-hochland" 3s 441ms

And Go to "USERS_TAB" 1s 711ms

When Click add user button 296ms

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

And Click save button 587ms

And Set user id 5s 711ms

Then Success alert is displayed 086ms

And Go to "USERS_TAB" 1s 637ms

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

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-piast" and set token of apiUsername "super-admin-piast" 6s 678ms

And Go to "USERS_TAB" 2s 877ms

When Click add user button 344ms

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

And Click save button 180ms

And Set user id 2s 072ms

Then Success alert is displayed 081ms

And Go to "USERS_TAB" 1s 368ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 191ms

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

And Go to "USERS_TAB" 1s 489ms

When Click add user button 305ms

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

And Click save button 183ms

And Set user id 2s 135ms

Then Success alert is displayed 074ms

And Go to "USERS_TAB" 1s 401ms

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

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-piast" and set token of apiUsername "super-admin-piast" 2s 752ms

And Go to "USERS_TAB" 1s 433ms

When Click add user button 290ms

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

And Click save button 164ms

And Set user id 1s 676ms

Then Success alert is displayed 085ms

And Go to "USERS_TAB" 1s 348ms

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

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-piast" and set token of apiUsername "super-admin-piast" 2s 850ms

And Go to "USERS_TAB" 1s 490ms

When Click add user button 269ms

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

And Click save button 159ms

And Set user id 1s 542ms

Then Success alert is displayed 091ms

And Go to "USERS_TAB" 1s 361ms

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

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-piast" and set token of apiUsername "super-admin-piast" 2s 753ms

And Go to "USERS_TAB" 1s 494ms

When Click add user button 305ms

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

And Click save button 180ms

And Set user id 1s 598ms

Then Success alert is displayed 077ms

And Go to "USERS_TAB" 1s 566ms

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

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-piast" and set token of apiUsername "super-admin-piast" 2s 742ms

And Go to "USERS_TAB" 1s 457ms

When Click add user button 302ms

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

And Click save button 190ms

And Set user id 2s 069ms

Then Success alert is displayed 074ms

And Go to "USERS_TAB" 1s 376ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 212ms

	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	27m 2s 942ms	Failed

Feature Report