Project Number Date
ApolloFullRunnerReport apollo-test-2.98 29 lip 2021, 06:08

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 6s 409ms 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) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 509ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 364ms
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 964ms
When Click button advice in transport table "CONTAINER" 210ms
And Set advice window in schedule 3s 326ms
And Fill advice form 17s 880ms
And Click advice save button and wait for advice form to disappear 33s 349ms
And Go to "TRANSPORT_TABLE" 431ms
And Go to transport details "CONTAINER" 2s 927ms
Then Check are advice values equals 2s 895ms
After Hooks.deleteTransportAfterTest() 834ms
After Hooks.cleanUserDetailsAfterTest() 2s 195ms
@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" 7s 860ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 399ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 022ms
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 "OWN_COLLECTION" created in transport table and set transport id 4s 126ms
When Click button advice in transport table "OWN_COLLECTION" 223ms
And Set advice window in schedule 3s 364ms
And Fill advice form 18s 059ms
And Click advice save button and wait for advice form to disappear 33s 262ms
And Go to "TRANSPORT_TABLE" 446ms
And Go to transport details "OWN_COLLECTION" 2s 893ms
Then Check are advice values equals 2s 930ms
After Hooks.deleteTransportAfterTest() 814ms
After Hooks.cleanUserDetailsAfterTest() 2s 086ms
@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 594ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 405ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
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 234ms
When Click button advice in transport table "TRANSPORT_ORDER" 216ms
And Set advice window in schedule 3s 356ms
And Fill advice form 17s 868ms
And Click advice save button and wait for advice form to disappear 33s 386ms
And Go to "TRANSPORT_TABLE" 467ms
And Go to transport details "TRANSPORT_ORDER" 2s 899ms
Then Check are advice values equals 2s 930ms
After Hooks.deleteTransportAfterTest() 864ms
After Hooks.cleanUserDetailsAfterTest() 2s 345ms
@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 835ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 375ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
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 3s 910ms
When Click button advice in transport table "TRANSPORT_ORDER" 201ms
And Set advice window in schedule 3s 308ms
And Fill advice form 17s 963ms
And Click advice save button and wait for advice form to disappear 33s 791ms
And Go to "TRANSPORT_TABLE" 507ms
And Go to transport details "TRANSPORT_ORDER" 2s 832ms
Then Check are advice values equals 2s 988ms
After Hooks.deleteTransportAfterTest() 815ms
After Hooks.cleanUserDetailsAfterTest() 2s 693ms
@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 546ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 734ms
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" 016ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 486ms
When Click button advice in transport table "TRANSPORT_ORDER" 204ms
And Set advice window in schedule 30s 631ms
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: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() 566ms
After Hooks.cleanUserDetailsAfterTest() 1s 801ms
@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 757ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 399ms
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" 018ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 451ms
When Click button advice in transport table "OWN_COLLECTION" 209ms
And Set advice window in schedule 3s 373ms
And Fill advice form 17s 923ms
And Click advice save button and wait for advice form to disappear 33s 255ms
And Go to "TRANSPORT_TABLE" 415ms
Then Check advice data in SK API database "OWN_COLLECTION" 406ms
After Hooks.deleteTransportAfterTest() 854ms
After Hooks.cleanUserDetailsAfterTest() 2s 095ms
@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 490ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 425ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "" 017ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 013ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 960ms
When Click button advice in transport table "CONTAINER" 229ms
And Set advice window in schedule 3s 316ms
And Fill advice form 17s 980ms
And Click advice save button and wait for advice form to disappear 33s 333ms
And Go to "TRANSPORT_TABLE" 425ms
Then Check advice data in SK API database "CONTAINER" 196ms
After Hooks.deleteTransportAfterTest() 859ms
After Hooks.cleanUserDetailsAfterTest() 2s 264ms
@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 802ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 428ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 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 183ms
When Click button advice in transport table "TRANSPORT_ORDER" 236ms
And Set advice window in schedule 3s 324ms
And Fill advice form 17s 990ms
And Click advice save button and wait for advice form to disappear 33s 277ms
And Go to "TRANSPORT_TABLE" 443ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 082ms
After Hooks.deleteTransportAfterTest() 949ms
After Hooks.cleanUserDetailsAfterTest() 2s 131ms
@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 594ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 465ms
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" 018ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 922ms
When Click button advice in transport table "TRANSPORT_ORDER" 226ms
And Set advice window in schedule 3s 359ms
And Fill advice form 17s 882ms
And Click advice save button and wait for advice form to disappear 33s 269ms
And Go to "TRANSPORT_TABLE" 480ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 091ms
After Hooks.deleteTransportAfterTest() 965ms
After Hooks.cleanUserDetailsAfterTest() 3s
@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 869ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 869ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 023ms
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 4s 514ms
When Click button advice in transport table "TRANSPORT_ORDER" 225ms
And Set advice window in schedule 3s 392ms
And Fill advice form 17s 949ms
And Click advice save button and wait for advice form to disappear 33s 884ms
And Go to "TRANSPORT_TABLE" 440ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 280ms
After Hooks.deleteTransportAfterTest() 911ms
After Hooks.cleanUserDetailsAfterTest() 1s 638ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 683ms
And Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id 3s 905ms
When Click button advice in transport table "CONTAINER" 230ms
And Set advice window in schedule in the past 3s 308ms
And Fill advice form 18s 008ms
And Click advice save button to check error message 196ms
Then Check if possible advice alert is displayed 067ms
After Hooks.deleteTransportAfterTest() 602ms
@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 677ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 021ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 079ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 54s 769ms
And Go to "TRANSPORT_TABLE" 433ms
When Go to transport details "OWN_COLLECTION" 2s 778ms
And Expand advice panel 280ms
And Edit advice in transport details 16s 612ms
And Fill arrival date field 2s 672ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 284ms
Then Check advice data in database after edition "OWN_COLLECTION" 111ms
After Hooks.deleteTransportAfterTest() 842ms
@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 642ms
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" 016ms
And Check is transport "CONTAINER" created in transport table and set transport id 4s 073ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 54s 982ms
And Go to "TRANSPORT_TABLE" 396ms
When Go to transport details "CONTAINER" 2s 901ms
And Expand advice panel 308ms
And Edit advice in transport details 16s 490ms
And Fill arrival date field 2s 608ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 249ms
Then Check advice data in database after edition "CONTAINER" 102ms
After Hooks.deleteTransportAfterTest() 791ms
@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) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 602ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id 3s 619ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 55s 163ms
And Go to "TRANSPORT_TABLE" 445ms
When Go to transport details "TRANSPORT_ORDER" 2s 891ms
And Expand advice panel 298ms
And Edit advice in transport details 16s 561ms
And Fill arrival date field 2s 640ms
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() 802ms