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 522ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 419ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
020ms
And
Check is transport "CONTAINER" created in transport table and set transport id
6s 962ms
When
Click button advice in transport table "CONTAINER"
215ms
And
Set advice window in schedule
3s 397ms
And
Fill advice form
20s 230ms
And
Click advice save button and wait for advice form to disappear
33s 258ms
And
Go to "TRANSPORT_TABLE"
447ms
And
Go to transport details "CONTAINER"
2s 864ms
Then
Check are advice values equals
4s 953ms
After
Hooks.deleteTransportAfterTest()
786ms
After
Hooks.cleanUserDetailsAfterTest()
2s 295ms
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 583ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 378ms
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"
019ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 161ms
When
Click button advice in transport table "OWN_COLLECTION"
236ms
And
Set advice window in schedule
3s 336ms
And
Fill advice form
20s 289ms
And
Click advice save button and wait for advice form to disappear
33s 270ms
And
Go to "TRANSPORT_TABLE"
448ms
And
Go to transport details "OWN_COLLECTION"
2s 857ms
Then
Check are advice values equals
4s 987ms
After
Hooks.deleteTransportAfterTest()
825ms
After
Hooks.cleanUserDetailsAfterTest()
2s 189ms
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 345ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 386ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
031ms
And
Add transport by SKApi in "MGW" assigned to ""
018ms
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 294ms
When
Click button advice in transport table "TRANSPORT_ORDER"
248ms
And
Set advice window in schedule
3s 327ms
And
Fill advice form
20s 285ms
And
Click advice save button and wait for advice form to disappear
33s 317ms
And
Go to "TRANSPORT_TABLE"
492ms
And
Go to transport details "TRANSPORT_ORDER"
2s 838ms
Then
Check are advice values equals
4s 967ms
After
Hooks.deleteTransportAfterTest()
818ms
After
Hooks.cleanUserDetailsAfterTest()
2s 347ms
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 667ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
3s 446ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW" assigned to ""
018ms
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
6s 956ms
When
Click button advice in transport table "TRANSPORT_ORDER"
222ms
And
Set advice window in schedule
3s 375ms
And
Fill advice form
20s 342ms
And
Click advice save button and wait for advice form to disappear
33s 289ms
And
Go to "TRANSPORT_TABLE"
514ms
And
Go to transport details "TRANSPORT_ORDER"
2s 904ms
Then
Check are advice values equals
5s 016ms
After
Hooks.deleteTransportAfterTest()
827ms
After
Hooks.cleanUserDetailsAfterTest()
2s 738ms
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 494ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
1s 701ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
020ms
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
7s 601ms
When
Click button advice in transport table "TRANSPORT_ORDER"
266ms
And
Set advice window in schedule
30s 586ms
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:90)
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:90)
at sun.reflect.GeneratedMethodAccessor242.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()
552ms
After
Hooks.cleanUserDetailsAfterTest()
1s 789ms
Scenario Outline
Verify that advice data are saved properly
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 642ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 362ms
And
Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz"
023ms
And
Add transport by SKApi in "MGW" assigned to ""
025ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
017ms
And
Check is transport "OWN_COLLECTION" created in transport table and set transport id
7s 147ms
When
Click button advice in transport table "OWN_COLLECTION"
227ms
And
Set advice window in schedule
3s 393ms
And
Fill advice form
20s 447ms
And
Click advice save button and wait for advice form to disappear
33s 319ms
And
Go to "TRANSPORT_TABLE"
441ms
Then
Check advice data in SK API database "OWN_COLLECTION"
452ms
After
Hooks.deleteTransportAfterTest()
801ms
After
Hooks.cleanUserDetailsAfterTest()
2s 144ms
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 394ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 362ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW" assigned to ""
018ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
029ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 922ms
When
Click button advice in transport table "CONTAINER"
220ms
And
Set advice window in schedule
3s 395ms
And
Fill advice form
20s 312ms
And
Click advice save button and wait for advice form to disappear
33s 297ms
And
Go to "TRANSPORT_TABLE"
452ms
Then
Check advice data in SK API database "CONTAINER"
238ms
After
Hooks.deleteTransportAfterTest()
836ms
After
Hooks.cleanUserDetailsAfterTest()
2s 337ms
Scenario Outline
Verify that advice data are saved properly
The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.
Before
Hooks.showScenarioName(Scenario)
000ms
Given
Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz"
7s 472ms
And
Prepare user "swisskrono-admin" details with all notifications and "" by JSON file
2s 383ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
022ms
And
Add transport by SKApi in "MGW" assigned to ""
021ms
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
4s 212ms
When
Click button advice in transport table "TRANSPORT_ORDER"
220ms
And
Set advice window in schedule
3s 293ms
And
Fill advice form
20s 337ms
And
Click advice save button and wait for advice form to disappear
33s 271ms
And
Go to "TRANSPORT_TABLE"
459ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
095ms
After
Hooks.deleteTransportAfterTest()
872ms
After
Hooks.cleanUserDetailsAfterTest()
2s 113ms
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 432ms
And
Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file
3s 447ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW" assigned to ""
018ms
And
Get inputs from database "CREATE_ADVICE" "super-admin-skz"
020ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 796ms
When
Click button advice in transport table "TRANSPORT_ORDER"
206ms
And
Set advice window in schedule
3s 317ms
And
Fill advice form
20s 213ms
And
Click advice save button and wait for advice form to disappear
33s 797ms
And
Go to "TRANSPORT_TABLE"
522ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
087ms
After
Hooks.deleteTransportAfterTest()
841ms
After
Hooks.cleanUserDetailsAfterTest()
2s 953ms
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 805ms
And
Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file
1s 907ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
021ms
And
Add transport by SKApi in "MGW" assigned to "automaty@test.pl"
017ms
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
7s 590ms
When
Click button advice in transport table "TRANSPORT_ORDER"
213ms
And
Set advice window in schedule
3s 303ms
And
Fill advice form
20s 387ms
And
Click advice save button and wait for advice form to disappear
33s 776ms
And
Go to "TRANSPORT_TABLE"
417ms
Then
Check advice data in SK API database "TRANSPORT_ORDER"
266ms
After
Hooks.deleteTransportAfterTest()
874ms
After
Hooks.cleanUserDetailsAfterTest()
1s 642ms
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 378ms
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 916ms
When
Click button advice in transport table "CONTAINER"
214ms
And
Set advice window in schedule in the past
3s 351ms
And
Fill advice form
20s 425ms
And
Click advice save button to check error message
183ms
Then
Check if possible advice alert is displayed
062ms
After
Hooks.deleteTransportAfterTest()
555ms
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_OWN_COLLECTION" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW" assigned to ""
017ms
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 121ms
And
Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz"
57s 122ms
And
Go to "TRANSPORT_TABLE"
405ms
When
Go to transport details "OWN_COLLECTION"
2s 818ms
And
Expand advice panel
298ms
And
Edit advice in transport details
18s 749ms
And
Fill arrival date field
2s 603ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 232ms
Then
Check advice data in database after edition "OWN_COLLECTION"
107ms
After
Hooks.deleteTransportAfterTest()
825ms
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 640ms
And
Get inputs from database "CREATE_CONTAINER" "super-admin-skz"
019ms
And
Add transport by SKApi in "MGW" assigned to ""
023ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
022ms
And
Check is transport "CONTAINER" created in transport table and set transport id
3s 925ms
And
Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz"
57s 143ms
And
Go to "TRANSPORT_TABLE"
417ms
When
Go to transport details "CONTAINER"
2s 852ms
And
Expand advice panel
278ms
And
Edit advice in transport details
18s 822ms
And
Fill arrival date field
2s 623ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 225ms
Then
Check advice data in database after edition "CONTAINER"
089ms
After
Hooks.deleteTransportAfterTest()
806ms
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 644ms
And
Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz"
020ms
And
Add transport by SKApi in "MGW" assigned to ""
019ms
And
Get inputs from database "EDIT_ADVICE" "super-admin-skz"
019ms
And
Check is transport "TRANSPORT_ORDER" created in transport table and set transport id
3s 602ms
And
Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz"
57s 286ms
And
Go to "TRANSPORT_TABLE"
451ms
When
Go to transport details "TRANSPORT_ORDER"
2s 862ms
And
Expand advice panel
239ms
And
Edit advice in transport details
18s 799ms
And
Fill arrival date field
2s 632ms
And
Click "save-transport-and-close" save button and wait for form to disappear
30s 168ms
Then
Check advice data in database after edition "TRANSPORT_ORDER"
101ms
After
Hooks.deleteTransportAfterTest()
803ms