Scenario Outline
Check if rejected invitation is visible in rejected tab
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-piast"
226ms
And
Delete invitations with email "automaty31415@test.pl"
087ms
Then
Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION"
1s 376ms
And
Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file
1s 303ms
When
Login as "piast-admin"
5s 035ms
Then
Go to "INVITATIONS_TAB"
671ms
And
Go to invitation details
141ms
Then
Reject invitation by button as user
297ms
When
If user is login then logout
651ms
Then
Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec"
4s 581ms
And
Go to "INVITATIONS_TAB"
457ms
And
Go to "REJECTED_TAB" invitation status tab
260ms
Then
Invitation is displayed on list "automaty31415@test.pl"
482ms
After
Hooks.deleteInvitationAfterTest()
146ms
After
Hooks.cleanUserDetailsAfterTest()
1s 210ms
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"
227ms
And
Prepare user "dha1-supplier-2" details with all notifications and "automatyy3333@test.pl" by JSON file
1s 707ms
When
Login as "neuca-admin" and set token of apiUsername "super-admin-neuca"
2s 368ms
And
Go to "INVITATIONS_TAB"
480ms
And
Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL"
2s 927ms
Then
Create invitation success alert is displayed
088ms
After
Hooks.deleteInvitationAfterTest()
208ms
After
Hooks.cleanUserDetailsAfterTest()
1s 285ms
Scenario Outline
Verify that password reset cancel login blockade [A-7286]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-skd"
247ms
And
Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1"
096ms
Given
Failed login as "swiss-krono-delivery-admin-2"
1s 440ms
Then
Verify that login error reason is "auth.invalidLoginOrPassword"
564ms
Given
Try login as "swiss-krono-delivery-admin-2"
1s 513ms
Then
Verify that login error reason is "auth.accountLocked"
277ms
Given
Click remind password button
225ms
And
Prepare user "swiss-krono-delivery-admin-2" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 130ms
And
Send remind password form with email "apolloautomattest@gmail.com"
548ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!"
11s 291ms
And
Extract password reset link from mailgun mail
4s 472ms
And
Reset password from link
1s 361ms
Then
Login as "swiss-krono-delivery-admin-2" with new password
4s 994ms
And
User is successfully logged
025ms
After
Hooks.cleanUserDetailsAfterTest()
994ms
After
Hooks.clearUserPasswordDataAfterTest()
478ms
After
Hooks.rollbackParameters()
099ms
After
Hooks.unlockUsers()
102ms
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 428ms
And
Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 445ms
And
Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama"
2s 191ms
And
Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama"
001ms
And
Show all transport types
1s 175ms
And
Click button advice in transport table "CONTAINER"
243ms
And
Set advice window in schedule
3s 366ms
And
Fill advice form
17s 129ms
And
Click advice save button and wait for advice form to disappear
33s 824ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!"
5s 860ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 291ms
After
Hooks.deleteTransportAfterTest()
839ms
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 733ms
And
Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 175ms
And
Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast"
2s 022ms
And
Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast"
001ms
And
Show all transport types
1s 156ms
And
Click button advice in transport table "DELIVERY"
253ms
And
Set advice window in schedule
3s 439ms
And
Fill advice form
12s 871ms
And
Click advice save button and wait for advice form to disappear
33s 313ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!"
5s 645ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 071ms
After
Hooks.deleteTransportAfterTest()
808ms
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 596ms
And
Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 943ms
And
Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper"
1s 985ms
And
Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper"
001ms
And
Show all transport types
1s 158ms
And
Click button advice in transport table "LOAD"
232ms
And
Set advice window in schedule
3s 258ms
And
Fill advice form
18s 738ms
And
Click advice save button and wait for advice form to disappear
33s 253ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!"
6s 044ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 511ms
After
Hooks.deleteTransportAfterTest()
734ms
Scenario Outline
Check if mail was sent to creator after editing advice
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
4s 820ms
And
Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 366ms
And
Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama"
1s 926ms
And
Show all transport types
1s 158ms
And
Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama"
3s 224ms
And
Go to "TRANSPORT_TABLE"
346ms
And
Go to transport details "CONTAINER"
2s 896ms
And
Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama"
001ms
When
Go to transport details "CONTAINER"
3s 565ms
And
Fill transport form
5s 191ms
And
Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama"
001ms
And
Expand advice panel
280ms
And
Edit advice in transport details
17s 606ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 207ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer"
5s 845ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 318ms
After
Hooks.deleteTransportAfterTest()
752ms
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 172ms
And
Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 166ms
And
Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast"
2s 067ms
And
Show all transport types
1s 160ms
And
Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast"
3s 502ms
And
Go to "TRANSPORT_TABLE"
390ms
And
Go to transport details "DELIVERY"
3s 055ms
And
Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-piast"
001ms
When
Go to transport details "DELIVERY"
3s 736ms
And
Fill transport form
1m 8s 622ms
And
Set "advice" inputs from JSON file "EDIT_ADVICE_DELIVERY" "super-admin-piast"
001ms
And
Expand advice panel
262ms
And
Edit advice in transport details
8s 098ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 241ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer"
5s 524ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 175ms
After
Hooks.deleteTransportAfterTest()
914ms
Scenario Outline
Check if mail was sent to creator after editing advice
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper"
5s 835ms
And
Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 716ms
And
Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper"
2s 053ms
And
Show all transport types
1s 168ms
And
Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper"
3s 368ms
And
Go to "TRANSPORT_TABLE"
402ms
And
Go to transport details "LOAD"
2s 885ms
And
Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper"
001ms
When
Go to transport details "LOAD"
3s 533ms
And
Fill transport form
28s 592ms
And
Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper"
001ms
And
Expand advice panel
280ms
And
Edit advice in transport details
23s 428ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 201ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer"
2m 47s 521ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 642ms
After
Hooks.deleteTransportAfterTest()
809ms
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"
251ms
And
Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 186ms
And
Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd"
2s 798ms
And
Confirm status "REPORTING" by Public API "v1"
572ms
And
Confirm status "ARRIVAL" by Public API "v1"
1s 143ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu"
10s 658ms
Then
Check if user got a mail
000ms
And
Assign Queue to classification resource: "super-admin-skd" "trociny" "CLASSIFICATION"
1s 019ms
And
Assign Place to classification resource: "super-admin-skd" "trociny" "Rozładunek" "UNLOAD"
1s 040ms
And
Confirm status "DEPARTURE" by Public API "v1"
1s 019ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd"
5s 386ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
939ms
After
Hooks.deleteTransportAfterTest()
761ms
Scenario Outline
Check if verification mail was sent to transport creator
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-hochland"
226ms
And
Prepare company "Dostawca Hochland Automat 1" verification email setting "48h"
217ms
And
Prepare user "dha1-supplier-2" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 103ms
And
Login as "dha1-supplier-2" and set token of apiUsername "dha1-supplier-2"
8s 703ms
And
Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2"
16s 867ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji"
1m 47s 653ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 721ms
After
Hooks.deleteTransportAfterTest()
720ms
After
Hooks.rollbackVerificationEmailSettingAfterTest()
436ms
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 802ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 237ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 125ms
And
Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama"
3s 556ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja"
5s 322ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 133ms
After
Hooks.deleteTransportAfterTest()
691ms
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 578ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 377ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 098ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
3s 033ms
And
Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama"
1s 380ms
And
Add a bid "500" to an auction by JSON file as "paa2-carrier" for "super-admin-adama"
1s 965ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia"
10s 731ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 100ms
After
Hooks.deleteTransportAfterTest()
629ms
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"
10s 986ms
And
Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 719ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
2s 182ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"
2s 841ms
And
Add a bid "1500" to an auction by JSON file as "pskza1-carrier" for "pskza1-carrier"
1s 045ms
And
Wait till auction end
1m 57s 016ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę"
2m 44s 957ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 409ms
After
Hooks.deleteTransportAfterTest()
624ms
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 639ms
And
Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 552ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 116ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
3s 057ms
And
Wait till auction end
1m 57s 015ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert"
2m 42s 525ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 415ms
After
Hooks.deleteTransportAfterTest()
653ms
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 852ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 351ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 107ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
3s 048ms
And
Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama"
1s 007ms
And
Add a bid "500" to an auction by JSON file as "paa2-carrier" for "super-admin-adama"
1s 837ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana"
10s 349ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 025ms
After
Hooks.deleteTransportAfterTest()
592ms
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 419ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 318ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 122ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
3s 123ms
And
Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama"
1s 011ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie"
2m 9s 934ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 312ms
After
Hooks.deleteTransportAfterTest()
582ms
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 583ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 346ms
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 019ms
And
Add a bid "500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama"
1s 765ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie"
5s 188ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 093ms
After
Hooks.deleteTransportAfterTest()
608ms
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 068ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 576ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 100ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes
3s 040ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji"
1m 2s 459ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 062ms
After
Hooks.deleteTransportAfterTest()
613ms
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"
2s 961ms
And
Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
4s 318ms
And
Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland"
3s 180ms
And
Go to "TRANSPORT_TABLE"
366ms
And
Go to transport details "DELIVERY"
2s 927ms
And
Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland"
001ms
And
Fill transport form
42s 887ms
And
Open section: "discrepancy-report-panel"
1s 139ms
And
Fill discrepancy report section
52s 360ms
And
Go to transport details "DELIVERY"
2s 913ms
And
Change filled value in details "rodo-acceptance" "checkbox" "true" "0"
1s 634ms
And
Generate discrepancy report
21s 576ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności"
5s 568ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
3s 408ms
After
Hooks.deleteTransportAfterTest()
916ms
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"
249ms
And
Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file
3s 027ms
When
Create default mode of transportation by API with "pba1-carrier"
695ms
Then
Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000"
373ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany"
10s 604ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 510ms
After
Hooks.deleteModeOfTransportationAfterTest()
348ms
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"
232ms
And
Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 855ms
When
Create default mode of transportation by API with "pba1-carrier"
536ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu"
5s 186ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 498ms
After
Hooks.deleteModeOfTransportationAfterTest()
311ms
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 192ms
And
Prepare user "pha2-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 168ms
And
Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin"
250ms
And
Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland"
3s 153ms
And
Go to "WAREHOUSE_TAB"
1s 382ms
And
Select warehouse "Serownia"
1s 567ms
And
Set week view
1s 267ms
And
Show yesterday
1s 164ms
And
Move window into the past
420ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na"
52s 028ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 368ms
After
Hooks.deleteTransportAfterTest()
767ms
After
Hooks.rollbackAddedAuthorities()
185ms
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"
9s 324ms
And
Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 469ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
2s 207ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import"
38s 219ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 160ms
After
Hooks.deleteTransportAfterTest()
592ms
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 431ms
And
Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 648ms
And
Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz"
2s 210ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport"
47s 318ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 170ms
After
Hooks.deleteTransportAfterTest()
574ms
Scenario Outline
Check if mail was sent to carrier after transport transfer
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
2s 611ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 592ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 078ms
And
Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true"
34s 915ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację"
5s 565ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 090ms
After
Hooks.deleteTransportAfterTest()
743ms
Scenario Outline
Check if mail was sent to carrier after transport transfer with no confirmation
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
2s 469ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 383ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 074ms
And
Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false"
34s 899ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie"
5s 601ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 019ms
After
Hooks.deleteTransportAfterTest()
598ms
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 483ms
And
Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 235ms
And
Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz"
2s 116ms
And
Transfer transport to carrier "Przewoźnik SKZ Automat 1"
34s 722ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację"
6s 137ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 759ms
After
Hooks.deleteTransportAfterTest()
804ms
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 771ms
And
Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
3s 170ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
2s 164ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"
3s 044ms
And
Add a bid "1500" to an auction by JSON file as "pskza1-carrier" for "pskza1-carrier"
1s 117ms
And
Add a bid "500" to an auction by JSON file as "pskza2-carrier-2" for "pskza2-carrier-2"
1s 218ms
Then
If user is login then logout
228ms
And
Login as "swisskrono-admin"
2s 674ms
And
Go to auction details
1s 863ms
And
Pass transport to carrier from auction details
1s 563ms
And
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia"
32s 325ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 798ms
After
Hooks.deleteTransportAfterTest()
850ms
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 861ms
And
Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
3s 163ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
2s 142ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"
2s 977ms
And
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe"
5s 489ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 948ms
After
Hooks.deleteTransportAfterTest()
650ms
Scenario Outline
Check if remind password http status is ok
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-adama"
228ms
And
Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file
1s 671ms
Then
Send password remind email "automaty10@o2.pl" and check if status is ok
231ms
After
Hooks.cleanUserDetailsAfterTest()
1s 273ms
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)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 630ms
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 430ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
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
6s 927ms
When
Click button advice in transport table "CONTAINER"
223ms
And
Set advice window in schedule
3s 410ms
And
Fill advice form
20s 279ms
And
Click advice save button and wait for advice form to disappear
18s 312ms
And
Go to "TRANSPORT_TABLE"
461ms
And
Go to transport details "CONTAINER"
2s 956ms
Then
Check are advice values equals
4s 937ms
After
Hooks.cleanUserDetailsAfterTest()
2s 362ms
After
Hooks.deleteTransportAfterTest()
836ms
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 507ms
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 415ms
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 "OWN_COLLECTION" created in transport table and set transport id
7s 177ms
When
Click button advice in transport table "OWN_COLLECTION"
231ms
And
Set advice window in schedule
3s 398ms
And
Fill advice form
20s 415ms
And
Click advice save button and wait for advice form to disappear
33s 224ms
And
Go to "TRANSPORT_TABLE"
460ms
And
Go to transport details "OWN_COLLECTION"
2s 929ms
Then
Check are advice values equals
4s 981ms
After
Hooks.cleanUserDetailsAfterTest()
2s 152ms
After
Hooks.deleteTransportAfterTest()
800ms
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 196ms
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 370ms
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 "TRANSPORT_ORDER" created in transport table and set transport id
7s 351ms
When
Click button advice in transport table "TRANSPORT_ORDER"
235ms
And
Set advice window in schedule
3s 338ms
And
Fill advice form
20s 420ms
And
Click advice save button and wait for advice form to disappear
33s 361ms
And
Go to "TRANSPORT_TABLE"
470ms
And
Go to transport details "TRANSPORT_ORDER"
2s 839ms
Then
Check are advice values equals
4s 976ms
After
Hooks.cleanUserDetailsAfterTest()
2s 339ms
After
Hooks.deleteTransportAfterTest()
745ms
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 399ms
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 600ms
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
6s 896ms
When
Click button advice in transport table "TRANSPORT_ORDER"
226ms
And
Set advice window in schedule
3s 325ms
And
Fill advice form
20s 627ms
And
Click advice save button and wait for advice form to disappear
33s 848ms
And
Go to "TRANSPORT_TABLE"
478ms
And
Go to transport details "TRANSPORT_ORDER"
2s 836ms
Then
Check are advice values equals
4s 959ms
After
Hooks.cleanUserDetailsAfterTest()
2s 789ms
After
Hooks.deleteTransportAfterTest()
807ms
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 720ms
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 464ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
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
4s 366ms
When
Click button advice in transport table "TRANSPORT_ORDER"
209ms
And
Set advice window in schedule
3s 434ms
And
Fill advice form
20s 424ms
And
Click advice save button and wait for advice form to disappear
33s 813ms
And
Go to "TRANSPORT_TABLE"
472ms
And
Go to transport details "TRANSPORT_ORDER"
2s 890ms
Then
Check are advice values equals
4s 984ms
After
Hooks.cleanUserDetailsAfterTest()
1s 776ms
After
Hooks.deleteTransportAfterTest()
832ms
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 537ms
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 391ms
And
Add transport by SKApi in "MGW" assigned to ""
020ms
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 200ms
When
Click button advice in transport table "OWN_COLLECTION"
211ms
And
Set advice window in schedule
3s 349ms
And
Fill advice form
20s 415ms
And
Click advice save button and wait for advice form to disappear
33s 258ms
And
Go to "TRANSPORT_TABLE"
449ms
Then
Check advice data in SK API database "OWN_COLLECTION"
412ms
After
Hooks.cleanUserDetailsAfterTest()
2s 131ms
After
Hooks.deleteTransportAfterTest()
814ms
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 321ms
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 392ms
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 958ms
When
Click button advice in transport table "CONTAINER"
209ms
And
Set advice window in schedule
3s 383ms
And
Fill advice form
20s 514ms
And
Click advice save button and wait for advice form to disappear
33s 236ms
And
Go to "TRANSPORT_TABLE"
394ms
Then
Check advice data in SK API database "CONTAINER"
193ms
After
Hooks.cleanUserDetailsAfterTest()
2s 262ms
After
Hooks.deleteTransportAfterTest()
818ms
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 495ms
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 364ms
And
Add transport by SKApi in "MGW" assigned to ""
019ms
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 372ms
When
Click button advice in transport table "TRANSPORT_ORDER"
226ms
And
Set advice window in schedule
3s 287ms
And
Fill advice form
20s 552ms
And
Click advice save button and wait for advice form to disappear
33s 381ms
And
Go to "TRANSPORT_TABLE"
479ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
092ms
After
Hooks.cleanUserDetailsAfterTest()
2s 105ms
After
Hooks.deleteTransportAfterTest()
834ms
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 "pskza1-carrier" and set token of apiUsername "super-admin-skz"
6s 137ms
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 286ms
And
Add transport by SKApi in "MGW" assigned to ""
017ms
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
4s 041ms
When
Click button advice in transport table "TRANSPORT_ORDER"
225ms
And
Set advice window in schedule
3s 400ms
And
Fill advice form
20s 438ms
And
Click advice save button and wait for advice form to disappear
33s 323ms
And
Go to "TRANSPORT_TABLE"
551ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
092ms
After
Hooks.cleanUserDetailsAfterTest()
2s 965ms
After
Hooks.deleteTransportAfterTest()
822ms
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 613ms
And
Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz"
000ms
And
Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file
1s 867ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
019ms
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 534ms
When
Click button advice in transport table "TRANSPORT_ORDER"
232ms
And
Set advice window in schedule
3s 443ms
And
Fill advice form
20s 411ms
And
Click advice save button and wait for advice form to disappear
33s 798ms
And
Go to "TRANSPORT_TABLE"
445ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
268ms
After
Hooks.cleanUserDetailsAfterTest()
1s 676ms
After
Hooks.deleteTransportAfterTest()
803ms
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 520ms
And
Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file
893ms
And
Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 056ms
And
Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file
747ms
And
Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen"
4s 242ms
And
Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen"
2s 878ms
And
Check if reject date is not visible
15s 040ms
When
Reject status: Book of disinfection
202ms
And
Check if reject date is visible
887ms
Then
If user is login then logout
275ms
And
Login as "lantmannen-admin"
2s 607ms
And
Check if note was added to transport after status rejection
1s 692ms
And
Check if history note was added to transport after status rejection - "LOAD"
7s 257ms
And
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji"
2m 47s 615ms
And
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 239ms
After
Hooks.deleteTransportAfterTest()
752ms
After
Hooks.rollbackWarehousesAccess()
752ms
Scenario Outline
Check if it is not possible to use the previous password when editing it - remind password [A-8005]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-skd"
232ms
And
Prepare login page
464ms
And
Click remind password button
277ms
And
Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 001ms
And
Send remind password form with email "apolloautomattest@gmail.com"
554ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!"
27s 397ms
And
Extract password reset link from mailgun mail
4s 550ms
And
Reset password from link with the same password
1s 561ms
Then
Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page
231ms
After
Hooks.cleanUserDetailsAfterTest()
941ms
Scenario Outline
Permission - Edit user main data [A-7965]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-adama"
226ms
And
Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2"
407ms
When
Login as "oaa1-receiver-2"
4s 131ms
And
Go to user "oaa1-receiver" details edition by prepared link
155ms
And
Change user details "email" to "newEmailAddress@newEmail.com"
985ms
And
Change user details "phone" to "123456789"
517ms
Then
Save user details
941ms
And
Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page
148ms
After
Hooks.cleanUserDetailsAfterTest()
647ms
After
Hooks.rollbackAddedAuthorities()
234ms
Scenario Outline
Permission - Edit user notifications [A-7887]
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Set token of apiUsername "super-admin-skz"
229ms
And
Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2"
201ms
When
Login as "pskza1-carrier-2"
6s 923ms
And
Go to user "pskza1-carrier" details edition by prepared link
095ms
And
Expand "other" notification section
2s 322ms
And
Select all notifications in "other" section
272ms
Then
Save user details
1s 530ms
After
Hooks.cleanUserDetailsAfterTest()
1s 057ms
After
Hooks.rollbackAddedAuthorities()
167ms
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"
227ms
And
Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer"
443ms
And
Set user details json of user "oaa1-receiver"
015ms
When
Login as "adama-buyer"
4s 974ms
And
Go to "USERS_TAB"
1s 435ms
And
Find user "oaa1-receiver"
3s 578ms
And
Change user details "email" to "newEmailAddress@newEmail.com"
778ms
And
Change user details "phone" to "123456789"
455ms
Then
Save user details
1s 062ms
And
Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page
153ms
After
Hooks.cleanUserDetailsAfterTest()
661ms
After
Hooks.rollbackAddedAuthorities()
220ms
Scenario Outline
Permission - Edit user notifications from other company [A-7887]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-skz"
225ms
And
Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman"
354ms
And
Set user details json of user "pskza1-carrier"
010ms
When
Login as "swisskrono-tradesman"
8s 979ms
And
Go to "USERS_TAB"
1s 555ms
And
Find user "pskza1-carrier"
3s 589ms
And
Expand "GLUE_FACTORY" notification section
560ms
And
Select all notifications in "GLUE_FACTORY" section
1s 397ms
Then
Save user details
1s 881ms
After
Hooks.cleanUserDetailsAfterTest()
1s 052ms
After
Hooks.rollbackAddedAuthorities()
232ms