Project Number Date
ApolloFullRunnerReport 2021.AT1.57 12 sie 2021, 05:48

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 19s 935ms 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 122ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 381ms
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 3s 310ms
When Click button advice in transport table "CONTAINER" 082ms
And Set advice window in schedule 2s 601ms
And Fill advice form 16s 726ms
And Click advice save button and wait for advice form to disappear 30s 741ms
And Go to "TRANSPORT_TABLE" 220ms
And Go to transport details "CONTAINER" 2s 507ms
Then Check are advice values equals 4s 344ms
After Hooks.deleteTransportAfterTest() 127ms
After Hooks.cleanUserDetailsAfterTest() 282ms
@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 937ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 345ms
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 384ms
When Click button advice in transport table "OWN_COLLECTION" 092ms
And Set advice window in schedule 2s 563ms
And Fill advice form 16s 775ms
And Click advice save button and wait for advice form to disappear 30s 705ms
And Go to "TRANSPORT_TABLE" 209ms
And Go to transport details "OWN_COLLECTION" 2s 477ms
Then Check are advice values equals 4s 324ms
After Hooks.deleteTransportAfterTest() 119ms
After Hooks.cleanUserDetailsAfterTest() 287ms
@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 918ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 344ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 046ms
And Add transport by SKApi in "MGW" assigned to "" 004ms
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 806ms
When Click button advice in transport table "TRANSPORT_ORDER" 072ms
And Set advice window in schedule 2s 554ms
And Fill advice form 16s 853ms
And Click advice save button and wait for advice form to disappear 30s 765ms
And Go to "TRANSPORT_TABLE" 205ms
And Go to transport details "TRANSPORT_ORDER" 2s 445ms
Then Check are advice values equals 4s 337ms
After Hooks.deleteTransportAfterTest() 114ms
After Hooks.cleanUserDetailsAfterTest() 289ms
@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 174ms
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" 036ms
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 3s 858ms
When Click button advice in transport table "TRANSPORT_ORDER" 097ms
And Set advice window in schedule 2s 589ms
And Fill advice form 16s 792ms
And Click advice save button and wait for advice form to disappear 30s 733ms
And Go to "TRANSPORT_TABLE" 214ms
And Go to transport details "TRANSPORT_ORDER" 2s 409ms
Then Check are advice values equals 4s 351ms
After Hooks.deleteTransportAfterTest() 119ms
After Hooks.cleanUserDetailsAfterTest() 371ms
@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 873ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 273ms
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" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 902ms
When Click button advice in transport table "TRANSPORT_ORDER" 085ms
And Set advice window in schedule 30s 066ms
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.kB5mLg}, 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: 1337ddc814c7369f7f040b306e3b9bab
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.GeneratedConstructorAccessor215.newInstance(Unknown Source)
	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() 058ms
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) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 892ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 358ms
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 379ms
When Click button advice in transport table "OWN_COLLECTION" 081ms
And Set advice window in schedule 2s 579ms
And Fill advice form 16s 739ms
And Click advice save button and wait for advice form to disappear 30s 712ms
And Go to "TRANSPORT_TABLE" 198ms
Then Check advice data in SK API database "OWN_COLLECTION" 138ms
After Hooks.deleteTransportAfterTest() 108ms
After Hooks.cleanUserDetailsAfterTest() 283ms
@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 869ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 323ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 360ms
When Click button advice in transport table "CONTAINER" 097ms
And Set advice window in schedule 2s 544ms
And Fill advice form 16s 709ms
And Click advice save button and wait for advice form to disappear 30s 682ms
And Go to "TRANSPORT_TABLE" 208ms
Then Check advice data in SK API database "CONTAINER" 094ms
After Hooks.deleteTransportAfterTest() 119ms
After Hooks.cleanUserDetailsAfterTest() 287ms
@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 827ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 328ms
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" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 814ms
When Click button advice in transport table "TRANSPORT_ORDER" 088ms
And Set advice window in schedule 2s 557ms
And Fill advice form 16s 803ms
And Click advice save button and wait for advice form to disappear 30s 786ms
And Go to "TRANSPORT_TABLE" 217ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 039ms
After Hooks.deleteTransportAfterTest() 089ms
After Hooks.cleanUserDetailsAfterTest() 284ms
@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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 731ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 449ms
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 1s 131ms
When Click button advice in transport table "TRANSPORT_ORDER" 099ms
And Set advice window in schedule 2s 594ms
And Fill advice form 16s 717ms
And Click advice save button and wait for advice form to disappear 30s 724ms
And Go to "TRANSPORT_TABLE" 252ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 035ms
After Hooks.deleteTransportAfterTest() 130ms
After Hooks.cleanUserDetailsAfterTest() 357ms
@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) 002ms
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 038ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 274ms
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" 034ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 934ms
When Click button advice in transport table "TRANSPORT_ORDER" 076ms
And Set advice window in schedule 2s 559ms
And Fill advice form 16s 839ms
And Click advice save button and wait for advice form to disappear 30s 719ms
And Go to "TRANSPORT_TABLE" 192ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms
After Hooks.deleteTransportAfterTest() 098ms
After Hooks.cleanUserDetailsAfterTest() 219ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 843ms
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 322ms
When Click button advice in transport table "CONTAINER" 090ms
And Set advice window in schedule in the past 2s 582ms
And Fill advice form 16s 793ms
And Click advice save button to check error message 085ms
Then Check if possible advice alert is displayed 022ms
After Hooks.deleteTransportAfterTest() 118ms
@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 224ms
And Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id 3s 365ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 50s 199ms
And Go to "TRANSPORT_TABLE" 193ms
When Go to transport details "OWN_COLLECTION" 2s 454ms
And Expand advice panel 085ms
And Edit advice in transport details 16s 089ms
And Fill arrival date field 2s 294ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 112ms
Then Check advice data in database after edition "OWN_COLLECTION" 029ms
After Hooks.deleteTransportAfterTest() 114ms
@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 260ms
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" 033ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 342ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 50s 234ms
And Go to "TRANSPORT_TABLE" 192ms
When Go to transport details "CONTAINER" 2s 475ms
And Expand advice panel 110ms
And Edit advice in transport details 16s 102ms
And Fill arrival date field 2s 292ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 071ms
Then Check advice data in database after edition "CONTAINER" 032ms
After Hooks.deleteTransportAfterTest() 108ms
@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 283ms
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 "EDIT_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1s 154ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 50s 169ms
And Go to "TRANSPORT_TABLE" 246ms
When Go to transport details "TRANSPORT_ORDER" 2s 489ms
And Expand advice panel 106ms
And Edit advice in transport details 16s 117ms
And Fill arrival date field 2s 268ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 128ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 029ms
After Hooks.deleteTransportAfterTest() 105ms