Cucumber-JVM Reports - Feature: User

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.130	24 sie 2021, 05:52

	Steps	Scenarios	Features
User	646	13	65	0	0	724	76	13	89	24m 52s 299ms	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 667ms

When Edit user by my account 1s 696ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 1s 390ms

And Wait "2" seconds 2s

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

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

When Edit user by my account 1s 451ms

And Wait "2" seconds 2s

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

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 "keeeper-admin" 2s 219ms

When Edit user by my account 1s 394ms

And Wait "2" seconds 2s

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

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

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_CARRIER_INVITATION" 6s 213ms

And Get invited user account data "automaty@test.pl" 4s 179ms

When Go to "USERS_TAB" 2s 968ms

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

Then Success alert is displayed 100ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 573ms

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

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

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

And Get invited user account data "automaty@test.pl" 2s 358ms

When Go to "USERS_TAB" 2s 763ms

When Delete user "automaty@test.pl" 4s 685ms

Then Success alert is displayed 092ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 486ms

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

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_CARRIER_INVITATION" 2s 848ms

And Get invited user account data "automaty@test.pl" 2s 983ms

When Go to "USERS_TAB" 2s 828ms

When Delete user "automaty@test.pl" 4s 480ms

Then Success alert is displayed 091ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 441ms

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

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

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

And Get invited user account data "automaty@test.pl" 2s 858ms

When Go to "USERS_TAB" 1s 404ms

When Delete user "automaty@test.pl" 4s 517ms

Then Success alert is displayed 098ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 444ms

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

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_SUPPLIER_INVITATION" 2s 384ms

And Get invited user account data "automaty@test.pl" 2s 204ms

When Go to "USERS_TAB" 2s 843ms

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

Then Success alert is displayed 086ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 446ms

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

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_CARRIER_INVITATION" 3s 546ms

And Get invited user account data "automaty@test.pl" 2s 617ms

When Go to "USERS_TAB" 2s 914ms

When Delete user "automaty@test.pl" 4s 778ms

Then Success alert is displayed 101ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 482ms

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

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

And Get invited user account data "automaty@test.pl" 2s 825ms

When Go to "USERS_TAB" 1s 583ms

When Delete user "automaty@test.pl" 4s 922ms

Then Success alert is displayed 075ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 471ms

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

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

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

And Get invited user account data "automaty@test.pl" 6s 977ms

When Go to "USERS_TAB" 3s 127ms

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

Then Success alert is displayed 103ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 635ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

And Get invited user account data "automaty@test.pl" 5s 588ms

When Go to "USERS_TAB" 1s 723ms

When Delete user "automaty@test.pl" 4s 903ms

Then Success alert is displayed 095ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 494ms

@deleteUserAndCompanyAfterTest

Scenario Outline Check if it is possible to delete user

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Get invited user account data "automaty@test.pl" 5s 974ms

When Go to "USERS_TAB" 1s 527ms

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

Then Success alert is displayed 074ms

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

Hooks

After Hooks.deleteUserAndCompanyAfterTest() 587ms

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

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_ADMIN_INVITATION" 2s 327ms

And Get invited user account data "automaty@test.pl" 3s 276ms

When Go to "USERS_TAB" 1s 476ms

When Delete user "automaty@test.pl" 4s 459ms

Then Success alert is displayed 078ms

And User "not" displayed in users list "automaty@test.pl" 425ms

Hooks

After Hooks.deleteUserAfterTest() 327ms

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

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_PRODUCER_INVITATION" 2s 170ms

And Get invited user account data "automaty@test.pl" 3s 306ms

When Go to "USERS_TAB" 1s 387ms

When Delete user "automaty@test.pl" 4s 416ms

Then Success alert is displayed 109ms

And User "not" displayed in users list "automaty@test.pl" 428ms

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

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_WAREHOUSE_MANAGER_INVITATION" 2s 151ms

And Get invited user account data "automaty@test.pl" 3s 286ms

When Go to "USERS_TAB" 1s 429ms

When Delete user "automaty@test.pl" 4s 396ms

Then Success alert is displayed 089ms

And User "not" displayed in users list "automaty@test.pl" 486ms

Hooks

After Hooks.deleteUserAfterTest() 315ms

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

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

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

And Get invited user account data "automaty@test.pl" 3s 302ms

When Go to "USERS_TAB" 1s 400ms

When Delete user "automaty@test.pl" 4s 445ms

Then Success alert is displayed 090ms

And User "not" displayed in users list "automaty@test.pl" 498ms

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

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" 2s 719ms

And Get invited user account data "automaty@test.pl" 3s 027ms

When Go to "USERS_TAB" 1s 460ms

When Delete user "automaty@test.pl" 4s 473ms

Then Success alert is displayed 107ms

And User "not" displayed in users list "automaty@test.pl" 447ms

Hooks

After Hooks.deleteUserAfterTest() 344ms

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

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

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

And Get invited user account data "automaty@test.pl" 3s 042ms

When Go to "USERS_TAB" 1s 490ms

When Delete user "automaty@test.pl" 4s 609ms

Then Success alert is displayed 092ms

And User "not" displayed in users list "automaty@test.pl" 474ms

Hooks

After Hooks.deleteUserAfterTest() 340ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

And Get invited user account data "automaty@test.pl" 3s 171ms

When Go to "USERS_TAB" 1s 459ms

When Delete user "automaty@test.pl" 4s 382ms

Then Success alert is displayed 086ms

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

Hooks

After Hooks.deleteUserAfterTest() 349ms

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

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

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

And Get invited user account data "automaty@test.pl" 3s 117ms

When Go to "USERS_TAB" 1s 391ms

When Delete user "automaty@test.pl" 4s 400ms

Then Success alert is displayed 086ms

And User "not" displayed in users list "automaty@test.pl" 476ms

Hooks

After Hooks.deleteUserAfterTest() 351ms

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

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

And Get invited user account data "automaty@test.pl" 2s 600ms

When Go to "USERS_TAB" 1s 512ms

When Delete user "automaty@test.pl" 4s 714ms

Then Success alert is displayed 073ms

And User "not" displayed in users list "automaty@test.pl" 453ms

Hooks

After Hooks.deleteUserAfterTest() 331ms

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

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

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

And Get invited user account data "automaty@test.pl" 2s 180ms

When Go to "USERS_TAB" 1s 486ms

When Delete user "automaty@test.pl" 4s 862ms

Then Success alert is displayed 078ms

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

Hooks

After Hooks.deleteUserAfterTest() 327ms

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

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

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

And Get invited user account data "automaty@test.pl" 2s 131ms

When Go to "USERS_TAB" 1s 508ms

When Delete user "automaty@test.pl" 4s 631ms

Then Success alert is displayed 083ms

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

Hooks

After Hooks.deleteUserAfterTest() 322ms

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

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_TRADESMAN_INVITATION" 3s 596ms

And Get invited user account data "automaty@test.pl" 2s 092ms

When Go to "USERS_TAB" 1s 548ms

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

Then Success alert is displayed 091ms

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

Hooks

After Hooks.deleteUserAfterTest() 327ms

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

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

And Get invited user account data "automaty@test.pl" 2s 374ms

When Go to "USERS_TAB" 1s 521ms

When Delete user "automaty@test.pl" 4s 616ms

Then Success alert is displayed 097ms

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

Hooks

After Hooks.deleteUserAfterTest() 318ms

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

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

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

And Get invited user account data "automaty@test.pl" 2s 756ms

When Go to "USERS_TAB" 1s 518ms

When Delete user "automaty@test.pl" 4s 575ms

Then Success alert is displayed 094ms

And User "not" displayed in users list "automaty@test.pl" 487ms

Hooks

After Hooks.deleteUserAfterTest() 318ms

@deleteUserAfterTest

Scenario Outline Check if it is possible to delete principal user

Hooks

Before Hooks.showScenarioName(Scenario) 005ms

Steps

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

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

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

And Get invited user account data "automaty@test.pl" 2s 926ms

When Go to "USERS_TAB" 1s 517ms

When Delete user "automaty@test.pl" 4s 684ms

Then Success alert is displayed 085ms

And User "not" displayed in users list "automaty@test.pl" 484ms

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

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_OPERATOR_INVITATION" 3s 248ms

And Get invited user account data "automaty@test.pl" 2s 512ms

When Go to "USERS_TAB" 1s 490ms

When Delete user "automaty@test.pl" 4s 695ms

Then Success alert is displayed 086ms

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

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

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_ADMIN_INVITATION" 7s 501ms

And Get invited user account data "automaty@test.pl" 9s 116ms

When Go to "USERS_TAB" 2s 059ms

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

Then Success alert is displayed 098ms

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

Hooks

After Hooks.deleteUserAfterTest() 491ms

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

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

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

And Get invited user account data "automaty@test.pl" 8s 512ms

When Go to "USERS_TAB" 1s 800ms

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

Then Success alert is displayed 108ms

And User "not" displayed in users list "automaty@test.pl" 540ms

Hooks

After Hooks.deleteUserAfterTest() 466ms

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

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

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

And Get invited user account data "automaty@test.pl" 8s 866ms

When Go to "USERS_TAB" 1s 887ms

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

Then Success alert is displayed 095ms

And User "not" displayed in users list "automaty@test.pl" 534ms

Hooks

After Hooks.deleteUserAfterTest() 483ms

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

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_LAB_EMPLOYEE_INVITATION" 6s 837ms

And Get invited user account data "automaty@test.pl" 8s 871ms

When Go to "USERS_TAB" 1s 847ms

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

Then Success alert is displayed 086ms

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

Hooks

After Hooks.deleteUserAfterTest() 509ms

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

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_PRODUCER_INVITATION" 5s 668ms

And Get invited user account data "automaty@test.pl" 8s 334ms

When Go to "USERS_TAB" 2s 135ms

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

Then Success alert is displayed 084ms

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

Hooks

After Hooks.deleteUserAfterTest() 447ms

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

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_SALES_EMPLOYEE_INVITATION" 5s 429ms

And Get invited user account data "automaty@test.pl" 7s 784ms

When Go to "USERS_TAB" 1s 690ms

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

Then Success alert is displayed 122ms

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

Hooks

After Hooks.deleteUserAfterTest() 427ms

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

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_SUPPLY_EMPLOYEE_INVITATION" 6s 050ms

And Get invited user account data "automaty@test.pl" 7s 965ms

When Go to "USERS_TAB" 1s 747ms

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

Then Success alert is displayed 084ms

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

Hooks

After Hooks.deleteUserAfterTest() 424ms

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

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_WAREHOUSE_MANAGER_INVITATION" 6s 981ms

And Get invited user account data "automaty@test.pl" 9s 004ms

When Go to "USERS_TAB" 1s 866ms

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

Then Success alert is displayed 094ms

And User "not" displayed in users list "automaty@test.pl" 492ms

Hooks

After Hooks.deleteUserAfterTest() 528ms

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

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

And Get invited user account data "automaty@test.pl" 8s 759ms

When Go to "USERS_TAB" 1s 708ms

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

Then Success alert is displayed 082ms

And User "not" displayed in users list "automaty@test.pl" 436ms

Hooks

After Hooks.deleteUserAfterTest() 563ms

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

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

And Get invited user account data "automaty@test.pl" 377ms

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <401>.

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:59)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:238)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.getAuthenticationTokenForUser(RestUtil.java:234)
	at Utils.RestUtils.RestUtil.getAuthenticationTokenForUser(RestUtil.java:210)
	at CucumberTests.User.DeleteUserTest.getInvitedUserAccountData(DeleteUserTest.java:34)
	at ✽.Get invited user account data "automaty@test.pl"(file:Features/Atom/Users/User.feature:43)

When Go to "USERS_TAB" 000ms

When Delete user "automaty@test.pl" 000ms

Then Success alert is displayed 000ms

And User "not" displayed in users list "automaty@test.pl" 000ms

Hooks

After Hooks.deleteUserAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteUserAfterTest(Hooks.java:314)
	at sun.reflect.GeneratedMethodAccessor319.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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Hochland Polska Sp. z o.o., NIP: 5660013371. Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:63)
	at CucumberTests.Invitation.RegistrationTest.createAndAcceptInvitationByJSONFileFor(RegistrationTest.java:73)
	at ✽.Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_ADMIN_INVITATION"(file:Features/Atom/Users/User.feature:42)

And Get invited user account data "automaty@test.pl" 000ms

When Go to "USERS_TAB" 000ms

When Delete user "automaty@test.pl" 000ms

Then Success alert is displayed 000ms

And User "not" displayed in users list "automaty@test.pl" 000ms

Hooks

After Hooks.deleteUserAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteUserAfterTest(Hooks.java:314)
	at sun.reflect.GeneratedMethodAccessor319.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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

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_GUARD_INVITATION" 520ms

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Hochland Polska Sp. z o.o., NIP: 5660013371. Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:63)
	at CucumberTests.Invitation.RegistrationTest.createAndAcceptInvitationByJSONFileFor(RegistrationTest.java:73)
	at ✽.Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_GUARD_INVITATION"(file:Features/Atom/Users/User.feature:42)

And Get invited user account data "automaty@test.pl" 000ms

When Go to "USERS_TAB" 000ms

When Delete user "automaty@test.pl" 000ms

Then Success alert is displayed 000ms

And User "not" displayed in users list "automaty@test.pl" 000ms

Hooks

After Hooks.deleteUserAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteUserAfterTest(Hooks.java:314)
	at sun.reflect.GeneratedMethodAccessor319.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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

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" 524ms

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Hochland Polska Sp. z o.o., NIP: 5660013371. Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:63)
	at CucumberTests.Invitation.RegistrationTest.createAndAcceptInvitationByJSONFileFor(RegistrationTest.java:73)
	at ✽.Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_OBSERVER_INVITATION"(file:Features/Atom/Users/User.feature:42)

And Get invited user account data "automaty@test.pl" 000ms

When Go to "USERS_TAB" 000ms

When Delete user "automaty@test.pl" 000ms

Then Success alert is displayed 000ms

And User "not" displayed in users list "automaty@test.pl" 000ms

Hooks

After Hooks.deleteUserAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteUserAfterTest(Hooks.java:314)
	at sun.reflect.GeneratedMethodAccessor319.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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Hochland Polska Sp. z o.o., NIP: 5660013371. Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:63)
	at CucumberTests.Invitation.RegistrationTest.createAndAcceptInvitationByJSONFileFor(RegistrationTest.java:73)
	at ✽.Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_PRODUCER_INVITATION"(file:Features/Atom/Users/User.feature:42)

And Get invited user account data "automaty@test.pl" 000ms

When Go to "USERS_TAB" 000ms

When Delete user "automaty@test.pl" 000ms

Then Success alert is displayed 000ms

And User "not" displayed in users list "automaty@test.pl" 000ms

Hooks

After Hooks.deleteUserAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteUserAfterTest(Hooks.java:314)
	at sun.reflect.GeneratedMethodAccessor319.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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

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_PURCHASING_DEPARTMENT_INVITATION" 515ms

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Hochland Polska Sp. z o.o., NIP: 5660013371. Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:63)
	at CucumberTests.Invitation.RegistrationTest.createAndAcceptInvitationByJSONFileFor(RegistrationTest.java:73)
	at ✽.Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_PURCHASING_DEPARTMENT_INVITATION"(file:Features/Atom/Users/User.feature:42)

And Get invited user account data "automaty@test.pl" 000ms

When Go to "USERS_TAB" 000ms

When Delete user "automaty@test.pl" 000ms

Then Success alert is displayed 000ms

And User "not" displayed in users list "automaty@test.pl" 000ms

Hooks

After Hooks.deleteUserAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteUserAfterTest(Hooks.java:314)
	at sun.reflect.GeneratedMethodAccessor319.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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

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_SALES_DEPARTMENT_INVITATION" 541ms

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Hochland Polska Sp. z o.o., NIP: 5660013371. Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:63)
	at CucumberTests.Invitation.RegistrationTest.createAndAcceptInvitationByJSONFileFor(RegistrationTest.java:73)
	at ✽.Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_SALES_DEPARTMENT_INVITATION"(file:Features/Atom/Users/User.feature:42)

And Get invited user account data "automaty@test.pl" 000ms

When Go to "USERS_TAB" 000ms

When Delete user "automaty@test.pl" 000ms

Then Success alert is displayed 000ms

And User "not" displayed in users list "automaty@test.pl" 000ms

Hooks

After Hooks.deleteUserAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteUserAfterTest(Hooks.java:314)
	at sun.reflect.GeneratedMethodAccessor319.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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

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_SERVICEMAN_INVITATION" 521ms

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Hochland Polska Sp. z o.o., NIP: 5660013371. Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:63)
	at CucumberTests.Invitation.RegistrationTest.createAndAcceptInvitationByJSONFileFor(RegistrationTest.java:73)
	at ✽.Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_SERVICEMAN_INVITATION"(file:Features/Atom/Users/User.feature:42)

And Get invited user account data "automaty@test.pl" 000ms

When Go to "USERS_TAB" 000ms

When Delete user "automaty@test.pl" 000ms

Then Success alert is displayed 000ms

And User "not" displayed in users list "automaty@test.pl" 000ms

Hooks

After Hooks.deleteUserAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteUserAfterTest(Hooks.java:314)
	at sun.reflect.GeneratedMethodAccessor319.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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

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" 530ms

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Hochland Polska Sp. z o.o., NIP: 5660013371. Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:63)
	at CucumberTests.Invitation.RegistrationTest.createAndAcceptInvitationByJSONFileFor(RegistrationTest.java:73)
	at ✽.Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_TRADESMAN_INVITATION"(file:Features/Atom/Users/User.feature:42)

And Get invited user account data "automaty@test.pl" 000ms

When Go to "USERS_TAB" 000ms

When Delete user "automaty@test.pl" 000ms

Then Success alert is displayed 000ms

And User "not" displayed in users list "automaty@test.pl" 000ms

Hooks

After Hooks.deleteUserAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteUserAfterTest(Hooks.java:314)
	at sun.reflect.GeneratedMethodAccessor319.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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

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_WAREHOUSEMAN_INVITATION" 503ms

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Hochland Polska Sp. z o.o., NIP: 5660013371. Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:63)
	at CucumberTests.Invitation.RegistrationTest.createAndAcceptInvitationByJSONFileFor(RegistrationTest.java:73)
	at ✽.Create and accept invitation by JSON file as "super-admin-skz" for "automaty@test.pl" "CREATE_WAREHOUSEMAN_INVITATION"(file:Features/Atom/Users/User.feature:42)

And Get invited user account data "automaty@test.pl" 000ms

When Go to "USERS_TAB" 000ms

When Delete user "automaty@test.pl" 000ms

Then Success alert is displayed 000ms

And User "not" displayed in users list "automaty@test.pl" 000ms

Hooks

After Hooks.deleteUserAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteUserAfterTest(Hooks.java:314)
	at sun.reflect.GeneratedMethodAccessor319.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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

When Go to my account details 461ms

Then Verify that user has disabled notification 15s 036ms

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Hochland Polska Sp. z o.o., NIP: 5660013371. Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:63)
	at CucumberTests.Invitation.RegistrationTest.createAndAcceptInvitationByJSONFileFor(RegistrationTest.java:73)
	at ✽.Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_SQUARE_MANAGER_INVITATION"(file:Features/Atom/Users/User.feature:97)

And Get invited user account data "automaty@test.pl" 000ms

When Go to "USERS_TAB" 000ms

And Find user "automaty@test.pl" 000ms

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

And Save user details 000ms

And Click edit button in user details page 000ms

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

Hooks

After Hooks.deleteUserAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteUserAfterTest(Hooks.java:314)
	at sun.reflect.GeneratedMethodAccessor319.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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Hochland Polska Sp. z o.o., NIP: 5660013371. Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:63)
	at CucumberTests.Invitation.RegistrationTest.createAndAcceptInvitationByJSONFileFor(RegistrationTest.java:73)
	at ✽.Create and accept invitation by JSON file as "super-admin-skd" for "automaty@test.pl" "CREATE_SORTER_INVITATION"(file:Features/Atom/Users/User.feature:112)

And Get invited user account data "automaty@test.pl" 000ms

When Go to "USERS_TAB" 000ms

And Find user "automaty@test.pl" 000ms

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

Hooks

After Hooks.deleteUserAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteUserAfterTest(Hooks.java:314)
	at sun.reflect.GeneratedMethodAccessor319.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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

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

And Go to my account details 391ms

And Open change password form 494ms

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

And Click save user details 349ms

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

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

And Prepare login page 458ms

And Click remind password button 287ms

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

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

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

And Extract password from mailgun mail 4s 008ms

And Reset password from link 1s 572ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 968ms

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

And Go to "USERS_TAB" 1s 533ms

When Click add user button 309ms

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

And Click save button 176ms

And Set user id 1s 387ms

Then Success alert is displayed 081ms

And Go to "USERS_TAB" 1s 388ms

And User "is" displayed in users list "automaty1@test.pl" 1s 935ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 216ms

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

And Go to "USERS_TAB" 1s 421ms

When Click add user button 292ms

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

And Click save button 138ms

And Set user id 1s 101ms

Then Success alert is displayed 081ms

And Go to "USERS_TAB" 1s 398ms

And User "is" displayed in users list "automaty1@test.pl" 1s 925ms

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

And Go to "USERS_TAB" 1s 439ms

When Click add user button 287ms

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

And Click save button 155ms

And Set user id 1s 143ms

Then Success alert is displayed 081ms

And Go to "USERS_TAB" 1s 395ms

And User "is" displayed in users list "automaty1@test.pl" 1s 979ms

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

And Go to "USERS_TAB" 1s 446ms

When Click add user button 314ms

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

And Click save button 165ms

And Set user id 1s 328ms

Then Success alert is displayed 068ms

And Go to "USERS_TAB" 1s 353ms

And User "is" displayed in users list "automaty1@test.pl" 1s 929ms

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

And Go to "USERS_TAB" 1s 443ms

When Click add user button 298ms

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

And Click save button 152ms

And Set user id 1s 083ms

Then Success alert is displayed 084ms

And Go to "USERS_TAB" 1s 329ms

And User "is" displayed in users list "automaty1@test.pl" 1s 882ms

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

And Go to "USERS_TAB" 1s 680ms

When Click add user button 283ms

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

And Click save button 217ms

And Set user id 1s 812ms

Then Success alert is displayed 092ms

And Go to "USERS_TAB" 1s 434ms

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

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

And Go to "USERS_TAB" 1s 512ms

When Click add user button 308ms

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

And Click save button 157ms

And Set user id 1s 232ms

Then Success alert is displayed 070ms

And Go to "USERS_TAB" 1s 430ms

And User "is" displayed in users list "automaty1@test.pl" 1s 862ms

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

And Go to "USERS_TAB" 1s 451ms

When Click add user button 297ms

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

And Click save button 139ms

And Set user id 983ms

Then Success alert is displayed 078ms

And Go to "USERS_TAB" 1s 373ms

And User "is" displayed in users list "automaty1@test.pl" 1s 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 716ms

And Go to "USERS_TAB" 1s 497ms

When Click add user button 269ms

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

And Click save button 164ms

And Set user id 937ms

Then Success alert is displayed 082ms

And Go to "USERS_TAB" 1s 357ms

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

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

And Go to "USERS_TAB" 1s 547ms

When Click add user button 372ms

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

And Click save button 182ms

And Set user id 1s 810ms

Then Success alert is displayed 073ms

And Go to "USERS_TAB" 1s 589ms

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

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

And Go to "USERS_TAB" 1s 487ms

When Click add user button 347ms

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

And Click save button 158ms

And Set user id 1s 919ms

Then Success alert is displayed 080ms

And Go to "USERS_TAB" 1s 425ms

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

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

And Go to "USERS_TAB" 1s 529ms

When Click add user button 511ms

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

And Click save button 168ms

And Set user id 1s 446ms

Then Success alert is displayed 075ms

And Go to "USERS_TAB" 1s 452ms

And User "is" displayed in users list "automaty1@test.pl" 1s 968ms

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

Steps

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

And Go to "USERS_TAB" 1s 438ms

When Click add user button 300ms

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

And Click save button 150ms

And Set user id 1s 417ms

Then Success alert is displayed 082ms

And Go to "USERS_TAB" 1s 426ms

And User "is" displayed in users list "automaty1@test.pl" 1s 969ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 187ms

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

And Go to "USERS_TAB" 1s 497ms

When Click add user button 395ms

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

And Click save button 180ms

And Set user id 1s 638ms

Then Success alert is displayed 079ms

And Go to "USERS_TAB" 1s 372ms

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

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

And Go to "USERS_TAB" 1s 501ms

When Click add user button 321ms

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

And Click save button 182ms

And Set user id 1s 419ms

Then Success alert is displayed 071ms

And Go to "USERS_TAB" 1s 409ms

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

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

And Go to "USERS_TAB" 1s 502ms

When Click add user button 308ms

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

And Click save button 168ms

And Set user id 1s 451ms

Then Success alert is displayed 092ms

And Go to "USERS_TAB" 1s 462ms

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

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

And Go to "USERS_TAB" 1s 580ms

When Click add user button 398ms

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

And Click save button 167ms

And Set user id 1s 434ms

Then Success alert is displayed 069ms

And Go to "USERS_TAB" 1s 460ms

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

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

And Go to "USERS_TAB" 1s 479ms

When Click add user button 309ms

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

And Click save button 161ms

And Set user id 1s 422ms

Then Success alert is displayed 089ms

And Go to "USERS_TAB" 1s 421ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 192ms

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

And Go to "USERS_TAB" 2s 267ms

When Click add user button 278ms

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

And Click save button 1s 131ms

And Set user id 6s 771ms

Then Success alert is displayed 089ms

And Go to "USERS_TAB" 1s 804ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 194ms

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

And Go to "USERS_TAB" 1s 805ms

When Click add user button 328ms

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

And Click save button 250ms

And Set user id 3s 817ms

Then Success alert is displayed 081ms

And Go to "USERS_TAB" 1s 762ms

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

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

And Go to "USERS_TAB" 1s 806ms

When Click add user button 296ms

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

And Click save button 553ms

And Set user id 5s 422ms

Then Success alert is displayed 089ms

And Go to "USERS_TAB" 1s 704ms

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

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

Steps

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

And Go to "USERS_TAB" 1s 705ms

When Click add user button 272ms

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

And Click save button 488ms

And Set user id 5s 061ms

Then Success alert is displayed 072ms

And Go to "USERS_TAB" 1s 682ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 185ms

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

When Click add user button 306ms

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

And Click save button 307ms

And Set user id 4s 107ms

Then Success alert is displayed 075ms

And Go to "USERS_TAB" 1s 630ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 174ms

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

And Go to "USERS_TAB" 1s 767ms

When Click add user button 320ms

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

And Click save button 820ms

And Set user id 6s 156ms

Then Success alert is displayed 074ms

And Go to "USERS_TAB" 1s 696ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 187ms

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

And Go to "USERS_TAB" 1s 692ms

When Click add user button 348ms

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

And Click save button 235ms

And Set user id 3s 564ms

Then Success alert is displayed 090ms

And Go to "USERS_TAB" 1s 669ms

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

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

And Go to "USERS_TAB" 2s 071ms

When Click add user button 364ms

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

And Click save button 331ms

And Set user id 4s 440ms

Then Success alert is displayed 070ms

And Go to "USERS_TAB" 1s 697ms

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

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

And Go to "USERS_TAB" 1s 738ms

When Click add user button 300ms

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

And Click save button 718ms

And Set user id 5s 758ms

Then Success alert is displayed 091ms

And Go to "USERS_TAB" 1s 672ms

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

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

And Go to "USERS_TAB" 1s 725ms

When Click add user button 300ms

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

And Click save button 641ms

And Set user id 5s 674ms

Then Success alert is displayed 069ms

And Go to "USERS_TAB" 1s 625ms

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

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

And Go to "USERS_TAB" 2s 799ms

When Click add user button 278ms

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

And Click save button 173ms

And Set user id 1s 940ms

Then Success alert is displayed 075ms

And Go to "USERS_TAB" 1s 347ms

And User "is" displayed in users list "automaty1@test.pl" 1s 929ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 225ms

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

And Go to "USERS_TAB" 1s 516ms

When Click add user button 273ms

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

And Click save button 188ms

And Set user id 1s 917ms

Then Success alert is displayed 082ms

And Go to "USERS_TAB" 1s 377ms

And User "is" displayed in users list "automaty1@test.pl" 1s 938ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 233ms

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

And Go to "USERS_TAB" 1s 481ms

When Click add user button 260ms

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

And Click save button 166ms

And Set user id 1s 488ms

Then Success alert is displayed 086ms

And Go to "USERS_TAB" 1s 387ms

And User "is" displayed in users list "automaty1@test.pl" 1s 887ms

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

And Go to "USERS_TAB" 1s 509ms

When Click add user button 277ms

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

And Click save button 177ms

And Set user id 1s 501ms

Then Success alert is displayed 077ms

And Go to "USERS_TAB" 1s 365ms

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

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

And Go to "USERS_TAB" 1s 450ms

When Click add user button 277ms

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

And Click save button 177ms

And Set user id 1s 479ms

Then Success alert is displayed 086ms

And Go to "USERS_TAB" 1s 421ms

And User "is" displayed in users list "automaty1@test.pl" 1s 926ms

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

And Go to "USERS_TAB" 1s 514ms

When Click add user button 339ms

And Add user "automaty1@test.pl" with "Spedycja Piast Cargo" 15s 515ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//li[text()='Spedycja Piast Cargo' and @role='option'] | //li[@role='option']//span[text()='Spedycja Piast Cargo']"}
  (Session info: headless chrome=92.0.4515.131)
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: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.Y8LWut}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 70d7a785ff1f116280ffd51b62a002a5
*** Element info: {Using=xpath, value=//li[text()='Spedycja Piast Cargo' and @role='option'] | //li[@role='option']//span[text()='Spedycja Piast Cargo']}
	at sun.reflect.GeneratedConstructorAccessor215.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.selectOptionFromSelect(BasePage.java:260)
	at CucumberTests.User.CreateUserTest.fillUserForm(CreateUserTest.java:36)
	at ✽.Add user "automaty1@test.pl" with "Spedycja Piast Cargo"(file:Features/Atom/Users/User.feature:153)

And Click save button 000ms

And Set user id 000ms

Then Success alert is displayed 000ms

And Go to "USERS_TAB" 000ms

And User "is" displayed in users list "automaty1@test.pl" 000ms

Hooks

After Hooks.deleteCreatedUserAfterTest() 000ms

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

And Go to "USERS_TAB" 1s 510ms

When Click add user button 344ms

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

And Click save button 177ms

And Set user id 1s 967ms

Then Success alert is displayed 088ms

And Go to "USERS_TAB" 1s 405ms

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

Hooks

After Hooks.deleteCreatedUserAfterTest() 210ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
User	646	13	65	0	0	724	76	13	89	24m 52s 299ms	Failed

Feature Report