Scenario Outline
Check if rejected invitation is visible in rejected tab
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-piast"
241ms
And
Delete invitations with email "automaty31415@test.pl"
099ms
Then
Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION"
1s 383ms
And
Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file
1s 313ms
When
Login as "piast-admin"
5s 075ms
Then
Go to "INVITATIONS_TAB"
711ms
And
Go to invitation details
145ms
Then
Reject invitation by button as user
302ms
When
If user is login then logout
675ms
Then
Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec"
4s 618ms
And
Go to "INVITATIONS_TAB"
491ms
And
Go to "REJECTED_TAB" invitation status tab
279ms
Then
Invitation is displayed on list "automaty31415@test.pl"
509ms
After
Hooks.deleteInvitationAfterTest()
152ms
After
Hooks.cleanUserDetailsAfterTest()
1s 329ms
Scenario Outline
Check if it is possible to invite existing user in order to associate him with principal company [A-7315]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-alrec"
239ms
And
Prepare user "dha1-supplier-2" details with all notifications and "automatyy3333@test.pl" by JSON file
1s 756ms
When
Login as "neuca-admin" and set token of apiUsername "super-admin-neuca"
2s 499ms
And
Go to "INVITATIONS_TAB"
525ms
And
Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL"
2s 936ms
Then
Create invitation success alert is displayed
115ms
After
Hooks.deleteInvitationAfterTest()
215ms
After
Hooks.cleanUserDetailsAfterTest()
1s 334ms
Scenario Outline
Verify that password reset cancel login blockade [A-7286]
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Set token of apiUsername "super-admin-skd"
226ms
And
Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1"
093ms
Given
Failed login as "swiss-krono-delivery-admin-2"
1s 291ms
Then
Verify that login error reason is "auth.invalidLoginOrPassword"
611ms
Given
Try login as "swiss-krono-delivery-admin-2"
1s 372ms
Then
Verify that login error reason is "auth.accountLocked"
276ms
Given
Click remind password button
220ms
And
Prepare user "swiss-krono-delivery-admin-2" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 247ms
And
Send remind password form with email "apolloautomattest@gmail.com"
527ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!"
11s 647ms
And
Extract password reset link from mailgun mail
3s 885ms
And
Reset password from link
1s 370ms
Then
Login as "swiss-krono-delivery-admin-2" with new password
4s 969ms
And
User is successfully logged
028ms
After
Hooks.cleanUserDetailsAfterTest()
939ms
After
Hooks.clearUserPasswordDataAfterTest()
484ms
After
Hooks.rollbackParameters()
096ms
After
Hooks.unlockUsers()
149ms
Scenario Outline
Check if mail was sent to creator after creating advice
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
2s 462ms
And
Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 500ms
And
Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama"
2s 226ms
And
Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama"
001ms
And
Show all transport types
1s 161ms
And
Click button advice in transport table "CONTAINER"
212ms
And
Set advice window in schedule
3s 314ms
And
Fill advice form
17s 024ms
And
Click advice save button and wait for advice form to disappear
33s 839ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!"
6s 916ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 305ms
After
Hooks.deleteTransportAfterTest()
824ms
Scenario Outline
Check if mail was sent to creator after creating advice
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "piast-admin" and set token of apiUsername "super-admin-piast"
2s 628ms
And
Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 197ms
And
Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast"
2s 041ms
And
Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast"
001ms
And
Show all transport types
1s 143ms
And
Click button advice in transport table "DELIVERY"
241ms
And
Set advice window in schedule
3s 441ms
And
Fill advice form
13s 013ms
And
Click advice save button and wait for advice form to disappear
33s 397ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!"
6s 103ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 086ms
After
Hooks.deleteTransportAfterTest()
775ms
Scenario Outline
Check if mail was sent to creator after creating advice
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper"
2s 534ms
And
Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 867ms
And
Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper"
2s 036ms
And
Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper"
001ms
And
Show all transport types
1s 151ms
And
Click button advice in transport table "LOAD"
246ms
And
Set advice window in schedule
3s 300ms
And
Fill advice form
18s 769ms
And
Click advice save button and wait for advice form to disappear
33s 255ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!"
5s 858ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 490ms
After
Hooks.deleteTransportAfterTest()
741ms
Scenario Outline
Check if mail was sent to creator after editing advice
Before
Hooks.showScenarioName(Scenario)
007ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
5s 079ms
And
Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 560ms
And
Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama"
1s 830ms
And
Show all transport types
1s 165ms
And
Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama"
3s 228ms
And
Go to "TRANSPORT_TABLE"
392ms
And
Go to transport details "CONTAINER"
2s 971ms
And
Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama"
001ms
When
Go to transport details "CONTAINER"
3s 520ms
And
Fill transport form
5s 232ms
And
Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama"
001ms
And
Expand advice panel
248ms
And
Edit advice in transport details
17s 663ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 251ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer"
27s 522ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 303ms
After
Hooks.deleteTransportAfterTest()
739ms
Scenario Outline
Check if mail was sent to creator after editing advice
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "piast-admin" and set token of apiUsername "super-admin-piast"
5s 310ms
And
Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 117ms
And
Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast"
1s 976ms
And
Show all transport types
1s 148ms
And
Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast"
3s 603ms
And
Go to "TRANSPORT_TABLE"
399ms
And
Go to transport details "DELIVERY"
3s 083ms
And
Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-piast"
001ms
When
Go to transport details "DELIVERY"
3s 843ms
And
Fill transport form
1m 8s 500ms
And
Set "advice" inputs from JSON file "EDIT_ADVICE_DELIVERY" "super-admin-piast"
001ms
And
Expand advice panel
284ms
And
Edit advice in transport details
8s 074ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 184ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer"
27s 680ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 122ms
After
Hooks.deleteTransportAfterTest()
905ms
Scenario Outline
Check if mail was sent to creator after editing advice
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper"
6s 160ms
And
Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 751ms
And
Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper"
1s 969ms
And
Show all transport types
1s 150ms
And
Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper"
3s 303ms
And
Go to "TRANSPORT_TABLE"
366ms
And
Go to transport details "LOAD"
2s 912ms
And
Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper"
000ms
When
Go to transport details "LOAD"
3s 485ms
And
Fill transport form
28s 695ms
And
Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper"
001ms
And
Expand advice panel
254ms
And
Edit advice in transport details
23s 391ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 250ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer"
2m 42s 250ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 689ms
After
Hooks.deleteTransportAfterTest()
810ms
Scenario Outline
Check if mail was sent to creator after status confirmation
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-skd"
232ms
And
Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 232ms
And
Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd"
2s 852ms
And
Confirm status "REPORTING" by Public API "v1"
545ms
And
Confirm status "ARRIVAL" by Public API "v1"
1s 163ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu"
10s 393ms
Then
Check if user got a mail
000ms
And
Assign Queue to classification resource: "super-admin-skd" "trociny" "CLASSIFICATION"
1s 085ms
And
Assign Place to classification resource: "super-admin-skd" "trociny" "Rozładunek" "UNLOAD"
1s 064ms
And
Confirm status "DEPARTURE" by Public API "v1"
1s 043ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd"
10s 386ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
965ms
After
Hooks.deleteTransportAfterTest()
866ms
Scenario Outline
Check if verification mail was sent to transport creator
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-hochland"
239ms
And
Prepare company "Dostawca Hochland Automat 1" verification email setting "48h"
196ms
And
Prepare user "dha1-supplier-2" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 131ms
And
Login as "dha1-supplier-2" and set token of apiUsername "dha1-supplier-2"
9s 072ms
And
Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2"
17s 012ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji"
1m 44s 845ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 690ms
After
Hooks.deleteTransportAfterTest()
677ms
After
Hooks.rollbackVerificationEmailSettingAfterTest()
402ms
Scenario Outline
Check mail after creating a new auction
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
4s 937ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 210ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 192ms
And
Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama"
3s 611ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja"
10s 426ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 074ms
After
Hooks.deleteTransportAfterTest()
761ms
Scenario Outline
Check mail after loosing auction
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
2s 625ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 422ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 161ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
3s 024ms
And
Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama"
1s 364ms
And
Add a bid "500" to an auction by JSON file as "paa2-carrier" for "super-admin-adama"
1s 895ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia"
10s 386ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 044ms
After
Hooks.deleteTransportAfterTest()
598ms
Scenario Outline
Check mail after bid has been added to auction
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz"
11s 045ms
And
Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 539ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
2s 046ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"
2s 848ms
And
Add a bid "1500" to an auction by JSON file as "pskza1-carrier" for "pskza1-carrier"
1s 041ms
And
Wait till auction end
1m 57s 016ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę"
2m 47s 086ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 386ms
After
Hooks.deleteTransportAfterTest()
630ms
Scenario Outline
Check mail after auction without bids
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
2s 550ms
And
Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 558ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 091ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
3s 054ms
And
Wait till auction end
1m 57s 016ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert"
5s 492ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 410ms
After
Hooks.deleteTransportAfterTest()
709ms
Scenario Outline
Check mail after loosing first place in auction
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
4s 876ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 337ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 120ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
3s 013ms
And
Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama"
1s 077ms
And
Add a bid "500" to an auction by JSON file as "paa2-carrier" for "super-admin-adama"
1s 800ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana"
41s 859ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 074ms
After
Hooks.deleteTransportAfterTest()
662ms
Scenario Outline
Check mail after winning an auction
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
2s 742ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 307ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 108ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
3s 011ms
And
Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama"
1s 006ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie"
1m 50s 467ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 312ms
After
Hooks.deleteTransportAfterTest()
610ms
Scenario Outline
Check mail after accepting minimal price
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
2s 636ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 344ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 086ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
3s 059ms
And
Add a bid "500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama"
1s 762ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie"
5s 315ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 036ms
After
Hooks.deleteTransportAfterTest()
571ms
Scenario Outline
Check mail two hours before auction ends
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "paa1-carrier" and set token of apiUsername "super-admin-adama"
5s 205ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 594ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 165ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes
3s 164ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji"
1m 3s 312ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 072ms
After
Hooks.deleteTransportAfterTest()
665ms
Scenario Outline
Check if mail was sent to after discrepancy report generation
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "hochland-admin" and set token of apiUsername "super-admin-hochland"
3s 206ms
And
Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
4s 294ms
And
Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland"
3s 143ms
And
Go to "TRANSPORT_TABLE"
403ms
And
Go to transport details "DELIVERY"
2s 945ms
And
Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland"
001ms
And
Fill transport form
43s 112ms
And
Open section: "discrepancy-report-panel"
1s 167ms
And
Fill discrepancy report section
52s 441ms
And
Go to transport details "DELIVERY"
2s 830ms
And
Change filled value in details "rodo-acceptance" "checkbox" "true" "0"
1s 596ms
And
Generate discrepancy report
22s 281ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności"
5s 832ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
3s 383ms
After
Hooks.deleteTransportAfterTest()
907ms
Scenario Outline
Check if mail was sent after updating mode of transportation
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-bausch"
238ms
And
Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file
3s 095ms
When
Create default mode of transportation by API with "pba1-carrier"
894ms
Then
Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000"
355ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany"
10s 670ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 462ms
After
Hooks.deleteModeOfTransportationAfterTest()
365ms
Scenario Outline
Check if mail was sent after creating mode of transportation
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-bausch"
261ms
And
Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 906ms
When
Create default mode of transportation by API with "pba1-carrier"
576ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu"
5s 318ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 507ms
After
Hooks.deleteModeOfTransportationAfterTest()
305ms
Scenario Outline
Check if mail was sent to after transport delay
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "hochland-admin" and set token of apiUsername "super-admin-hochland"
9s 215ms
And
Prepare user "pha2-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 081ms
And
Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin"
273ms
And
Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland"
3s 222ms
And
Go to "WAREHOUSE_TAB"
1s 322ms
And
Select warehouse "Serownia"
1s 647ms
And
Set week view
1s 251ms
And
Show yesterday
1s 155ms
And
Move window into the past
444ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na"
21s 634ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 383ms
After
Hooks.deleteTransportAfterTest()
795ms
After
Hooks.rollbackAddedAuthorities()
131ms
Scenario Outline
Check if mail was sent to after transport creation
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
9s 293ms
And
Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 468ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
2s 202ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import"
42s 121ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 114ms
After
Hooks.deleteTransportAfterTest()
598ms
Scenario Outline
Check if mail was sent to after transport creation
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 618ms
And
Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 661ms
And
Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz"
2s 164ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport"
47s 159ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 135ms
After
Hooks.deleteTransportAfterTest()
549ms
Scenario Outline
Check if mail was sent to carrier after transport transfer
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
2s 518ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 670ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 102ms
And
Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true"
34s 765ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację"
5s 630ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 313ms
After
Hooks.deleteTransportAfterTest()
772ms
Scenario Outline
Check if mail was sent to carrier after transport transfer with no confirmation
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
2s 544ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 293ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 105ms
And
Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false"
34s 946ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie"
5s 502ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 138ms
After
Hooks.deleteTransportAfterTest()
637ms
Scenario Outline
Check if mail was sent to carrier after transport transfer in inquiry
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 621ms
And
Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 340ms
And
Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz"
2s 154ms
And
Transfer transport to carrier "Przewoźnik SKZ Automat 1"
34s 747ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację"
6s 090ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 759ms
After
Hooks.deleteTransportAfterTest()
852ms
Scenario Outline
Check mail after loosing inquiry
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 777ms
And
Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
3s 159ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
2s 122ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"
3s 081ms
And
Add a bid "1500" to an auction by JSON file as "pskza1-carrier" for "pskza1-carrier"
1s 049ms
And
Add a bid "500" to an auction by JSON file as "pskza2-carrier-2" for "pskza2-carrier-2"
1s 288ms
Then
If user is login then logout
261ms
And
Login as "swisskrono-admin"
2s 814ms
And
Go to auction details
1s 873ms
And
Pass transport to carrier from auction details
1s 535ms
And
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia"
37s 970ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 814ms
After
Hooks.deleteTransportAfterTest()
824ms
Scenario Outline
Check mail after creating new inquiry
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 817ms
And
Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
3s 154ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
2s 138ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"
3s 079ms
And
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe"
5s 492ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
3s 007ms
After
Hooks.deleteTransportAfterTest()
727ms
Scenario Outline
Check if remind password http status is ok
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-adama"
238ms
And
Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file
1s 638ms
Then
Send password remind email "automaty10@o2.pl" and check if status is ok
205ms
After
Hooks.cleanUserDetailsAfterTest()
1s 363ms
Scenario Outline
Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 680ms
And
Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz"
001ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 535ms
And
Add transport by SKApi in "MGW" assigned to ""
022ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
000ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 907ms
When
Click button advice in transport table "CONTAINER"
221ms
And
Set advice window in schedule
3s 387ms
And
Fill advice form
20s 357ms
And
Click advice save button and wait for advice form to disappear
33s 320ms
And
Go to "TRANSPORT_TABLE"
392ms
And
Go to transport details "CONTAINER"
2s 910ms
Then
Check are advice values equals
4s 956ms
After
Hooks.cleanUserDetailsAfterTest()
2s 307ms
After
Hooks.deleteTransportAfterTest()
777ms
Scenario Outline
Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 421ms
And
Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz"
001ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 408ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 166ms
When
Click button advice in transport table "OWN_COLLECTION"
208ms
And
Set advice window in schedule
3s 376ms
And
Fill advice form
20s 523ms
And
Click advice save button and wait for advice form to disappear
33s 266ms
And
Go to "TRANSPORT_TABLE"
396ms
And
Go to transport details "OWN_COLLECTION"
2s 948ms
Then
Check are advice values equals
4s 944ms
After
Hooks.cleanUserDetailsAfterTest()
2s 109ms
After
Hooks.deleteTransportAfterTest()
779ms
Scenario Outline
Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 208ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
000ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 329ms
And
Add transport by SKApi in "MGW" assigned to ""
023ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
7s 429ms
When
Click button advice in transport table "TRANSPORT_ORDER"
222ms
And
Set advice window in schedule
3s 339ms
And
Fill advice form
20s 363ms
And
Click advice save button and wait for advice form to disappear
33s 339ms
And
Go to "TRANSPORT_TABLE"
475ms
And
Go to transport details "TRANSPORT_ORDER"
2s 919ms
Then
Check are advice values equals
4s 937ms
After
Hooks.cleanUserDetailsAfterTest()
2s 275ms
After
Hooks.deleteTransportAfterTest()
814ms
Scenario Outline
Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "pskza1-carrier" and set token of apiUsername "super-admin-skz"
8s 551ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
And
Prepare user "pskza1-carrier" details with all notifications and "" by JSON file
3s 490ms
And
Add transport by SKApi in "MGW" assigned to ""
022ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 872ms
When
Click button advice in transport table "TRANSPORT_ORDER"
225ms
And
Set advice window in schedule
3s 360ms
And
Fill advice form
20s 478ms
And
Click advice save button and wait for advice form to disappear
33s 293ms
And
Go to "TRANSPORT_TABLE"
494ms
And
Go to transport details "TRANSPORT_ORDER"
2s 840ms
Then
Check are advice values equals
5s 036ms
After
Hooks.cleanUserDetailsAfterTest()
2s 714ms
After
Hooks.deleteTransportAfterTest()
848ms
Scenario Outline
Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-tradesman" and set token of apiUsername "super-admin-skz"
8s 889ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
And
Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file
2s 467ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
023ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
000ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
4s 324ms
When
Click button advice in transport table "TRANSPORT_ORDER"
246ms
And
Set advice window in schedule
3s 521ms
And
Fill advice form
20s 105ms
And
Click advice save button and wait for advice form to disappear
33s 954ms
And
Go to "TRANSPORT_TABLE"
485ms
And
Go to transport details "TRANSPORT_ORDER"
2s 909ms
Then
Check are advice values equals
5s 042ms
After
Hooks.cleanUserDetailsAfterTest()
1s 744ms
After
Hooks.deleteTransportAfterTest()
788ms
Scenario Outline
Verify that advice data are saved properly
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 526ms
And
Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz"
001ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 369ms
And
Add transport by SKApi in "MGW" assigned to ""
025ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 173ms
When
Click button advice in transport table "OWN_COLLECTION"
222ms
And
Set advice window in schedule
3s 393ms
And
Fill advice form
20s 448ms
And
Click advice save button and wait for advice form to disappear
33s 309ms
And
Go to "TRANSPORT_TABLE"
480ms
Then
Check advice data in SK API database "OWN_COLLECTION"
423ms
After
Hooks.cleanUserDetailsAfterTest()
2s 080ms
After
Hooks.deleteTransportAfterTest()
780ms
Scenario Outline
Verify that advice data are saved properly
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 452ms
And
Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz"
001ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 333ms
And
Add transport by SKApi in "MGW" assigned to ""
019ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 928ms
When
Click button advice in transport table "CONTAINER"
233ms
And
Set advice window in schedule
3s 363ms
And
Fill advice form
20s 425ms
And
Click advice save button and wait for advice form to disappear
33s 824ms
And
Go to "TRANSPORT_TABLE"
450ms
Then
Check advice data in SK API database "CONTAINER"
232ms
After
Hooks.cleanUserDetailsAfterTest()
2s 311ms
After
Hooks.deleteTransportAfterTest()
881ms
Scenario Outline
Verify that advice data are saved properly
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 440ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 489ms
And
Add transport by SKApi in "MGW" assigned to ""
024ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
000ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
7s 217ms
When
Click button advice in transport table "TRANSPORT_ORDER"
265ms
And
Set advice window in schedule
3s 372ms
And
Fill advice form
20s 481ms
And
Click advice save button and wait for advice form to disappear
33s 319ms
And
Go to "TRANSPORT_TABLE"
536ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
092ms
After
Hooks.cleanUserDetailsAfterTest()
2s 140ms
After
Hooks.deleteTransportAfterTest()
794ms
Scenario Outline
Verify that advice data are saved properly
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "pskza1-carrier" and set token of apiUsername "super-admin-skz"
6s 252ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
000ms
And
Prepare user "pskza1-carrier" details with all notifications and "" by JSON file
3s 573ms
And
Add transport by SKApi in "MGW" assigned to ""
023ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
001ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 829ms
When
Click button advice in transport table "TRANSPORT_ORDER"
229ms
And
Set advice window in schedule
3s 326ms
And
Fill advice form
20s 556ms
And
Click advice save button and wait for advice form to disappear
33s 832ms
And
Go to "TRANSPORT_TABLE"
471ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
099ms
After
Hooks.cleanUserDetailsAfterTest()
2s 959ms
After
Hooks.deleteTransportAfterTest()
855ms
Scenario Outline
Verify that advice data are saved properly
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-tradesman" and set token of apiUsername "super-admin-skz"
7s 782ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
001ms
And
Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file
1s 880ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
020ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
000ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
4s 548ms
When
Click button advice in transport table "TRANSPORT_ORDER"
228ms
And
Set advice window in schedule
3s 381ms
And
Fill advice form
20s 667ms
And
Click advice save button and wait for advice form to disappear
33s 846ms
And
Go to "TRANSPORT_TABLE"
411ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
264ms
After
Hooks.cleanUserDetailsAfterTest()
1s 682ms
After
Hooks.deleteTransportAfterTest()
792ms
Scenario Outline
Check if it is possible to reject status by guard in transport table
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen"
4s 170ms
And
Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 020ms
And
Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 068ms
And
Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file
782ms
And
Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen"
4s 388ms
And
Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen"
2s 890ms
And
Check if reject date is not visible
15s 077ms
When
Reject status: Book of disinfection
202ms
And
Check if reject date is visible
1s 169ms
Then
If user is login then logout
5s 726ms
And
Login as "lantmannen-admin"
2s 069ms
And
Check if note was added to transport after status rejection
1s 661ms
And
Check if history note was added to transport after status rejection - "LOAD"
7s 258ms
And
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji"
2m 46s 929ms
And
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 375ms
After
Hooks.deleteTransportAfterTest()
756ms
After
Hooks.rollbackWarehousesAccess()
722ms
Scenario Outline
Check if it is not possible to use the previous password when editing it - remind password [A-8005]
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Set token of apiUsername "super-admin-skd"
245ms
And
Prepare login page
485ms
And
Click remind password button
278ms
And
Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 025ms
And
Send remind password form with email "apolloautomattest@gmail.com"
538ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!"
26s 382ms
And
Extract password reset link from mailgun mail
3s 860ms
And
Reset password from link with the same password
1s 445ms
Then
Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page
157ms
After
Hooks.cleanUserDetailsAfterTest()
876ms
Scenario Outline
Permission - Edit user main data [A-7965]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-adama"
239ms
And
Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2"
398ms
When
Login as "oaa1-receiver-2"
4s 079ms
And
Go to user "oaa1-receiver" details edition by prepared link
161ms
And
Change user details "email" to "newEmailAddress@newEmail.com"
966ms
And
Change user details "phone" to "123456789"
555ms
Then
Save user details
1s 128ms
And
Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page
147ms
After
Hooks.cleanUserDetailsAfterTest()
678ms
After
Hooks.rollbackAddedAuthorities()
238ms
Scenario Outline
Permission - Edit user notifications [A-7887]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-skz"
242ms
And
Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2"
202ms
When
Login as "pskza1-carrier-2"
7s 038ms
And
Go to user "pskza1-carrier" details edition by prepared link
101ms
And
Expand "other" notification section
2s 950ms
And
Select all notifications in "other" section
296ms
Then
Save user details
1s 463ms
After
Hooks.cleanUserDetailsAfterTest()
1s 004ms
After
Hooks.rollbackAddedAuthorities()
159ms
Scenario Outline
Permission - Edit user main data from other company [A-7887]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-adama"
247ms
And
Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer"
501ms
And
Set user details json of user "oaa1-receiver"
011ms
When
Login as "adama-buyer"
5s 019ms
And
Go to "USERS_TAB"
1s 472ms
And
Find user "oaa1-receiver"
3s 561ms
And
Change user details "email" to "newEmailAddress@newEmail.com"
824ms
And
Change user details "phone" to "123456789"
385ms
Then
Save user details
965ms
And
Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page
139ms
After
Hooks.cleanUserDetailsAfterTest()
633ms
After
Hooks.rollbackAddedAuthorities()
231ms
Scenario Outline
Permission - Edit user notifications from other company [A-7887]
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Set token of apiUsername "super-admin-skz"
233ms
And
Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman"
360ms
And
Set user details json of user "pskza1-carrier"
010ms
When
Login as "swisskrono-tradesman"
9s 380ms
And
Go to "USERS_TAB"
1s 763ms
And
Find user "pskza1-carrier"
3s 543ms
And
Expand "GLUE_FACTORY" notification section
685ms
And
Select all notifications in "GLUE_FACTORY" section
1s 303ms
Then
Save user details
1s 822ms
After
Hooks.cleanUserDetailsAfterTest()
1s 096ms
After
Hooks.rollbackAddedAuthorities()
246ms