Project Number Date
ApolloFullRunnerReport apollo-test-2.109 07 sie 2021, 05:54

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 52s 196ms 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 513ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 383ms
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 6s 946ms
When Click button advice in transport table "CONTAINER" 206ms
And Set advice window in schedule 3s 306ms
And Fill advice form 20s 191ms
And Click advice save button and wait for advice form to disappear 33s 215ms
And Go to "TRANSPORT_TABLE" 473ms
And Go to transport details "CONTAINER" 2s 966ms
Then Check are advice values equals 4s 949ms
After Hooks.cleanUserDetailsAfterTest() 2s 298ms
After Hooks.deleteTransportAfterTest() 766ms
@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 489ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 386ms
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 123ms
When Click button advice in transport table "OWN_COLLECTION" 210ms
And Set advice window in schedule 3s 333ms
And Fill advice form 20s 337ms
And Click advice save button and wait for advice form to disappear 33s 304ms
And Go to "TRANSPORT_TABLE" 398ms
And Go to transport details "OWN_COLLECTION" 2s 835ms
Then Check are advice values equals 5s 001ms
After Hooks.cleanUserDetailsAfterTest() 2s 150ms
After Hooks.deleteTransportAfterTest() 802ms
@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 172ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 318ms
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 368ms
When Click button advice in transport table "TRANSPORT_ORDER" 193ms
And Set advice window in schedule 3s 299ms
And Fill advice form 20s 395ms
And Click advice save button and wait for advice form to disappear 33s 212ms
And Go to "TRANSPORT_TABLE" 460ms
And Go to transport details "TRANSPORT_ORDER" 2s 835ms
Then Check are advice values equals 4s 962ms
After Hooks.cleanUserDetailsAfterTest() 2s 271ms
After Hooks.deleteTransportAfterTest() 770ms
@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 292ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 452ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "" 015ms
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 837ms
When Click button advice in transport table "TRANSPORT_ORDER" 224ms
And Set advice window in schedule 3s 325ms
And Fill advice form 20s 417ms
And Click advice save button and wait for advice form to disappear 33s 340ms
And Go to "TRANSPORT_TABLE" 503ms
And Go to transport details "TRANSPORT_ORDER" 2s 849ms
Then Check are advice values equals 4s 985ms
After Hooks.cleanUserDetailsAfterTest() 2s 688ms
After Hooks.deleteTransportAfterTest() 797ms
@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 325ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 688ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 7s 542ms
When Click button advice in transport table "TRANSPORT_ORDER" 215ms
And Set advice window in schedule 30s 088ms
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=91.0.4472.164)
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=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.YieHRa}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.164, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 078af000bf697485a7dbc2c07806430a
*** 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:323)
	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.cleanUserDetailsAfterTest() 1s 701ms
After Hooks.deleteTransportAfterTest() 571ms
@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 437ms
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" 022ms
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 "OWN_COLLECTION" created in transport table and set transport id 7s 396ms
When Click button advice in transport table "OWN_COLLECTION" 212ms
And Set advice window in schedule 3s 360ms
And Fill advice form 20s 353ms
And Click advice save button and wait for advice form to disappear 33s 339ms
And Go to "TRANSPORT_TABLE" 459ms
Then Check advice data in SK API database "OWN_COLLECTION" 445ms
After Hooks.cleanUserDetailsAfterTest() 2s 130ms
After Hooks.deleteTransportAfterTest() 798ms
@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 309ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 340ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 024ms
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 "CONTAINER" created in transport table and set transport id 3s 927ms
When Click button advice in transport table "CONTAINER" 217ms
And Set advice window in schedule 3s 342ms
And Fill advice form 20s 367ms
And Click advice save button and wait for advice form to disappear 33s 183ms
And Go to "TRANSPORT_TABLE" 439ms
Then Check advice data in SK API database "CONTAINER" 235ms
After Hooks.cleanUserDetailsAfterTest() 2s 278ms
After Hooks.deleteTransportAfterTest() 926ms
@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 470ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 225ms
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" 014ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 434ms
When Click button advice in transport table "TRANSPORT_ORDER" 197ms
And Set advice window in schedule 3s 391ms
And Fill advice form 20s 394ms
And Click advice save button and wait for advice form to disappear 33s 331ms
And Go to "TRANSPORT_TABLE" 494ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 092ms
After Hooks.cleanUserDetailsAfterTest() 2s 156ms
After Hooks.deleteTransportAfterTest() 781ms
@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 181ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 436ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 024ms
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 "TRANSPORT_ORDER" created in transport table and set transport id 3s 874ms
When Click button advice in transport table "TRANSPORT_ORDER" 198ms
And Set advice window in schedule 3s 333ms
And Fill advice form 20s 137ms
And Click advice save button and wait for advice form to disappear 33s 340ms
And Go to "TRANSPORT_TABLE" 483ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 093ms
After Hooks.cleanUserDetailsAfterTest() 2s 992ms
After Hooks.deleteTransportAfterTest() 803ms
@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 606ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 868ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 030ms
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 535ms
When Click button advice in transport table "TRANSPORT_ORDER" 212ms
And Set advice window in schedule 3s 357ms
And Fill advice form 20s 253ms
And Click advice save button and wait for advice form to disappear 33s 814ms
And Go to "TRANSPORT_TABLE" 422ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 303ms
After Hooks.cleanUserDetailsAfterTest() 1s 654ms
After Hooks.deleteTransportAfterTest() 797ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 322ms
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" 018ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 925ms
When Click button advice in transport table "CONTAINER" 236ms
And Set advice window in schedule in the past 3s 335ms
And Fill advice form 20s 323ms
And Click advice save button to check error message 185ms
Then Check if possible advice alert is displayed 065ms
After Hooks.deleteTransportAfterTest() 577ms
@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 701ms
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 105ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 172ms
And Go to "TRANSPORT_TABLE" 473ms
When Go to transport details "OWN_COLLECTION" 2s 826ms
And Expand advice panel 294ms
And Edit advice in transport details 18s 729ms
And Fill arrival date field 2s 615ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 166ms
Then Check advice data in database after edition "OWN_COLLECTION" 108ms
After Hooks.deleteTransportAfterTest() 833ms
@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 522ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 020ms
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 "CONTAINER" created in transport table and set transport id 3s 975ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 325ms
And Go to "TRANSPORT_TABLE" 446ms
When Go to transport details "CONTAINER" 2s 844ms
And Expand advice panel 299ms
And Edit advice in transport details 18s 712ms
And Fill arrival date field 2s 601ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 259ms
Then Check advice data in database after edition "CONTAINER" 094ms
After Hooks.deleteTransportAfterTest() 825ms
@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 559ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 018ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 606ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 57s 179ms
And Go to "TRANSPORT_TABLE" 450ms
When Go to transport details "TRANSPORT_ORDER" 2s 823ms
And Expand advice panel 267ms
And Edit advice in transport details 18s 762ms
And Fill arrival date field 2s 599ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 237ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 098ms
After Hooks.deleteTransportAfterTest() 812ms