Project Number Date
ApolloFullRunnerReport 2021.AT1.54 09 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 18s 156ms 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" 1s 088ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 381ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 039ms
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 314ms
When Click button advice in transport table "CONTAINER" 093ms
And Set advice window in schedule 2s 552ms
And Fill advice form 16s 714ms
And Click advice save button and wait for advice form to disappear 30s 683ms
And Go to "TRANSPORT_TABLE" 177ms
And Go to transport details "CONTAINER" 2s 500ms
Then Check are advice values equals 4s 343ms
After Hooks.deleteTransportAfterTest() 110ms
After Hooks.cleanUserDetailsAfterTest() 288ms
@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 877ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 332ms
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 "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 374ms
When Click button advice in transport table "OWN_COLLECTION" 098ms
And Set advice window in schedule 2s 545ms
And Fill advice form 16s 771ms
And Click advice save button and wait for advice form to disappear 30s 748ms
And Go to "TRANSPORT_TABLE" 195ms
And Go to transport details "OWN_COLLECTION" 2s 439ms
Then Check are advice values equals 4s 309ms
After Hooks.deleteTransportAfterTest() 115ms
After Hooks.cleanUserDetailsAfterTest() 307ms
@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 857ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 316ms
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" 038ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 818ms
When Click button advice in transport table "TRANSPORT_ORDER" 091ms
And Set advice window in schedule 2s 563ms
And Fill advice form 16s 681ms
And Click advice save button and wait for advice form to disappear 30s 759ms
And Go to "TRANSPORT_TABLE" 222ms
And Go to transport details "TRANSPORT_ORDER" 2s 449ms
Then Check are advice values equals 4s 321ms
After Hooks.deleteTransportAfterTest() 086ms
After Hooks.cleanUserDetailsAfterTest() 259ms
@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 011ms
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 821ms
When Click button advice in transport table "TRANSPORT_ORDER" 081ms
And Set advice window in schedule 2s 533ms
And Fill advice form 16s 709ms
And Click advice save button and wait for advice form to disappear 30s 746ms
And Go to "TRANSPORT_TABLE" 222ms
And Go to transport details "TRANSPORT_ORDER" 2s 413ms
Then Check are advice values equals 4s 331ms
After Hooks.deleteTransportAfterTest() 117ms
After Hooks.cleanUserDetailsAfterTest() 400ms
@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) 000ms
Steps
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 874ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 252ms
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" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 900ms
When Click button advice in transport table "TRANSPORT_ORDER" 094ms
And Set advice window in schedule 30s 050ms
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.owmipW}, 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: b6cac0b1b19eeaa75fd4d23da779b781
*** 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() 079ms
After Hooks.cleanUserDetailsAfterTest() 257ms
@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 801ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 344ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 040ms
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 368ms
When Click button advice in transport table "OWN_COLLECTION" 094ms
And Set advice window in schedule 2s 556ms
And Fill advice form 16s 766ms
And Click advice save button and wait for advice form to disappear 30s 719ms
And Go to "TRANSPORT_TABLE" 143ms
Then Check advice data in SK API database "OWN_COLLECTION" 153ms
After Hooks.deleteTransportAfterTest() 103ms
After Hooks.cleanUserDetailsAfterTest() 289ms
@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 817ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 331ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 041ms
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 318ms
When Click button advice in transport table "CONTAINER" 089ms
And Set advice window in schedule 2s 568ms
And Fill advice form 16s 769ms
And Click advice save button and wait for advice form to disappear 30s 700ms
And Go to "TRANSPORT_TABLE" 183ms
Then Check advice data in SK API database "CONTAINER" 081ms
After Hooks.deleteTransportAfterTest() 121ms
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) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 791ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 372ms
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 1s 140ms
When Click button advice in transport table "TRANSPORT_ORDER" 098ms
And Set advice window in schedule 2s 565ms
And Fill advice form 16s 667ms
And Click advice save button and wait for advice form to disappear 30s 758ms
And Go to "TRANSPORT_TABLE" 238ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 039ms
After Hooks.deleteTransportAfterTest() 112ms
After Hooks.cleanUserDetailsAfterTest() 290ms
@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 691ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 445ms
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" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 811ms
When Click button advice in transport table "TRANSPORT_ORDER" 099ms
And Set advice window in schedule 2s 580ms
And Fill advice form 16s 768ms
And Click advice save button and wait for advice form to disappear 30s 737ms
And Go to "TRANSPORT_TABLE" 220ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 037ms
After Hooks.deleteTransportAfterTest() 094ms
After Hooks.cleanUserDetailsAfterTest() 354ms
@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" 1s 977ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 243ms
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 1s 147ms
When Click button advice in transport table "TRANSPORT_ORDER" 098ms
And Set advice window in schedule 2s 564ms
And Fill advice form 16s 640ms
And Click advice save button and wait for advice form to disappear 30s 744ms
And Go to "TRANSPORT_TABLE" 205ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 104ms
After Hooks.deleteTransportAfterTest() 135ms
After Hooks.cleanUserDetailsAfterTest() 249ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 807ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 041ms
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 "CONTAINER" created in transport table and set transport id 3s 317ms
When Click button advice in transport table "CONTAINER" 104ms
And Set advice window in schedule in the past 2s 559ms
And Fill advice form 16s 787ms
And Click advice save button to check error message 102ms
Then Check if possible advice alert is displayed 019ms
After Hooks.deleteTransportAfterTest() 079ms
@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 220ms
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 "EDIT_ADVICE" "super-admin-skz" 033ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 388ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 49s 999ms
And Go to "TRANSPORT_TABLE" 178ms
When Go to transport details "OWN_COLLECTION" 2s 452ms
And Expand advice panel 091ms
And Edit advice in transport details 16s 084ms
And Fill arrival date field 2s 295ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 095ms
Then Check advice data in database after edition "OWN_COLLECTION" 028ms
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) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 240ms
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 3s 306ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 50s 090ms
And Go to "TRANSPORT_TABLE" 186ms
When Go to transport details "CONTAINER" 2s 506ms
And Expand advice panel 100ms
And Edit advice in transport details 16s 142ms
And Fill arrival date field 2s 311ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 085ms
Then Check advice data in database after edition "CONTAINER" 029ms
After Hooks.deleteTransportAfterTest() 100ms
@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 232ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id 6s 171ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 50s 150ms
And Go to "TRANSPORT_TABLE" 199ms
When Go to transport details "TRANSPORT_ORDER" 2s 448ms
And Expand advice panel 098ms
And Edit advice in transport details 16s 111ms
And Fill arrival date field 2s 264ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 075ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 034ms
After Hooks.deleteTransportAfterTest() 124ms