Scenario Outline
Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
2s 574ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 394ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW" assigned to ""
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 926ms
When
Click button advice in transport table "CONTAINER"
217ms
And
Set advice window in schedule
3s 406ms
And
Fill advice form
17s 890ms
And
Click advice save button and wait for advice form to disappear
33s 298ms
And
Go to "TRANSPORT_TABLE"
406ms
And
Go to transport details "CONTAINER"
2s 909ms
Then
Check are advice values equals
2s 928ms
After
Hooks.deleteTransportAfterTest()
900ms
After
Hooks.cleanUserDetailsAfterTest()
2s 250ms
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 867ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 348ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW" assigned to ""
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 158ms
When
Click button advice in transport table "OWN_COLLECTION"
201ms
And
Set advice window in schedule
3s 423ms
And
Fill advice form
18s 020ms
And
Click advice save button and wait for advice form to disappear
33s 306ms
And
Go to "TRANSPORT_TABLE"
479ms
And
Go to transport details "OWN_COLLECTION"
2s 881ms
Then
Check are advice values equals
2s 875ms
After
Hooks.deleteTransportAfterTest()
930ms
After
Hooks.cleanUserDetailsAfterTest()
2s 137ms
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 723ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 392ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW" assigned to ""
023ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
4s 218ms
When
Click button advice in transport table "TRANSPORT_ORDER"
215ms
And
Set advice window in schedule
3s 372ms
And
Fill advice form
18s 310ms
And
Click advice save button and wait for advice form to disappear
33s 845ms
And
Go to "TRANSPORT_TABLE"
500ms
And
Go to transport details "TRANSPORT_ORDER"
2s 909ms
Then
Check are advice values equals
2s 902ms
After
Hooks.deleteTransportAfterTest()
927ms
After
Hooks.cleanUserDetailsAfterTest()
2s 223ms
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"
8s 984ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
3s 679ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW" assigned to ""
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
015ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
7s 074ms
When
Click button advice in transport table "TRANSPORT_ORDER"
230ms
And
Set advice window in schedule
3s 345ms
And
Fill advice form
18s 116ms
And
Click advice save button and wait for advice form to disappear
18s 379ms
And
Go to "TRANSPORT_TABLE"
485ms
And
Go to transport details "TRANSPORT_ORDER"
2s 901ms
Then
Check are advice values equals
2s 909ms
After
Hooks.deleteTransportAfterTest()
897ms
After
Hooks.cleanUserDetailsAfterTest()
2s 725ms
Scenario Outline
Check if it possible to advice transport when transport is created by sk API
The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz"
7s 571ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
1s 842ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
018ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
020ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
019ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
4s 498ms
When
Click button advice in transport table "TRANSPORT_ORDER"
226ms
And
Set advice window in schedule
30s 625ms
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-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: 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()
626ms
After
Hooks.cleanUserDetailsAfterTest()
1s 713ms
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 511ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 367ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW" assigned to ""
018ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 142ms
When
Click button advice in transport table "OWN_COLLECTION"
204ms
And
Set advice window in schedule
3s 480ms
And
Fill advice form
17s 879ms
And
Click advice save button and wait for advice form to disappear
33s 266ms
And
Go to "TRANSPORT_TABLE"
405ms
Then
Check advice data in SK API database "OWN_COLLECTION"
467ms
After
Hooks.deleteTransportAfterTest()
1s 079ms
After
Hooks.cleanUserDetailsAfterTest()
2s 117ms
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 697ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 374ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 955ms
When
Click button advice in transport table "CONTAINER"
213ms
And
Set advice window in schedule
3s 434ms
And
Fill advice form
17s 645ms
And
Click advice save button and wait for advice form to disappear
33s 273ms
And
Go to "TRANSPORT_TABLE"
437ms
Then
Check advice data in SK API database "CONTAINER"
238ms
After
Hooks.deleteTransportAfterTest()
1s 028ms
After
Hooks.cleanUserDetailsAfterTest()
2s 280ms
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 410ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 380ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW" assigned to ""
019ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
7s 277ms
When
Click button advice in transport table "TRANSPORT_ORDER"
227ms
And
Set advice window in schedule
3s 352ms
And
Fill advice form
17s 935ms
And
Click advice save button and wait for advice form to disappear
33s 315ms
And
Go to "TRANSPORT_TABLE"
452ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
091ms
After
Hooks.deleteTransportAfterTest()
1s 018ms
After
Hooks.cleanUserDetailsAfterTest()
2s 094ms
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@qa.qa-test" and set token of apiUsername "super-admin-skz"
7s 075ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
3s 398ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW" assigned to ""
017ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
014ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 900ms
When
Click button advice in transport table "TRANSPORT_ORDER"
206ms
And
Set advice window in schedule
3s 410ms
And
Fill advice form
17s 960ms
And
Click advice save button and wait for advice form to disappear
33s 777ms
And
Go to "TRANSPORT_TABLE"
447ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
083ms
After
Hooks.deleteTransportAfterTest()
963ms
After
Hooks.cleanUserDetailsAfterTest()
2s 859ms
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@qa.qa-test" and set token of apiUsername "super-admin-skz"
8s 600ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
1s 889ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
017ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
4s 532ms
When
Click button advice in transport table "TRANSPORT_ORDER"
210ms
And
Set advice window in schedule
3s 322ms
And
Fill advice form
17s 900ms
And
Click advice save button and wait for advice form to disappear
33s 805ms
And
Go to "TRANSPORT_TABLE"
418ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
264ms
After
Hooks.deleteTransportAfterTest()
928ms
After
Hooks.cleanUserDetailsAfterTest()
1s 671ms
Scenario Outline
Check if not possible to advice transport in the past when advice is created from transports table and transport is created by sk API
Before
Hooks.showScenarioName(Scenario)
001ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
8s 039ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
024ms
And
Add transport by SKApi in "MGW" assigned to ""
030ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 940ms
When
Click button advice in transport table "CONTAINER"
199ms
And
Set advice window in schedule in the past
3s 347ms
And
Fill advice form
17s 936ms
And
Click advice save button to check error message
175ms
Then
Check if possible advice alert is displayed
068ms
After
Hooks.deleteTransportAfterTest()
576ms
Scenario Outline
Check if advice data saved in SK API database after edition
The scenario checks if you can correctly edit an advice. After that 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"
2s 713ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW" assigned to ""
020ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 112ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 964ms
And
Go to "TRANSPORT_TABLE"
392ms
When
Go to transport details "OWN_COLLECTION"
2s 912ms
And
Expand advice panel
423ms
And
Edit advice in transport details
16s 574ms
And
Fill arrival date field
2s 609ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 195ms
Then
Check advice data in database after edition "OWN_COLLECTION"
093ms
After
Hooks.deleteTransportAfterTest()
850ms
Scenario Outline
Check if advice data saved in SK API database after edition
The scenario checks if you can correctly edit an advice. After that 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"
2s 659ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW" assigned to ""
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 923ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 945ms
And
Go to "TRANSPORT_TABLE"
406ms
When
Go to transport details "CONTAINER"
2s 884ms
And
Expand advice panel
292ms
And
Edit advice in transport details
16s 543ms
And
Fill arrival date field
2s 654ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 218ms
Then
Check advice data in database after edition "CONTAINER"
081ms
After
Hooks.deleteTransportAfterTest()
876ms
Scenario Outline
Check if advice data saved in SK API database after edition
The scenario checks if you can correctly edit an advice. After that 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"
2s 801ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW" assigned to ""
029ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
7s 421ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
39s 886ms
And
Go to "TRANSPORT_TABLE"
452ms
When
Go to transport details "TRANSPORT_ORDER"
2s 861ms
And
Expand advice panel
288ms
And
Edit advice in transport details
16s 531ms
And
Fill arrival date field
2s 614ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 276ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
082ms
After
Hooks.deleteTransportAfterTest()
923ms