Project Number Date
ApolloFullRunnerReport apollo-test-2.106 05 sie 2021, 05:40

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
SK Api - Advice transport 168 1 5 0 0 174 13 1 14 18m 46s 495ms Failed
Feature SK Api - Advice transport
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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 356ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 410ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
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 7s 152ms
When Click button advice in transport table "CONTAINER" 262ms
And Set advice window in schedule 3s 341ms
And Fill advice form 20s 415ms
And Click advice save button and wait for advice form to disappear 33s 252ms
And Go to "TRANSPORT_TABLE" 443ms
And Go to transport details "CONTAINER" 2s 865ms
Then Check are advice values equals 4s 978ms
After Hooks.deleteTransportAfterTest() 799ms
After Hooks.cleanUserDetailsAfterTest() 2s 233ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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 587ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 384ms
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" 017ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 105ms
When Click button advice in transport table "OWN_COLLECTION" 230ms
And Set advice window in schedule 3s 443ms
And Fill advice form 20s 278ms
And Click advice save button and wait for advice form to disappear 33s 253ms
And Go to "TRANSPORT_TABLE" 460ms
And Go to transport details "OWN_COLLECTION" 2s 839ms
Then Check are advice values equals 4s 950ms
After Hooks.deleteTransportAfterTest() 795ms
After Hooks.cleanUserDetailsAfterTest() 2s 182ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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 314ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 328ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
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 7s 317ms
When Click button advice in transport table "TRANSPORT_ORDER" 204ms
And Set advice window in schedule 3s 355ms
And Fill advice form 20s 364ms
And Click advice save button and wait for advice form to disappear 33s 318ms
And Go to "TRANSPORT_TABLE" 445ms
And Go to transport details "TRANSPORT_ORDER" 2s 852ms
Then Check are advice values equals 4s 942ms
After Hooks.deleteTransportAfterTest() 812ms
After Hooks.cleanUserDetailsAfterTest() 2s 285ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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 892ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 607ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 024ms
And Add transport by SKApi in "MGW" assigned to "" 017ms
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 741ms
When Click button advice in transport table "TRANSPORT_ORDER" 238ms
And Set advice window in schedule 3s 345ms
And Fill advice form 20s 487ms
And Click advice save button and wait for advice form to disappear 18s 407ms
And Go to "TRANSPORT_TABLE" 471ms
And Go to transport details "TRANSPORT_ORDER" 2s 834ms
Then Check are advice values equals 4s 930ms
After Hooks.deleteTransportAfterTest() 813ms
After Hooks.cleanUserDetailsAfterTest() 2s 744ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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
Steps
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 462ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 720ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 022ms
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 534ms
When Click button advice in transport table "TRANSPORT_ORDER" 215ms
And Set advice window in schedule 30s 636ms
Error message 
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.GeneratedMethodAccessor241.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() 564ms
After Hooks.cleanUserDetailsAfterTest() 1s 933ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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 445ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 411ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "" 018ms
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 129ms
When Click button advice in transport table "OWN_COLLECTION" 227ms
And Set advice window in schedule 3s 349ms
And Fill advice form 20s 348ms
And Click advice save button and wait for advice form to disappear 33s 228ms
And Go to "TRANSPORT_TABLE" 486ms
Then Check advice data in SK API database "OWN_COLLECTION" 443ms
After Hooks.deleteTransportAfterTest() 803ms
After Hooks.cleanUserDetailsAfterTest() 2s 134ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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 491ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 393ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 023ms
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 "CONTAINER" created in transport table and set transport id 3s 891ms
When Click button advice in transport table "CONTAINER" 214ms
And Set advice window in schedule 3s 330ms
And Fill advice form 20s 399ms
And Click advice save button and wait for advice form to disappear 33s 246ms
And Go to "TRANSPORT_TABLE" 423ms
Then Check advice data in SK API database "CONTAINER" 234ms
After Hooks.deleteTransportAfterTest() 860ms
After Hooks.cleanUserDetailsAfterTest() 2s 316ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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 528ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 398ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 035ms
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 4s 286ms
When Click button advice in transport table "TRANSPORT_ORDER" 253ms
And Set advice window in schedule 3s 357ms
And Fill advice form 20s 419ms
And Click advice save button and wait for advice form to disappear 33s 250ms
And Go to "TRANSPORT_TABLE" 455ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 095ms
After Hooks.deleteTransportAfterTest() 885ms
After Hooks.cleanUserDetailsAfterTest() 2s 072ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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 314ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 646ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
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 3s 808ms
When Click button advice in transport table "TRANSPORT_ORDER" 214ms
And Set advice window in schedule 3s 294ms
And Fill advice form 19s 783ms
And Click advice save button and wait for advice form to disappear 33s 266ms
And Go to "TRANSPORT_TABLE" 487ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 095ms
After Hooks.deleteTransportAfterTest() 870ms
After Hooks.cleanUserDetailsAfterTest() 3s 018ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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 721ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 879ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 018ms
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 628ms
When Click button advice in transport table "TRANSPORT_ORDER" 248ms
And Set advice window in schedule 3s 319ms
And Fill advice form 20s 288ms
And Click advice save button and wait for advice form to disappear 33s 787ms
And Go to "TRANSPORT_TABLE" 462ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 278ms
After Hooks.deleteTransportAfterTest() 833ms
After Hooks.cleanUserDetailsAfterTest() 1s 627ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 439ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 023ms
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 "CONTAINER" created in transport table and set transport id 6s 941ms
When Click button advice in transport table "CONTAINER" 232ms
And Set advice window in schedule in the past 3s 317ms
And Fill advice form 20s 381ms
And Click advice save button to check error message 187ms
Then Check if possible advice alert is displayed 072ms
After Hooks.deleteTransportAfterTest() 576ms
@deleteTransportAfterTest
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_OWN_COLLECTION" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 016ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 139ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 287ms
And Go to "TRANSPORT_TABLE" 476ms
When Go to transport details "OWN_COLLECTION" 2s 849ms
And Expand advice panel 298ms
And Edit advice in transport details 18s 852ms
And Fill arrival date field 2s 641ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 230ms
Then Check advice data in database after edition "OWN_COLLECTION" 104ms
After Hooks.deleteTransportAfterTest() 797ms
@deleteTransportAfterTest
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 618ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
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 917ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 261ms
And Go to "TRANSPORT_TABLE" 458ms
When Go to transport details "CONTAINER" 2s 952ms
And Expand advice panel 246ms
And Edit advice in transport details 18s 857ms
And Fill arrival date field 2s 637ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 250ms
Then Check advice data in database after edition "CONTAINER" 100ms
After Hooks.deleteTransportAfterTest() 817ms
@deleteTransportAfterTest
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 570ms
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" 021ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 614ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 57s 246ms
And Go to "TRANSPORT_TABLE" 469ms
When Go to transport details "TRANSPORT_ORDER" 2s 871ms
And Expand advice panel 304ms
And Edit advice in transport details 18s 919ms
And Fill arrival date field 2s 628ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 253ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 109ms
After Hooks.deleteTransportAfterTest() 795ms