Project Number Date
ApolloFullRunnerReport 2021.AT1.55 10 sie 2021, 05:37

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 25s 109ms 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" 1s 151ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 377ms
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" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 304ms
When Click button advice in transport table "CONTAINER" 089ms
And Set advice window in schedule 2s 558ms
And Fill advice form 16s 733ms
And Click advice save button and wait for advice form to disappear 30s 708ms
And Go to "TRANSPORT_TABLE" 178ms
And Go to transport details "CONTAINER" 2s 450ms
Then Check are advice values equals 4s 328ms
After Hooks.deleteTransportAfterTest() 136ms
After Hooks.cleanUserDetailsAfterTest() 294ms
@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" 1s 897ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 329ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 039ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 035ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 370ms
When Click button advice in transport table "OWN_COLLECTION" 086ms
And Set advice window in schedule 2s 564ms
And Fill advice form 16s 742ms
And Click advice save button and wait for advice form to disappear 30s 709ms
And Go to "TRANSPORT_TABLE" 193ms
And Go to transport details "OWN_COLLECTION" 2s 458ms
Then Check are advice values equals 4s 332ms
After Hooks.deleteTransportAfterTest() 138ms
After Hooks.cleanUserDetailsAfterTest() 321ms
@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" 1s 827ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 335ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
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 815ms
When Click button advice in transport table "TRANSPORT_ORDER" 094ms
And Set advice window in schedule 2s 570ms
And Fill advice form 16s 735ms
And Click advice save button and wait for advice form to disappear 30s 732ms
And Go to "TRANSPORT_TABLE" 217ms
And Go to transport details "TRANSPORT_ORDER" 2s 421ms
Then Check are advice values equals 4s 345ms
After Hooks.deleteTransportAfterTest() 107ms
After Hooks.cleanUserDetailsAfterTest() 273ms
@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" 2s 115ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 484ms
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" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 863ms
When Click button advice in transport table "TRANSPORT_ORDER" 089ms
And Set advice window in schedule 2s 515ms
And Fill advice form 16s 693ms
And Click advice save button and wait for advice form to disappear 30s 696ms
And Go to "TRANSPORT_TABLE" 222ms
And Go to transport details "TRANSPORT_ORDER" 2s 452ms
Then Check are advice values equals 4s 328ms
After Hooks.deleteTransportAfterTest() 118ms
After Hooks.cleanUserDetailsAfterTest() 366ms
@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" 1s 860ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 259ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 002ms
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 807ms
When Click button advice in transport table "TRANSPORT_ORDER" 097ms
And Set advice window in schedule 30s 094ms
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', 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.kDektr}, 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: 219761719aa29ec1339b994900a3bd67
*** 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() 070ms
After Hooks.cleanUserDetailsAfterTest() 240ms
@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" 1s 827ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 363ms
And Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id 3s 358ms
When Click button advice in transport table "OWN_COLLECTION" 099ms
And Set advice window in schedule 2s 544ms
And Fill advice form 16s 757ms
And Click advice save button and wait for advice form to disappear 30s 707ms
And Go to "TRANSPORT_TABLE" 182ms
Then Check advice data in SK API database "OWN_COLLECTION" 146ms
After Hooks.deleteTransportAfterTest() 110ms
After Hooks.cleanUserDetailsAfterTest() 279ms
@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" 1s 877ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 328ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "" 005ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 337ms
When Click button advice in transport table "CONTAINER" 101ms
And Set advice window in schedule 2s 571ms
And Fill advice form 16s 760ms
And Click advice save button and wait for advice form to disappear 30s 737ms
And Go to "TRANSPORT_TABLE" 190ms
Then Check advice data in SK API database "CONTAINER" 091ms
After Hooks.deleteTransportAfterTest() 105ms
After Hooks.cleanUserDetailsAfterTest() 292ms
@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" 1s 903ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 324ms
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" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 822ms
When Click button advice in transport table "TRANSPORT_ORDER" 090ms
And Set advice window in schedule 2s 545ms
And Fill advice form 16s 761ms
And Click advice save button and wait for advice form to disappear 30s 728ms
And Go to "TRANSPORT_TABLE" 229ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 050ms
After Hooks.deleteTransportAfterTest() 103ms
After Hooks.cleanUserDetailsAfterTest() 276ms
@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" 1s 728ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 459ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 035ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
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 823ms
When Click button advice in transport table "TRANSPORT_ORDER" 092ms
And Set advice window in schedule 2s 532ms
And Fill advice form 16s 758ms
And Click advice save button and wait for advice form to disappear 30s 683ms
And Go to "TRANSPORT_TABLE" 211ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 039ms
After Hooks.deleteTransportAfterTest() 103ms
After Hooks.cleanUserDetailsAfterTest() 370ms
@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" 2s 029ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 295ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms
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 862ms
When Click button advice in transport table "TRANSPORT_ORDER" 093ms
And Set advice window in schedule 2s 530ms
And Fill advice form 16s 688ms
And Click advice save button and wait for advice form to disappear 30s 688ms
And Go to "TRANSPORT_TABLE" 169ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms
After Hooks.deleteTransportAfterTest() 106ms
After Hooks.cleanUserDetailsAfterTest() 231ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 801ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 040ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 037ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 332ms
When Click button advice in transport table "CONTAINER" 102ms
And Set advice window in schedule in the past 2s 589ms
And Fill advice form 16s 789ms
And Click advice save button to check error message 101ms
Then Check if possible advice alert is displayed 020ms
After Hooks.deleteTransportAfterTest() 080ms
@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" 1s 232ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 037ms
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 392ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 50s 098ms
And Go to "TRANSPORT_TABLE" 191ms
When Go to transport details "OWN_COLLECTION" 2s 424ms
And Expand advice panel 096ms
And Edit advice in transport details 16s 070ms
And Fill arrival date field 2s 282ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 136ms
Then Check advice data in database after edition "OWN_COLLECTION" 034ms
After Hooks.deleteTransportAfterTest() 117ms
@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" 1s 224ms
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 "EDIT_ADVICE" "super-admin-skz" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 330ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 50s 181ms
And Go to "TRANSPORT_TABLE" 197ms
When Go to transport details "CONTAINER" 2s 456ms
And Expand advice panel 107ms
And Edit advice in transport details 16s 062ms
And Fill arrival date field 2s 276ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 116ms
Then Check advice data in database after edition "CONTAINER" 029ms
After Hooks.deleteTransportAfterTest() 101ms
@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" 1s 230ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "" 004ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 042ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 146ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 50s 199ms
And Go to "TRANSPORT_TABLE" 244ms
When Go to transport details "TRANSPORT_ORDER" 2s 449ms
And Expand advice panel 081ms
And Edit advice in transport details 16s 117ms
And Fill arrival date field 2s 258ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 136ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 033ms
After Hooks.deleteTransportAfterTest() 120ms