Project Number Date
ApolloFullRunnerReport apollo-test-2.123 18 sie 2021, 06:09

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 272ms 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 678ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 326ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 014ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 941ms
When Click button advice in transport table "CONTAINER" 217ms
And Set advice window in schedule 3s 346ms
And Fill advice form 20s 266ms
And Click advice save button and wait for advice form to disappear 33s 258ms
And Go to "TRANSPORT_TABLE" 481ms
And Go to transport details "CONTAINER" 2s 951ms
Then Check are advice values equals 4s 936ms
After Hooks.deleteTransportAfterTest() 798ms
After Hooks.cleanUserDetailsAfterTest() 2s 238ms
@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 454ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 294ms
And Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id 7s 122ms
When Click button advice in transport table "OWN_COLLECTION" 215ms
And Set advice window in schedule 3s 391ms
And Fill advice form 20s 353ms
And Click advice save button and wait for advice form to disappear 33s 266ms
And Go to "TRANSPORT_TABLE" 444ms
And Go to transport details "OWN_COLLECTION" 2s 966ms
Then Check are advice values equals 4s 969ms
After Hooks.deleteTransportAfterTest() 802ms
After Hooks.cleanUserDetailsAfterTest() 2s 059ms
@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 269ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 350ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 023ms
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 "TRANSPORT_ORDER" created in transport table and set transport id 4s 448ms
When Click button advice in transport table "TRANSPORT_ORDER" 212ms
And Set advice window in schedule 3s 360ms
And Fill advice form 20s 478ms
And Click advice save button and wait for advice form to disappear 33s 226ms
And Go to "TRANSPORT_TABLE" 484ms
And Go to transport details "TRANSPORT_ORDER" 2s 859ms
Then Check are advice values equals 5s 152ms
After Hooks.deleteTransportAfterTest() 832ms
After Hooks.cleanUserDetailsAfterTest() 2s 119ms
@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 677ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 494ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms
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 4s 707ms
When Click button advice in transport table "TRANSPORT_ORDER" 204ms
And Set advice window in schedule 3s 577ms
And Fill advice form 20s 247ms
And Click advice save button and wait for advice form to disappear 33s 937ms
And Go to "TRANSPORT_TABLE" 468ms
And Go to transport details "TRANSPORT_ORDER" 2s 798ms
Then Check are advice values equals 4s 991ms
After Hooks.deleteTransportAfterTest() 784ms
After Hooks.cleanUserDetailsAfterTest() 2s 704ms
@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 534ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 760ms
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" 018ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 562ms
When Click button advice in transport table "TRANSPORT_ORDER" 203ms
And Set advice window in schedule 30s 193ms
Error message 
org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-button-name='SHIFT_RIGHT_DAY']"}
  (Session info: headless chrome=92.0.4515.131)
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: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.Wp7ONc}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: e145d6961212f956fc0dcb269d0fc6f2
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java:325)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:91)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)
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() 567ms
After Hooks.cleanUserDetailsAfterTest() 1s 771ms
@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 449ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 328ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 022ms
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 "OWN_COLLECTION" created in transport table and set transport id 7s 142ms
When Click button advice in transport table "OWN_COLLECTION" 230ms
And Set advice window in schedule 3s 401ms
And Fill advice form 20s 497ms
And Click advice save button and wait for advice form to disappear 33s 186ms
And Go to "TRANSPORT_TABLE" 450ms
Then Check advice data in SK API database "OWN_COLLECTION" 409ms
After Hooks.deleteTransportAfterTest() 805ms
After Hooks.cleanUserDetailsAfterTest() 2s 113ms
@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 449ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 135ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 017ms
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 906ms
When Click button advice in transport table "CONTAINER" 210ms
And Set advice window in schedule 3s 378ms
And Fill advice form 20s 452ms
And Click advice save button and wait for advice form to disappear 33s 305ms
And Go to "TRANSPORT_TABLE" 451ms
Then Check advice data in SK API database "CONTAINER" 245ms
After Hooks.deleteTransportAfterTest() 849ms
After Hooks.cleanUserDetailsAfterTest() 2s 341ms
@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 650ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 353ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms
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 "TRANSPORT_ORDER" created in transport table and set transport id 4s 303ms
When Click button advice in transport table "TRANSPORT_ORDER" 232ms
And Set advice window in schedule 3s 347ms
And Fill advice form 20s 451ms
And Click advice save button and wait for advice form to disappear 33s 293ms
And Go to "TRANSPORT_TABLE" 424ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 085ms
After Hooks.deleteTransportAfterTest() 830ms
After Hooks.cleanUserDetailsAfterTest() 2s 073ms
@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 237ms
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" 020ms
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 3s 899ms
When Click button advice in transport table "TRANSPORT_ORDER" 220ms
And Set advice window in schedule 3s 400ms
And Fill advice form 20s 508ms
And Click advice save button and wait for advice form to disappear 18s 321ms
And Go to "TRANSPORT_TABLE" 504ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 096ms
After Hooks.deleteTransportAfterTest() 923ms
After Hooks.cleanUserDetailsAfterTest() 2s 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-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 8s 615ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 861ms
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" 017ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 535ms
When Click button advice in transport table "TRANSPORT_ORDER" 224ms
And Set advice window in schedule 3s 357ms
And Fill advice form 20s 453ms
And Click advice save button and wait for advice form to disappear 33s 802ms
And Go to "TRANSPORT_TABLE" 446ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 274ms
After Hooks.deleteTransportAfterTest() 853ms
After Hooks.cleanUserDetailsAfterTest() 1s 660ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 372ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 022ms
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 931ms
When Click button advice in transport table "CONTAINER" 232ms
And Set advice window in schedule in the past 3s 361ms
And Fill advice form 20s 496ms
And Click advice save button to check error message 182ms
Then Check if possible advice alert is displayed 070ms
After Hooks.deleteTransportAfterTest() 581ms
@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 734ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 024ms
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 114ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 312ms
And Go to "TRANSPORT_TABLE" 465ms
When Go to transport details "OWN_COLLECTION" 2s 905ms
And Expand advice panel 296ms
And Edit advice in transport details 18s 853ms
And Fill arrival date field 2s 659ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 208ms
Then Check advice data in database after edition "OWN_COLLECTION" 092ms
After Hooks.deleteTransportAfterTest() 803ms
@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 681ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 019ms
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 "CONTAINER" created in transport table and set transport id 6s 965ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 476ms
And Go to "TRANSPORT_TABLE" 467ms
When Go to transport details "CONTAINER" 2s 863ms
And Expand advice panel 294ms
And Edit advice in transport details 18s 922ms
And Fill arrival date field 2s 624ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 211ms
Then Check advice data in database after edition "CONTAINER" 099ms
After Hooks.deleteTransportAfterTest() 810ms
@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 801ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 018ms
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 "TRANSPORT_ORDER" created in transport table and set transport id 3s 664ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 57s 462ms
And Go to "TRANSPORT_TABLE" 496ms
When Go to transport details "TRANSPORT_ORDER" 2s 860ms
And Expand advice panel 320ms
And Edit advice in transport details 18s 919ms
And Fill arrival date field 2s 650ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 277ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 106ms
After Hooks.deleteTransportAfterTest() 831ms