Scenario Outline
Check if rejected invitation is visible in rejected tab
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Set token of apiUsername "super-admin-piast"
222ms
And
Delete invitations with email "automaty31415@test.pl"
091ms
Then
Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION"
1s 385ms
And
Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file
1s 317ms
When
Login as "piast-admin"
4s 812ms
Then
Go to "INVITATIONS_TAB"
680ms
And
Go to invitation details
150ms
Then
Reject invitation by button as user
309ms
When
If user is login then logout
258ms
Then
Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec"
4s 609ms
And
Go to "INVITATIONS_TAB"
467ms
And
Go to "REJECTED_TAB" invitation status tab
263ms
Then
Invitation is displayed on list "automaty31415@test.pl"
481ms
After
Hooks.deleteInvitationAfterTest()
147ms
After
Hooks.cleanUserDetailsAfterTest()
1s 219ms
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 735ms
When
Login as "neuca-admin" and set token of apiUsername "super-admin-neuca"
2s 169ms
And
Go to "INVITATIONS_TAB"
404ms
And
Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL"
2s 775ms
Then
Create invitation success alert is displayed
105ms
After
Hooks.deleteInvitationAfterTest()
191ms
After
Hooks.cleanUserDetailsAfterTest()
1s 268ms
Scenario Outline
Verify that password reset cancel login blockade [A-7286]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-skd"
243ms
And
Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1"
110ms
Given
Failed login as "swiss-krono-delivery-admin-2"
1s 357ms
Then
Verify that login error reason is "auth.invalidLoginOrPassword"
555ms
Given
Try login as "swiss-krono-delivery-admin-2"
1s 521ms
Then
Verify that login error reason is "auth.accountLocked"
304ms
Given
Click remind password button
256ms
And
Prepare user "swiss-krono-delivery-admin-2" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 268ms
And
Send remind password form with email "apolloautomattest@gmail.com"
525ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!"
33s 632ms
And
Extract password reset link from mailgun mail
3s 888ms
And
Reset password from link
1s 391ms
Then
Login as "swiss-krono-delivery-admin-2" with new password
5s 038ms
And
User is successfully logged
030ms
After
Hooks.cleanUserDetailsAfterTest()
990ms
After
Hooks.clearUserPasswordDataAfterTest()
709ms
After
Hooks.rollbackParameters()
103ms
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 453ms
And
Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 077ms
And
Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama"
2s 212ms
And
Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama"
001ms
And
Show all transport types
1s 166ms
And
Click button advice in transport table "CONTAINER"
251ms
And
Set advice window in schedule
3s 270ms
And
Fill advice form
17s 141ms
And
Click advice save button and wait for advice form to disappear
33s 805ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!"
5s 556ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 295ms
After
Hooks.deleteTransportAfterTest()
768ms
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 648ms
And
Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 179ms
And
Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast"
2s 168ms
And
Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast"
001ms
And
Show all transport types
1s 166ms
And
Click button advice in transport table "DELIVERY"
227ms
And
Set advice window in schedule
3s 422ms
And
Fill advice form
13s 018ms
And
Click advice save button and wait for advice form to disappear
33s 177ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!"
6s 240ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 029ms
After
Hooks.deleteTransportAfterTest()
793ms
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 686ms
And
Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 697ms
And
Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper"
2s 009ms
And
Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper"
001ms
And
Show all transport types
1s 160ms
And
Click button advice in transport table "LOAD"
259ms
And
Set advice window in schedule
3s 294ms
And
Fill advice form
18s 766ms
And
Click advice save button and wait for advice form to disappear
33s 240ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!"
5s 867ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 525ms
After
Hooks.deleteTransportAfterTest()
739ms
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 884ms
And
Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 430ms
And
Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama"
1s 888ms
And
Show all transport types
1s 157ms
And
Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama"
3s 270ms
And
Go to "TRANSPORT_TABLE"
359ms
And
Go to transport details "CONTAINER"
2s 914ms
And
Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama"
001ms
When
Go to transport details "CONTAINER"
3s 572ms
And
Fill transport form
5s 212ms
And
Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama"
001ms
And
Expand advice panel
229ms
And
Edit advice in transport details
17s 568ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 187ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer"
10s 749ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 288ms
After
Hooks.deleteTransportAfterTest()
738ms
Scenario Outline
Check if mail was sent to creator after editing advice
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "piast-admin" and set token of apiUsername "super-admin-piast"
5s 336ms
And
Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 192ms
And
Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast"
1s 996ms
And
Show all transport types
1s 160ms
And
Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast"
3s 494ms
And
Go to "TRANSPORT_TABLE"
391ms
And
Go to transport details "DELIVERY"
2s 980ms
And
Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-piast"
001ms
When
Go to transport details "DELIVERY"
3s 783ms
And
Fill transport form
1m 8s 763ms
And
Set "advice" inputs from JSON file "EDIT_ADVICE_DELIVERY" "super-admin-piast"
001ms
And
Expand advice panel
264ms
And
Edit advice in transport details
8s 137ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 193ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer"
10s 816ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 110ms
After
Hooks.deleteTransportAfterTest()
928ms
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 632ms
And
Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 710ms
And
Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper"
1s 934ms
And
Show all transport types
1s 158ms
And
Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper"
3s 280ms
And
Go to "TRANSPORT_TABLE"
394ms
And
Go to transport details "LOAD"
2s 936ms
And
Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper"
001ms
When
Go to transport details "LOAD"
3s 557ms
And
Fill transport form
28s 628ms
And
Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper"
001ms
And
Expand advice panel
278ms
And
Edit advice in transport details
23s 306ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 240ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer"
2m 53s 855ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 655ms
After
Hooks.deleteTransportAfterTest()
754ms
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"
239ms
And
Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 124ms
And
Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd"
2s 820ms
And
Confirm status "REPORTING" by Public API "v1"
565ms
And
Confirm status "ARRIVAL" by Public API "v1"
1s 046ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu"
10s 686ms
Then
Check if user got a mail
000ms
And
Assign Queue to classification resource: "super-admin-skd" "trociny" "CLASSIFICATION"
1s 020ms
And
Assign Place to classification resource: "super-admin-skd" "trociny" "Rozładunek" "UNLOAD"
1s 039ms
And
Confirm status "DEPARTURE" by Public API "v1"
1s 091ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd"
10s 915ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
952ms
After
Hooks.deleteTransportAfterTest()
814ms
Scenario Outline
Check if verification mail was sent to transport creator
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-hochland"
257ms
And
Prepare company "Dostawca Hochland Automat 1" verification email setting "48h"
208ms
And
Prepare user "dha1-supplier-2" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 122ms
And
Login as "dha1-supplier-2" and set token of apiUsername "dha1-supplier-2"
8s 784ms
And
Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2"
16s 863ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji"
1m 28s 655ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 666ms
After
Hooks.deleteTransportAfterTest()
755ms
After
Hooks.rollbackVerificationEmailSettingAfterTest()
426ms
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 653ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 246ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 161ms
And
Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama"
3s 484ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja"
10s 913ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 071ms
After
Hooks.deleteTransportAfterTest()
704ms
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 497ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 323ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 080ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
3s 019ms
And
Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama"
1s 360ms
And
Add a bid "500" to an auction by JSON file as "paa2-carrier" for "super-admin-adama"
1s 934ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia"
10s 650ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 121ms
After
Hooks.deleteTransportAfterTest()
597ms
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"
12s 348ms
And
Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 605ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
2s 162ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"
2s 851ms
And
Add a bid "1500" to an auction by JSON file as "pskza1-carrier" for "pskza1-carrier"
1s 054ms
And
Wait till auction end
1m 57s 016ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę"
2m 49s 631ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 391ms
After
Hooks.deleteTransportAfterTest()
620ms
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 640ms
And
Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 547ms
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 056ms
And
Wait till auction end
1m 57s 019ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert"
11s 468ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 375ms
After
Hooks.deleteTransportAfterTest()
526ms
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 771ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 305ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 099ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
3s 002ms
And
Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama"
1s 016ms
And
Add a bid "500" to an auction by JSON file as "paa2-carrier" for "super-admin-adama"
1s 829ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana"
37s 654ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 015ms
After
Hooks.deleteTransportAfterTest()
609ms
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 798ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 356ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 082ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
2s 996ms
And
Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama"
991ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie"
1m 52s 429ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 232ms
After
Hooks.deleteTransportAfterTest()
596ms
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 616ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 299ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 085ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
2s 984ms
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 326ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 112ms
After
Hooks.deleteTransportAfterTest()
586ms
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 220ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 523ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 065ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes
3s 082ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji"
1m 26s 495ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 353ms
After
Hooks.deleteTransportAfterTest()
690ms
Scenario Outline
Check if mail was sent to after discrepancy report generation
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "hochland-admin" and set token of apiUsername "super-admin-hochland"
3s 080ms
And
Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
4s 332ms
And
Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland"
3s 170ms
And
Go to "TRANSPORT_TABLE"
382ms
And
Go to transport details "DELIVERY"
2s 961ms
And
Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland"
001ms
And
Fill transport form
42s 846ms
And
Open section: "discrepancy-report-panel"
1s 147ms
And
Fill discrepancy report section
52s 449ms
And
Go to transport details "DELIVERY"
2s 832ms
And
Change filled value in details "rodo-acceptance" "checkbox" "true" "0"
1s 522ms
And
Generate discrepancy report
21s 519ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności"
6s 735ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
3s 617ms
After
Hooks.deleteTransportAfterTest()
930ms
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 048ms
When
Create default mode of transportation by API with "pba1-carrier"
670ms
Then
Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000"
368ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany"
11s 206ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 447ms
After
Hooks.deleteModeOfTransportationAfterTest()
361ms
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"
228ms
And
Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 835ms
When
Create default mode of transportation by API with "pba1-carrier"
578ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu"
5s 189ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 478ms
After
Hooks.deleteModeOfTransportationAfterTest()
326ms
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 016ms
And
Prepare user "pha2-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 161ms
And
Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin"
182ms
And
Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland"
3s 150ms
And
Go to "WAREHOUSE_TAB"
1s 260ms
And
Select warehouse "Serownia"
1s 636ms
And
Set week view
1s 250ms
And
Show yesterday
1s 163ms
And
Move window into the past
408ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na"
53s 097ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 340ms
After
Hooks.deleteTransportAfterTest()
780ms
After
Hooks.rollbackAddedAuthorities()
127ms
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 161ms
And
Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 446ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
2s 200ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import"
38s 458ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 098ms
After
Hooks.deleteTransportAfterTest()
563ms
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 320ms
And
Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 632ms
And
Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz"
2s 177ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport"
47s 285ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 200ms
After
Hooks.deleteTransportAfterTest()
545ms
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 642ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 618ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
2s 088ms
And
Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true"
34s 793ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację"
5s 843ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 111ms
After
Hooks.deleteTransportAfterTest()
784ms
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 587ms
And
Prepare user "paa1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 332ms
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 "false"
34s 910ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie"
5s 744ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 082ms
After
Hooks.deleteTransportAfterTest()
565ms
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 533ms
And
Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
2s 230ms
And
Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz"
2s 109ms
And
Transfer transport to carrier "Przewoźnik SKZ Automat 1"
34s 801ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację"
5s 477ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 688ms
After
Hooks.deleteTransportAfterTest()
787ms
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 678ms
And
Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
3s 131ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
2s 132ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"
3s 046ms
And
Add a bid "1500" to an auction by JSON file as "pskza1-carrier" for "pskza1-carrier"
1s 141ms
And
Add a bid "500" to an auction by JSON file as "pskza2-carrier-2" for "pskza2-carrier-2"
1s 202ms
Then
If user is login then logout
265ms
And
Login as "swisskrono-admin"
2s 774ms
And
Go to auction details
1s 842ms
And
Pass transport to carrier from auction details
1s 544ms
And
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia"
36s 467ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
2s 704ms
After
Hooks.deleteTransportAfterTest()
864ms
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 769ms
And
Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
3s 140ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
2s 154ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"
2s 958ms
And
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe"
5s 268ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
3s 035ms
After
Hooks.deleteTransportAfterTest()
651ms
Scenario Outline
Check if remind password http status is ok
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-adama"
254ms
And
Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file
1s 543ms
Then
Send password remind email "automaty10@o2.pl" and check if status is ok
269ms
After
Hooks.cleanUserDetailsAfterTest()
1s 257ms
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 551ms
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 ""
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
6s 947ms
When
Click button advice in transport table "CONTAINER"
204ms
And
Set advice window in schedule
3s 360ms
And
Fill advice form
20s 408ms
And
Click advice save button and wait for advice form to disappear
33s 247ms
And
Go to "TRANSPORT_TABLE"
458ms
And
Go to transport details "CONTAINER"
2s 939ms
Then
Check are advice values equals
4s 996ms
After
Hooks.cleanUserDetailsAfterTest()
2s 320ms
After
Hooks.deleteTransportAfterTest()
789ms
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 475ms
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 365ms
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 091ms
When
Click button advice in transport table "OWN_COLLECTION"
235ms
And
Set advice window in schedule
3s 357ms
And
Fill advice form
20s 364ms
And
Click advice save button and wait for advice form to disappear
33s 249ms
And
Go to "TRANSPORT_TABLE"
451ms
And
Go to transport details "OWN_COLLECTION"
2s 904ms
Then
Check are advice values equals
4s 989ms
After
Hooks.cleanUserDetailsAfterTest()
2s 094ms
After
Hooks.deleteTransportAfterTest()
828ms
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 225ms
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 325ms
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 "TRANSPORT_ORDER" created in transport table and set transport id
7s 415ms
When
Click button advice in transport table "TRANSPORT_ORDER"
228ms
And
Set advice window in schedule
3s 342ms
And
Fill advice form
20s 328ms
And
Click advice save button and wait for advice form to disappear
33s 316ms
And
Go to "TRANSPORT_TABLE"
419ms
And
Go to transport details "TRANSPORT_ORDER"
2s 910ms
Then
Check are advice values equals
4s 933ms
After
Hooks.cleanUserDetailsAfterTest()
2s 304ms
After
Hooks.deleteTransportAfterTest()
805ms
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 436ms
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 396ms
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
7s 056ms
When
Click button advice in transport table "TRANSPORT_ORDER"
213ms
And
Set advice window in schedule
3s 455ms
And
Fill advice form
20s 448ms
And
Click advice save button and wait for advice form to disappear
18s 341ms
And
Go to "TRANSPORT_TABLE"
434ms
And
Go to transport details "TRANSPORT_ORDER"
2s 818ms
Then
Check are advice values equals
4s 945ms
After
Hooks.cleanUserDetailsAfterTest()
2s 693ms
After
Hooks.deleteTransportAfterTest()
809ms
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 740ms
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 495ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
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
4s 343ms
When
Click button advice in transport table "TRANSPORT_ORDER"
211ms
And
Set advice window in schedule
3s 388ms
And
Fill advice form
20s 307ms
And
Click advice save button and wait for advice form to disappear
33s 839ms
And
Go to "TRANSPORT_TABLE"
497ms
And
Go to transport details "TRANSPORT_ORDER"
2s 912ms
Then
Check are advice values equals
4s 971ms
After
Hooks.cleanUserDetailsAfterTest()
1s 783ms
After
Hooks.deleteTransportAfterTest()
824ms
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"
8s 079ms
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 364ms
And
Add transport by SKApi in "MGW" assigned to ""
020ms
And
Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz"
000ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 221ms
When
Click button advice in transport table "OWN_COLLECTION"
197ms
And
Set advice window in schedule
3s 343ms
And
Fill advice form
20s 492ms
And
Click advice save button and wait for advice form to disappear
33s 234ms
And
Go to "TRANSPORT_TABLE"
490ms
Then
Check advice data in SK API database "OWN_COLLECTION"
425ms
After
Hooks.cleanUserDetailsAfterTest()
2s 089ms
After
Hooks.deleteTransportAfterTest()
805ms
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 281ms
And
Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz"
000ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 376ms
And
Add transport by SKApi in "MGW" assigned to ""
020ms
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 921ms
When
Click button advice in transport table "CONTAINER"
227ms
And
Set advice window in schedule
3s 311ms
And
Fill advice form
20s 389ms
And
Click advice save button and wait for advice form to disappear
33s 245ms
And
Go to "TRANSPORT_TABLE"
457ms
Then
Check advice data in SK API database "CONTAINER"
233ms
After
Hooks.cleanUserDetailsAfterTest()
2s 286ms
After
Hooks.deleteTransportAfterTest()
781ms
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 381ms
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 320ms
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 "TRANSPORT_ORDER" created in transport table and set transport id
4s 361ms
When
Click button advice in transport table "TRANSPORT_ORDER"
233ms
And
Set advice window in schedule
3s 327ms
And
Fill advice form
20s 467ms
And
Click advice save button and wait for advice form to disappear
33s 367ms
And
Go to "TRANSPORT_TABLE"
488ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
094ms
After
Hooks.cleanUserDetailsAfterTest()
2s 077ms
After
Hooks.deleteTransportAfterTest()
783ms
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 191ms
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 301ms
And
Add transport by SKApi in "MGW" assigned to ""
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 040ms
When
Click button advice in transport table "TRANSPORT_ORDER"
241ms
And
Set advice window in schedule
3s 339ms
And
Fill advice form
20s 388ms
And
Click advice save button and wait for advice form to disappear
33s 828ms
And
Go to "TRANSPORT_TABLE"
479ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
101ms
After
Hooks.cleanUserDetailsAfterTest()
3s 059ms
After
Hooks.deleteTransportAfterTest()
826ms
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"
001ms
And
Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file
1s 926ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
025ms
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 513ms
When
Click button advice in transport table "TRANSPORT_ORDER"
227ms
And
Set advice window in schedule
3s 387ms
And
Fill advice form
20s 376ms
And
Click advice save button and wait for advice form to disappear
33s 789ms
And
Go to "TRANSPORT_TABLE"
521ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
255ms
After
Hooks.cleanUserDetailsAfterTest()
1s 744ms
After
Hooks.deleteTransportAfterTest()
836ms
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 400ms
And
Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file
897ms
And
Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 085ms
And
Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file
744ms
And
Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen"
4s 407ms
And
Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen"
2s 866ms
And
Check if reject date is not visible
15s 069ms
When
Reject status: Book of disinfection
199ms
And
Check if reject date is visible
884ms
Then
If user is login then logout
721ms
And
Login as "lantmannen-admin"
2s 077ms
And
Check if note was added to transport after status rejection
1s 648ms
And
Check if history note was added to transport after status rejection - "LOAD"
7s 315ms
And
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji"
2m 43s 522ms
And
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
1s 282ms
After
Hooks.deleteTransportAfterTest()
765ms
After
Hooks.rollbackWarehousesAccess()
721ms
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"
227ms
And
Prepare login page
444ms
And
Click remind password button
252ms
And
Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
1s 016ms
And
Send remind password form with email "apolloautomattest@gmail.com"
561ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!"
31s 625ms
And
Extract password reset link from mailgun mail
3s 957ms
And
Reset password from link with the same password
1s 466ms
Then
Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page
205ms
After
Hooks.cleanUserDetailsAfterTest()
915ms
Scenario Outline
Permission - Edit user main data [A-7965]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-adama"
238ms
And
Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2"
397ms
When
Login as "oaa1-receiver-2"
4s 245ms
And
Go to user "oaa1-receiver" details edition by prepared link
132ms
And
Change user details "email" to "newEmailAddress@newEmail.com"
1s 021ms
And
Change user details "phone" to "123456789"
488ms
Then
Save user details
1s 003ms
And
Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page
171ms
After
Hooks.cleanUserDetailsAfterTest()
673ms
After
Hooks.rollbackAddedAuthorities()
252ms
Scenario Outline
Permission - Edit user notifications [A-7887]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-skz"
247ms
And
Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2"
200ms
When
Login as "pskza1-carrier-2"
7s 112ms
And
Go to user "pskza1-carrier" details edition by prepared link
093ms
And
Expand "other" notification section
2s 454ms
And
Select all notifications in "other" section
283ms
Then
Save user details
1s 574ms
After
Hooks.cleanUserDetailsAfterTest()
966ms
After
Hooks.rollbackAddedAuthorities()
154ms
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"
237ms
And
Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer"
451ms
And
Set user details json of user "oaa1-receiver"
013ms
When
Login as "adama-buyer"
4s 905ms
And
Go to "USERS_TAB"
1s 483ms
And
Find user "oaa1-receiver"
3s 595ms
And
Change user details "email" to "newEmailAddress@newEmail.com"
791ms
And
Change user details "phone" to "123456789"
437ms
Then
Save user details
1s 038ms
And
Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page
162ms
After
Hooks.cleanUserDetailsAfterTest()
657ms
After
Hooks.rollbackAddedAuthorities()
254ms
Scenario Outline
Permission - Edit user notifications from other company [A-7887]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-skz"
220ms
And
Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman"
342ms
And
Set user details json of user "pskza1-carrier"
009ms
When
Login as "swisskrono-tradesman"
9s 166ms
And
Go to "USERS_TAB"
1s 660ms
And
Find user "pskza1-carrier"
3s 574ms
And
Expand "GLUE_FACTORY" notification section
603ms
And
Select all notifications in "GLUE_FACTORY" section
1s 359ms
Then
Save user details
1s 954ms
After
Hooks.cleanUserDetailsAfterTest()
1s 072ms
After
Hooks.rollbackAddedAuthorities()
232ms