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 472ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 359ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW" assigned to ""
022ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 905ms
When
Click button advice in transport table "CONTAINER"
207ms
And
Set advice window in schedule
3s 372ms
And
Fill advice form
17s 995ms
And
Click advice save button and wait for advice form to disappear
33s 290ms
And
Go to "TRANSPORT_TABLE"
440ms
And
Go to transport details "CONTAINER"
2s 895ms
Then
Check are advice values equals
2s 896ms
After
Hooks.deleteTransportAfterTest()
822ms
After
Hooks.cleanUserDetailsAfterTest()
2s 232ms
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"
7s 659ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 353ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW" assigned to ""
018ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
014ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 167ms
When
Click button advice in transport table "OWN_COLLECTION"
229ms
And
Set advice window in schedule
3s 364ms
And
Fill advice form
17s 938ms
And
Click advice save button and wait for advice form to disappear
33s 304ms
And
Go to "TRANSPORT_TABLE"
468ms
And
Go to transport details "OWN_COLLECTION"
2s 870ms
Then
Check are advice values equals
2s 882ms
After
Hooks.deleteTransportAfterTest()
834ms
After
Hooks.cleanUserDetailsAfterTest()
2s 056ms
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 412ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 336ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
024ms
And
Add transport by SKApi in "MGW" assigned to ""
028ms
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
4s 414ms
When
Click button advice in transport table "TRANSPORT_ORDER"
190ms
And
Set advice window in schedule
3s 391ms
And
Fill advice form
17s 860ms
And
Click advice save button and wait for advice form to disappear
33s 325ms
And
Go to "TRANSPORT_TABLE"
469ms
And
Go to transport details "TRANSPORT_ORDER"
2s 913ms
Then
Check are advice values equals
2s 902ms
After
Hooks.deleteTransportAfterTest()
869ms
After
Hooks.cleanUserDetailsAfterTest()
2s 244ms
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 773ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
3s 380ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW" assigned to ""
017ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 858ms
When
Click button advice in transport table "TRANSPORT_ORDER"
211ms
And
Set advice window in schedule
3s 288ms
And
Fill advice form
18s 014ms
And
Click advice save button and wait for advice form to disappear
18s 351ms
And
Go to "TRANSPORT_TABLE"
450ms
And
Go to transport details "TRANSPORT_ORDER"
2s 855ms
Then
Check are advice values equals
2s 934ms
After
Hooks.deleteTransportAfterTest()
855ms
After
Hooks.cleanUserDetailsAfterTest()
2s 741ms
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"
7s 603ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
1s 765ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
021ms
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 889ms
When
Click button advice in transport table "TRANSPORT_ORDER"
220ms
And
Set advice window in schedule
30s 589ms
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()
548ms
After
Hooks.cleanUserDetailsAfterTest()
1s 561ms
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 498ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 550ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW" assigned to ""
019ms
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 132ms
When
Click button advice in transport table "OWN_COLLECTION"
218ms
And
Set advice window in schedule
3s 278ms
And
Fill advice form
17s 935ms
And
Click advice save button and wait for advice form to disappear
33s 199ms
And
Go to "TRANSPORT_TABLE"
437ms
Then
Check advice data in SK API database "OWN_COLLECTION"
416ms
After
Hooks.deleteTransportAfterTest()
803ms
After
Hooks.cleanUserDetailsAfterTest()
2s 088ms
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 837ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 334ms
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"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 938ms
When
Click button advice in transport table "CONTAINER"
224ms
And
Set advice window in schedule
3s 380ms
And
Fill advice form
17s 862ms
And
Click advice save button and wait for advice form to disappear
33s 243ms
And
Go to "TRANSPORT_TABLE"
461ms
Then
Check advice data in SK API database "CONTAINER"
197ms
After
Hooks.deleteTransportAfterTest()
831ms
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 444ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 369ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW" assigned to ""
017ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
7s 357ms
When
Click button advice in transport table "TRANSPORT_ORDER"
231ms
And
Set advice window in schedule
3s 333ms
And
Fill advice form
17s 888ms
And
Click advice save button and wait for advice form to disappear
33s 307ms
And
Go to "TRANSPORT_TABLE"
467ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
091ms
After
Hooks.deleteTransportAfterTest()
823ms
After
Hooks.cleanUserDetailsAfterTest()
2s 071ms
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"
6s 729ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
3s 381ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW" assigned to ""
016ms
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
6s 948ms
When
Click button advice in transport table "TRANSPORT_ORDER"
219ms
And
Set advice window in schedule
3s 316ms
And
Fill advice form
17s 900ms
And
Click advice save button and wait for advice form to disappear
33s 201ms
And
Go to "TRANSPORT_TABLE"
470ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
092ms
After
Hooks.deleteTransportAfterTest()
860ms
After
Hooks.cleanUserDetailsAfterTest()
2s 791ms
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 448ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
1s 841ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
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
4s 454ms
When
Click button advice in transport table "TRANSPORT_ORDER"
225ms
And
Set advice window in schedule
3s 303ms
And
Fill advice form
18s 060ms
And
Click advice save button and wait for advice form to disappear
33s 838ms
And
Go to "TRANSPORT_TABLE"
419ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
250ms
After
Hooks.deleteTransportAfterTest()
846ms
After
Hooks.cleanUserDetailsAfterTest()
1s 735ms
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"
7s 650ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
018ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 933ms
When
Click button advice in transport table "CONTAINER"
213ms
And
Set advice window in schedule in the past
3s 304ms
And
Fill advice form
17s 952ms
And
Click advice save button to check error message
200ms
Then
Check if possible advice alert is displayed
067ms
After
Hooks.deleteTransportAfterTest()
599ms
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 686ms
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 "EDIT_ADVICE" "super-admin-skz"
017ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
4s 147ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
54s 880ms
And
Go to "TRANSPORT_TABLE"
405ms
When
Go to transport details "OWN_COLLECTION"
2s 830ms
And
Expand advice panel
303ms
And
Edit advice in transport details
16s 578ms
And
Fill arrival date field
2s 649ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 213ms
Then
Check advice data in database after edition "OWN_COLLECTION"
101ms
After
Hooks.deleteTransportAfterTest()
762ms
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 628ms
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"
016ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 925ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
54s 941ms
And
Go to "TRANSPORT_TABLE"
444ms
When
Go to transport details "CONTAINER"
2s 921ms
And
Expand advice panel
291ms
And
Edit advice in transport details
16s 457ms
And
Fill arrival date field
2s 604ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 247ms
Then
Check advice data in database after edition "CONTAINER"
109ms
After
Hooks.deleteTransportAfterTest()
808ms
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 630ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
018ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
016ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 599ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
55s 409ms
And
Go to "TRANSPORT_TABLE"
426ms
When
Go to transport details "TRANSPORT_ORDER"
2s 851ms
And
Expand advice panel
316ms
And
Edit advice in transport details
16s 534ms
And
Fill arrival date field
2s 602ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 199ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
107ms
After
Hooks.deleteTransportAfterTest()
846ms