Scenario Outline
Check if user has accepted invitation from principal after accepting invitation by another user from company
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Set token of apiUsername "super-admin-farmacol"
094ms
And
Prepare user "dnfa1-supplier" details with all notifications and "automaty314153@test.pl" by JSON file
366ms
And
Create invitation by JSON file "super-admin-farmacol" for "automaty314153@test.pl" "CREATE_SUPPLIER_INVITATION"
468ms
java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Użytkownik o podanym adresie e-mail już istnieje. Prosimy o kontakt z naszą obsługą klienta na support@support.xd.]]
at org.junit.Assert.fail(Assert.java:88)
at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:64)
at ✽.Create invitation by JSON file "super-admin-farmacol" for "automaty314153@test.pl" "CREATE_SUPPLIER_INVITATION"(file:Features/Atom/Invitations/Invitation.feature:86)
And
Prepare user "dnfa1-supplier-2" details with all notifications and "automaty214152@test.pl" by JSON file
000ms
And
Create invitation by JSON file "super-admin-farmacol" for "automaty214152@test.pl" "CREATE_SUPPLIER_INVITATION"
000ms
When
Login as "dnfa1-supplier" and set token of apiUsername "super-admin-farmacol"
000ms
And
Go to "INVITATIONS_TAB"
000ms
And
Accept invitation
000ms
And
If user is login then logout
000ms
And
Login as "dnfa1-supplier-2" and set token of apiUsername "super-admin-farmacol"
000ms
And
Verify if user has visible "no waiting" invitation
000ms
And
Verify if user has visible "accepted" invitation
000ms
And
Verify if user can see "Farmacol" on principal switch dropdown
000ms
After
Hooks.cleanUserDetailsAfterTest()
187ms
Scenario Outline
Check if rejected invitation is visible in rejected tab
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-piast"
095ms
And
Delete invitations with email "automaty31415@test.pl"
002ms
And
Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file
147ms
Then
Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION"
124ms
java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Piast Cargo Transport Sp. z o.o., NIP: . Prosimy o poprawienie danych.]]
at org.junit.Assert.fail(Assert.java:88)
at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:64)
at ✽.Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION"(file:Features/Atom/Invitations/Invitation.feature:175)
When
Login as "piast-admin"
000ms
Then
Go to "INVITATIONS_TAB"
000ms
And
Go to invitation details
000ms
Then
Reject invitation by button as user
000ms
When
If user is login then logout
000ms
Then
Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec"
000ms
And
Go to "INVITATIONS_TAB"
000ms
And
Go to "REJECTED_TAB" invitation status tab
000ms
Then
Invitation is displayed on list "automaty31415@test.pl"
000ms
After
Hooks.deleteInvitationAfterTest()
000ms
java.lang.NullPointerException
at CucumberTests.Hooks.deleteInvitationAfterTest(Hooks.java:263)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at cucumber.runtime.Utils$1.call(Utils.java:26)
at cucumber.runtime.Timeout.timeout(Timeout.java:16)
at cucumber.runtime.Utils.invoke(Utils.java:20)
at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
at cucumber.runner.TestStep.executeStep(TestStep.java:63)
at cucumber.runner.TestStep.run(TestStep.java:49)
at cucumber.runner.TestCase.run(TestCase.java:49)
at cucumber.runner.Runner.runPickle(Runner.java:40)
at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
After
Hooks.cleanUserDetailsAfterTest()
130ms
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)
000ms
Given
Set token of apiUsername "super-admin-alrec"
096ms
And
Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file
230ms
When
Login as "neuca-admin" and set token of apiUsername "super-admin-neuca"
909ms
And
Go to "INVITATIONS_TAB"
153ms
And
Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL"
1s 054ms
Then
Create invitation success alert is displayed
041ms
After
Hooks.deleteInvitationAfterTest()
006ms
After
Hooks.cleanUserDetailsAfterTest()
237ms
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"
958ms
And
Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
172ms
And
Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama"
1s 197ms
And
Get inputs from database "ADVICE_CONTAINER" "super-admin-adama"
036ms
And
Show all transport types
1s 037ms
And
Click button advice in transport table "CONTAINER"
085ms
And
Set advice window in schedule
2s 430ms
And
Fill advice form
11s 682ms
And
Click advice save button and wait for advice form to disappear
30s 710ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!"
5s 805ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
110ms
After
Hooks.cleanUserDetailsAfterTest()
184ms
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"
1s 143ms
And
Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
145ms
And
Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast"
1s 205ms
And
Get inputs from database "ADVICE_DELIVERY" "super-admin-piast"
036ms
And
Show all transport types
1s 042ms
And
Click button advice in transport table "DELIVERY"
104ms
And
Set advice window in schedule
2s 567ms
And
Fill advice form
8s 248ms
And
Click advice save button and wait for advice form to disappear
30s 712ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!"
5s 473ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
137ms
After
Hooks.cleanUserDetailsAfterTest()
166ms
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"
1s 096ms
And
Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
306ms
And
Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper"
1s 222ms
And
Get inputs from database "ADVICE_LOAD" "super-admin-keeeper"
038ms
And
Show all transport types
1s 042ms
And
Click button advice in transport table "LOAD"
092ms
And
Set advice window in schedule
2s 428ms
And
Fill advice form
13s 033ms
And
Click advice save button and wait for advice form to disappear
30s 689ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!"
5s 476ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
092ms
After
Hooks.cleanUserDetailsAfterTest()
182ms
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"
1s 521ms
And
Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
194ms
And
Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama"
1s 214ms
And
Show all transport types
1s 043ms
And
Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama"
44s 989ms
And
Go to "TRANSPORT_TABLE"
185ms
And
Go to transport details "CONTAINER"
2s 387ms
And
Get inputs from database "EDIT_CONTAINER" "super-admin-adama"
039ms
When
Go to transport details "CONTAINER"
3s 186ms
And
Fill transport form
4s 701ms
And
Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-adama"
036ms
And
Expand advice panel
115ms
And
Edit advice in transport details
12s 238ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 110ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer"
5s 539ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
103ms
After
Hooks.cleanUserDetailsAfterTest()
177ms
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"
1s 668ms
And
Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
166ms
And
Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast"
1s 196ms
And
Show all transport types
1s 042ms
And
Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast"
41s 628ms
And
Go to "TRANSPORT_TABLE"
227ms
And
Go to transport details "DELIVERY"
2s 489ms
And
Get inputs from database "EDIT_DELIVERY" "super-admin-piast"
036ms
When
Go to transport details "DELIVERY"
3s 182ms
And
Fill transport form
1m 2s 082ms
And
Get inputs from database "EDIT_ADVICE_DELIVERY" "super-admin-piast"
037ms
And
Expand advice panel
101ms
And
Edit advice in transport details
6s 562ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 073ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer"
5s 491ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
119ms
After
Hooks.cleanUserDetailsAfterTest()
162ms
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"
1s 637ms
And
Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
234ms
And
Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper"
1s 214ms
And
Show all transport types
1s 038ms
And
Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper"
46s 278ms
And
Go to "TRANSPORT_TABLE"
181ms
And
Go to transport details "LOAD"
2s 379ms
And
Get inputs from database "EDIT_LOAD" "super-admin-keeeper"
038ms
When
Go to transport details "LOAD"
3s 174ms
And
Fill transport form
25s 881ms
And
Get inputs from database "EDIT_ADVICE_LOAD" "super-admin-keeeper"
036ms
And
Expand advice panel
099ms
And
Edit advice in transport details
18s 490ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 109ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer"
36s 824ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
111ms
After
Hooks.cleanUserDetailsAfterTest()
233ms
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"
097ms
And
Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
140ms
And
Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd"
1s 353ms
And
Confirm status "ARRIVAL" by Public API "v1"
277ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu"
5s 199ms
Then
Check if user got a mail
000ms
And
Confirm status "DEPARTURE" by Public API "v1"
225ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd"
31s 286ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
137ms
After
Hooks.cleanUserDetailsAfterTest()
151ms
Scenario Outline
Check if verification mail was sent to transport creator
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-hochland"
096ms
And
Prepare company "Dostawca Hochland Automat 1" verification email setting "48h"
008ms
And
Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file
176ms
And
Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test"
2s 329ms
And
Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test"
15s 283ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji"
1m 23s 989ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
122ms
After
Hooks.cleanUserDetailsAfterTest()
252ms
After
Hooks.rollbackVerificationEmailSettingAfterTest()
007ms
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"
1s 545ms
And
Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file
194ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
1s 217ms
And
Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama"
2s 615ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja"
5s 186ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
093ms
After
Hooks.cleanUserDetailsAfterTest()
271ms
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"
956ms
And
Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file
288ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
1s 218ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
2s 137ms
And
Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama"
456ms
And
Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama"
415ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia"
10s 387ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
077ms
After
Hooks.cleanUserDetailsAfterTest()
259ms
Scenario Outline
Check mail after bid has been added to auction
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz"
2s 547ms
And
Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file
422ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
1s 236ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"
2s 098ms
And
Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test"
185ms
And
Wait till auction end
1m 58s 018ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę"
5s 788ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
090ms
After
Hooks.cleanUserDetailsAfterTest()
298ms
Scenario Outline
Check mail after auction without bids
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "adama-admin" and set token of apiUsername "super-admin-adama"
1s 118ms
And
Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
201ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
1s 229ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
2s 128ms
And
Wait till auction end
1m 58s 019ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert"
5s 472ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
084ms
After
Hooks.cleanUserDetailsAfterTest()
166ms
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"
1s 539ms
And
Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file
325ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
1s 205ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
2s 126ms
And
Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama"
181ms
And
Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama"
303ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana"
15s 678ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
105ms
After
Hooks.cleanUserDetailsAfterTest()
283ms
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"
1s 095ms
And
Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file
333ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
1s 234ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
2s 126ms
And
Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama"
203ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie"
2m 27s 305ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
098ms
After
Hooks.cleanUserDetailsAfterTest()
289ms
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"
1s 111ms
And
Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file
329ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
1s 243ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama"
2s 138ms
And
Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama"
305ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie"
5s 203ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
086ms
After
Hooks.cleanUserDetailsAfterTest()
252ms
Scenario Outline
Check mail two hours before auction ends
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama"
1s 638ms
And
Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file
340ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
1s 232ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes
2s 177ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji"
20s 795ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
087ms
After
Hooks.cleanUserDetailsAfterTest()
275ms
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"
1s 308ms
And
Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
603ms
And
Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland"
1s 412ms
And
Go to "TRANSPORT_TABLE"
127ms
And
Go to transport details "DELIVERY"
2s 667ms
And
Get inputs from database "EDIT_DELIVERY" "super-admin-hochland"
036ms
And
Fill transport form
35s 559ms
And
Open section: "discrepancy-report-panel"
1s 079ms
And
Fill discrepancy report section
49s 534ms
And
Go to transport details "DELIVERY"
2s 422ms
And
Change filled value in details "rodo-acceptance" "checkbox" "true" "0"
1s 296ms
And
Generate discrepancy report
18s 265ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności"
5s 795ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
111ms
After
Hooks.cleanUserDetailsAfterTest()
393ms
Scenario Outline
Check if mail was sent after updating mode of transportation
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Set token of apiUsername "super-admin-bausch"
098ms
And
Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file
388ms
When
Create default mode of transportation by API with "pba1-carrier"
146ms
Then
Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000"
094ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany"
5s 346ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
305ms
After
Hooks.deleteModeOfTransportationAfterTest()
098ms
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"
109ms
And
Prepare user "super-admin-bausch" details with all notifications and "apolloautomattest@gmail.com" by JSON file
357ms
When
Create default mode of transportation by API with "pba1-carrier"
082ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu"
5s 313ms
Then
Check if user got a mail
000ms
After
Hooks.cleanUserDetailsAfterTest()
276ms
After
Hooks.deleteModeOfTransportationAfterTest()
061ms
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"
2s 294ms
And
Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file
386ms
And
Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin"
036ms
And
Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland"
1s 411ms
And
Go to "WAREHOUSE_TAB"
744ms
And
Select warehouse "Serownia"
1s 376ms
And
Set week view
1s 119ms
And
Show yesterday
1s 055ms
And
Move window into the past
297ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na"
42s 836ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
116ms
After
Hooks.cleanUserDetailsAfterTest()
327ms
After
Hooks.rollbackAddedAuthorities()
024ms
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"
2s 201ms
And
Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
341ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
1s 277ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import"
54s 495ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
061ms
After
Hooks.cleanUserDetailsAfterTest()
247ms
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"
1s 793ms
And
Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file
357ms
And
Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz"
1s 266ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport"
53s 774ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
109ms
After
Hooks.cleanUserDetailsAfterTest()
342ms
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"
1s 104ms
And
Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file
358ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
1s 225ms
And
Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true"
19s 190ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację"
5s 343ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
092ms
After
Hooks.cleanUserDetailsAfterTest()
247ms
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"
1s 085ms
And
Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file
340ms
And
Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama"
1s 243ms
And
Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false"
19s 198ms
When
Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie"
5s 359ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
075ms
After
Hooks.cleanUserDetailsAfterTest()
279ms
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"
1s 936ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file
438ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
1s 216ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"
2s 163ms
And
Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test"
205ms
And
Add a bid "500" to an auction by JSON file as "pskza2-carrier-2@qa.qa-test" for "pskza2-carrier-2@qa.qa-test"
202ms
Then
If user is login then logout
239ms
And
Login as "swisskrono-admin"
995ms
And
Go to auction details
1s 195ms
And
Pass transport to carrier from auction details
1s 245ms
And
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia"
2m 45s 698ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
200ms
After
Hooks.cleanUserDetailsAfterTest()
437ms
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"
1s 224ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file
461ms
And
Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz"
1s 235ms
And
Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"
2s 154ms
And
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe"
5s 333ms
Then
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
080ms
After
Hooks.cleanUserDetailsAfterTest()
333ms
Scenario Outline
Check if remind password http status is ok
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-adama"
096ms
And
Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file
239ms
Then
Send password remind email "automaty10@o2.pl" and check if status is ok
076ms
After
Hooks.cleanUserDetailsAfterTest()
170ms
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"
1s 067ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
353ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 300ms
When
Click button advice in transport table "CONTAINER"
085ms
And
Set advice window in schedule
2s 541ms
And
Fill advice form
14s 431ms
And
Click advice save button and wait for advice form to disappear
30s 744ms
And
Go to "TRANSPORT_TABLE"
185ms
And
Go to transport details "CONTAINER"
2s 452ms
Then
Check are advice values equals
2s 264ms
After
Hooks.deleteTransportAfterTest()
110ms
After
Hooks.cleanUserDetailsAfterTest()
271ms
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)
002ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
1s 853ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
335ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
036ms
And
Add transport by SKApi in "MGW" assigned to ""
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
3s 355ms
When
Click button advice in transport table "OWN_COLLECTION"
102ms
And
Set advice window in schedule
2s 526ms
And
Fill advice form
14s 438ms
And
Click advice save button and wait for advice form to disappear
30s 732ms
And
Go to "TRANSPORT_TABLE"
182ms
And
Go to transport details "OWN_COLLECTION"
2s 425ms
Then
Check are advice values equals
2s 292ms
After
Hooks.deleteTransportAfterTest()
143ms
After
Hooks.cleanUserDetailsAfterTest()
268ms
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"
1s 905ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
346ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
038ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
5s 803ms
When
Click button advice in transport table "TRANSPORT_ORDER"
085ms
And
Set advice window in schedule
2s 547ms
And
Fill advice form
14s 437ms
And
Click advice save button and wait for advice form to disappear
30s 710ms
And
Go to "TRANSPORT_TABLE"
222ms
And
Go to transport details "TRANSPORT_ORDER"
2s 437ms
Then
Check are advice values equals
2s 287ms
After
Hooks.deleteTransportAfterTest()
099ms
After
Hooks.cleanUserDetailsAfterTest()
278ms
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@qa.qa-test" and set token of apiUsername "super-admin-skz"
2s 092ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
490ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
043ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
034ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
2s 797ms
When
Click button advice in transport table "TRANSPORT_ORDER"
082ms
And
Set advice window in schedule
2s 516ms
And
Fill advice form
14s 426ms
And
Click advice save button and wait for advice form to disappear
30s 727ms
And
Go to "TRANSPORT_TABLE"
216ms
And
Go to transport details "TRANSPORT_ORDER"
2s 426ms
Then
Check are advice values equals
2s 281ms
After
Hooks.deleteTransportAfterTest()
109ms
After
Hooks.cleanUserDetailsAfterTest()
375ms
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@qa.qa-test" and set token of apiUsername "super-admin-skz"
1s 767ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
267ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
042ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
5s 885ms
When
Click button advice in transport table "TRANSPORT_ORDER"
102ms
And
Set advice window in schedule
30s 598ms
org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of element located by By.xpath: //div[contains(@class, 'success-alert')] (tried for 30 second(s) with 500 MILLISECONDS interval)
at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
at Pages.BasePage.checkElementIsVisible(BasePage.java:177)
at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:85)
at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //div[contains(@class, 'success-alert')]
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: driver.version: unknown
at org.openqa.selenium.support.ui.ExpectedConditions.lambda$findElement$0(ExpectedConditions.java:882)
at java.util.Optional.orElseThrow(Optional.java:290)
at org.openqa.selenium.support.ui.ExpectedConditions.findElement(ExpectedConditions.java:881)
at org.openqa.selenium.support.ui.ExpectedConditions.access$000(ExpectedConditions.java:43)
at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:205)
at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:201)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208)
at Pages.BasePage.checkElementIsVisible(BasePage.java:177)
at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:85)
at sun.reflect.GeneratedMethodAccessor240.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at cucumber.runtime.Utils$1.call(Utils.java:26)
at cucumber.runtime.Timeout.timeout(Timeout.java:16)
at cucumber.runtime.Utils.invoke(Utils.java:20)
at cucumber.runtime.java.JavaStepDefinition.execute(JavaStepDefinition.java:57)
at cucumber.runner.PickleStepDefinitionMatch.runStep(PickleStepDefinitionMatch.java:50)
at cucumber.runner.TestStep.executeStep(TestStep.java:63)
at cucumber.runner.TestStep.run(TestStep.java:49)
at cucumber.runner.PickleStepTestStep.run(PickleStepTestStep.java:43)
at cucumber.runner.TestCase.run(TestCase.java:45)
at cucumber.runner.Runner.runPickle(Runner.java:40)
at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
And
Fill advice form
000ms
And
Click advice save button and wait for advice form to disappear
000ms
And
Go to "TRANSPORT_TABLE"
000ms
And
Go to transport details "TRANSPORT_ORDER"
000ms
Then
Check are advice values equals
000ms
After
Hooks.deleteTransportAfterTest()
062ms
After
Hooks.cleanUserDetailsAfterTest()
213ms
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"
1s 801ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
338ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
039ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
6s 373ms
When
Click button advice in transport table "OWN_COLLECTION"
102ms
And
Set advice window in schedule
2s 526ms
And
Fill advice form
14s 436ms
And
Click advice save button and wait for advice form to disappear
30s 719ms
And
Go to "TRANSPORT_TABLE"
172ms
Then
Check advice data in SK API database "OWN_COLLECTION"
155ms
After
Hooks.deleteTransportAfterTest()
114ms
After
Hooks.cleanUserDetailsAfterTest()
290ms
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"
1s 833ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
324ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
036ms
And
Add transport by SKApi in "MGW" assigned to ""
003ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 304ms
When
Click button advice in transport table "CONTAINER"
089ms
And
Set advice window in schedule
2s 532ms
And
Fill advice form
14s 394ms
And
Click advice save button and wait for advice form to disappear
30s 685ms
And
Go to "TRANSPORT_TABLE"
190ms
Then
Check advice data in SK API database "CONTAINER"
105ms
After
Hooks.deleteTransportAfterTest()
100ms
After
Hooks.cleanUserDetailsAfterTest()
258ms
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"
1s 821ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
318ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
039ms
And
Add transport by SKApi in "MGW" assigned to ""
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
036ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
5s 843ms
When
Click button advice in transport table "TRANSPORT_ORDER"
095ms
And
Set advice window in schedule
2s 509ms
And
Fill advice form
14s 448ms
And
Click advice save button and wait for advice form to disappear
30s 751ms
And
Go to "TRANSPORT_TABLE"
235ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
031ms
After
Hooks.deleteTransportAfterTest()
107ms
After
Hooks.cleanUserDetailsAfterTest()
325ms
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@qa.qa-test" and set token of apiUsername "super-admin-skz"
1s 692ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
516ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW" assigned to ""
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
038ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 818ms
When
Click button advice in transport table "TRANSPORT_ORDER"
083ms
And
Set advice window in schedule
2s 538ms
And
Fill advice form
14s 489ms
And
Click advice save button and wait for advice form to disappear
30s 699ms
And
Go to "TRANSPORT_TABLE"
204ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
039ms
After
Hooks.deleteTransportAfterTest()
119ms
After
Hooks.cleanUserDetailsAfterTest()
334ms
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)
002ms
Given
Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz"
1s 965ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
272ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
037ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
002ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
033ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 792ms
When
Click button advice in transport table "TRANSPORT_ORDER"
089ms
And
Set advice window in schedule
2s 501ms
And
Fill advice form
14s 463ms
And
Click advice save button and wait for advice form to disappear
30s 721ms
And
Go to "TRANSPORT_TABLE"
188ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
090ms
After
Hooks.deleteTransportAfterTest()
121ms
After
Hooks.cleanUserDetailsAfterTest()
245ms
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"
1s 453ms
And
Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file
234ms
And
Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file
182ms
And
Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file
129ms
And
Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen"
1s 215ms
And
Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen"
1s 300ms
And
Check if reject date is not visible
15s 022ms
When
Reject status: Book of disinfection
079ms
And
Check if reject date is visible
327ms
Then
If user is login then logout
214ms
And
Login as "lantmannen-admin"
856ms
And
Check if note was added to transport after status rejection
1s 241ms
And
Check if history note was added to transport after status rejection - "LOAD"
3s 536ms
And
Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji"
5s 478ms
And
Check if user got a mail
000ms
After
Hooks.deleteTransportAfterTest()
076ms
After
Hooks.cleanUserDetailsAfterTest()
146ms
After
Hooks.rollbackWarehousesAccess()
111ms
Scenario Outline
Permission - Edit user main data [A-7965]
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Set token of apiUsername "super-admin-adama"
091ms
And
Set basic authorities "ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test"
038ms
When
Login as "oaa1-receiver-2@qa.qa-test"
1s 147ms
And
Go to user "oaa1-receiver@qa.qa-test" details edition
078ms
And
Change user details "email" to "newEmailAddress@newEmail.com"
15s 059ms
org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to be clickable: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
at Pages.BasePage.waitUntilElementClickable(BasePage.java:223)
at CucumberTests.User.EditUserTest.changeUserEmailAddressByAccountDetails(EditUserTest.java:189)
at ✽.Change user details "email" to "newEmailAddress@newEmail.com"(file:Features/Atom/Users/UserAuthority.feature:9)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //button[@data-button-name='save']
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: driver.version: unknown
at org.openqa.selenium.support.ui.ExpectedConditions.lambda$findElement$0(ExpectedConditions.java:882)
at java.util.Optional.orElseThrow(Optional.java:290)
at org.openqa.selenium.support.ui.ExpectedConditions.findElement(ExpectedConditions.java:881)
at org.openqa.selenium.support.ui.ExpectedConditions.access$000(ExpectedConditions.java:43)
at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:205)
at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:201)
at org.openqa.selenium.support.ui.ExpectedConditions$22.apply(ExpectedConditions.java:643)
at org.openqa.selenium.support.ui.ExpectedConditions$22.apply(ExpectedConditions.java:640)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208)
at Pages.BasePage.waitUntilElementClickable(BasePage.java:223)
at CucumberTests.User.EditUserTest.changeUserEmailAddressByAccountDetails(EditUserTest.java:189)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at cucumber.runtime.Utils$1.call(Utils.java:26)
at cucumber.runtime.Timeout.timeout(Timeout.java:16)
at cucumber.runtime.Utils.invoke(Utils.java:20)
at cucumber.runtime.java.JavaStepDefinition.execute(JavaStepDefinition.java:57)
at cucumber.runner.PickleStepDefinitionMatch.runStep(PickleStepDefinitionMatch.java:50)
at cucumber.runner.TestStep.executeStep(TestStep.java:63)
at cucumber.runner.TestStep.run(TestStep.java:49)
at cucumber.runner.PickleStepTestStep.run(PickleStepTestStep.java:43)
at cucumber.runner.TestCase.run(TestCase.java:45)
at cucumber.runner.Runner.runPickle(Runner.java:40)
at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
And
Change user details "phone" to "123456789"
000ms
Then
Save user details
000ms
After
Hooks.cleanUserDetailsAfterTest()
000ms
java.lang.NullPointerException
at Utils.JsonApiUtil.editJsonTextNode(JsonApiUtil.java:158)
at CucumberTests.Hooks.cleanUserDetailsAfterTest(Hooks.java:335)
at sun.reflect.GeneratedMethodAccessor261.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at cucumber.runtime.Utils$1.call(Utils.java:26)
at cucumber.runtime.Timeout.timeout(Timeout.java:16)
at cucumber.runtime.Utils.invoke(Utils.java:20)
at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
at cucumber.runner.TestStep.executeStep(TestStep.java:63)
at cucumber.runner.TestStep.run(TestStep.java:49)
at cucumber.runner.TestCase.run(TestCase.java:49)
at cucumber.runner.Runner.runPickle(Runner.java:40)
at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
After
Hooks.rollbackAddedAuthorities()
060ms