Project Number Date
ApolloFullRunnerReport 2021.AT1.52 07 sie 2021, 05:34

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 15m 21s 088ms Failed
Feature SK Api - Advice transport
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" 1s 134ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 380ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 315ms
When Click button advice in transport table "CONTAINER" 098ms
And Set advice window in schedule 2s 551ms
And Fill advice form 16s 724ms
And Click advice save button and wait for advice form to disappear 30s 740ms
And Go to "TRANSPORT_TABLE" 204ms
And Go to transport details "CONTAINER" 2s 530ms
Then Check are advice values equals 4s 337ms
After Hooks.deleteTransportAfterTest() 119ms
After Hooks.cleanUserDetailsAfterTest() 285ms
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) 002ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 933ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 342ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 367ms
When Click button advice in transport table "OWN_COLLECTION" 098ms
And Set advice window in schedule 2s 568ms
And Fill advice form 16s 722ms
And Click advice save button and wait for advice form to disappear 30s 715ms
And Go to "TRANSPORT_TABLE" 186ms
And Go to transport details "OWN_COLLECTION" 2s 452ms
Then Check are advice values equals 4s 345ms
After Hooks.deleteTransportAfterTest() 120ms
After Hooks.cleanUserDetailsAfterTest() 293ms
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" 1s 865ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 334ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 039ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 824ms
When Click button advice in transport table "TRANSPORT_ORDER" 090ms
And Set advice window in schedule 2s 546ms
And Fill advice form 16s 724ms
And Click advice save button and wait for advice form to disappear 30s 710ms
And Go to "TRANSPORT_TABLE" 199ms
And Go to transport details "TRANSPORT_ORDER" 2s 455ms
Then Check are advice values equals 4s 330ms
After Hooks.deleteTransportAfterTest() 109ms
After Hooks.cleanUserDetailsAfterTest() 281ms
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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 111ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 501ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 847ms
When Click button advice in transport table "TRANSPORT_ORDER" 101ms
And Set advice window in schedule 2s 545ms
And Fill advice form 16s 727ms
And Click advice save button and wait for advice form to disappear 30s 706ms
And Go to "TRANSPORT_TABLE" 245ms
And Go to transport details "TRANSPORT_ORDER" 2s 424ms
Then Check are advice values equals 4s 335ms
After Hooks.deleteTransportAfterTest() 122ms
After Hooks.cleanUserDetailsAfterTest() 377ms
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" 2s 076ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 265ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 888ms
When Click button advice in transport table "TRANSPORT_ORDER" 092ms
And Set advice window in schedule 30s 124ms
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', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-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-2/temp/buildTmp/.com.google.Chrome.ajBDmS}, 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: 38262c65af6a9a3dc4ba2a5ee69e6895
*** 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.deleteTransportAfterTest() 065ms
After Hooks.cleanUserDetailsAfterTest() 208ms
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" 1s 895ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 372ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 390ms
When Click button advice in transport table "OWN_COLLECTION" 084ms
And Set advice window in schedule 2s 555ms
And Fill advice form 16s 629ms
And Click advice save button and wait for advice form to disappear 30s 675ms
And Go to "TRANSPORT_TABLE" 263ms
Then Check advice data in SK API database "OWN_COLLECTION" 133ms
After Hooks.deleteTransportAfterTest() 105ms
After Hooks.cleanUserDetailsAfterTest() 279ms
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" 1s 879ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 334ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 004ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 329ms
When Click button advice in transport table "CONTAINER" 089ms
And Set advice window in schedule 2s 555ms
And Fill advice form 16s 798ms
And Click advice save button and wait for advice form to disappear 30s 724ms
And Go to "TRANSPORT_TABLE" 187ms
Then Check advice data in SK API database "CONTAINER" 086ms
After Hooks.deleteTransportAfterTest() 116ms
After Hooks.cleanUserDetailsAfterTest() 320ms
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" 1s 877ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 366ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 794ms
When Click button advice in transport table "TRANSPORT_ORDER" 092ms
And Set advice window in schedule 2s 574ms
And Fill advice form 16s 812ms
And Click advice save button and wait for advice form to disappear 30s 699ms
And Go to "TRANSPORT_TABLE" 233ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 032ms
After Hooks.deleteTransportAfterTest() 102ms
After Hooks.cleanUserDetailsAfterTest() 262ms
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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 756ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 437ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1s 143ms
When Click button advice in transport table "TRANSPORT_ORDER" 102ms
And Set advice window in schedule 2s 560ms
And Fill advice form 16s 695ms
And Click advice save button and wait for advice form to disappear 30s 723ms
And Go to "TRANSPORT_TABLE" 258ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 043ms
After Hooks.deleteTransportAfterTest() 102ms
After Hooks.cleanUserDetailsAfterTest() 361ms
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" 1s 991ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 263ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 916ms
When Click button advice in transport table "TRANSPORT_ORDER" 111ms
And Set advice window in schedule 2s 523ms
And Fill advice form 16s 810ms
And Click advice save button and wait for advice form to disappear 30s 762ms
And Go to "TRANSPORT_TABLE" 162ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 085ms
After Hooks.deleteTransportAfterTest() 113ms
After Hooks.cleanUserDetailsAfterTest() 220ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 833ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 303ms
When Click button advice in transport table "CONTAINER" 096ms
And Set advice window in schedule in the past 2s 560ms
And Fill advice form 16s 690ms
And Click advice save button to check error message 084ms
Then Check if possible advice alert is displayed 019ms
After Hooks.deleteTransportAfterTest() 059ms
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" 1s 217ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 039ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 033ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 393ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 50s 137ms
And Go to "TRANSPORT_TABLE" 174ms
When Go to transport details "OWN_COLLECTION" 2s 454ms
And Expand advice panel 099ms
And Edit advice in transport details 16s 116ms
And Fill arrival date field 2s 318ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 157ms
Then Check advice data in database after edition "OWN_COLLECTION" 034ms
After Hooks.deleteTransportAfterTest() 110ms
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" 1s 223ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 332ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 50s 197ms
And Go to "TRANSPORT_TABLE" 180ms
When Go to transport details "CONTAINER" 2s 449ms
And Expand advice panel 092ms
And Edit advice in transport details 16s 098ms
And Fill arrival date field 2s 271ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 098ms
Then Check advice data in database after edition "CONTAINER" 030ms
After Hooks.deleteTransportAfterTest() 099ms
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" 1s 226ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 043ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 153ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 50s 042ms
And Go to "TRANSPORT_TABLE" 228ms
When Go to transport details "TRANSPORT_ORDER" 2s 477ms
And Expand advice panel 098ms
And Edit advice in transport details 16s 102ms
And Fill arrival date field 2s 298ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 057ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 032ms
After Hooks.deleteTransportAfterTest() 107ms