Project Number Date
ApolloFullRunnerReport 2021.AT1.61 16 sie 2021, 05:45

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 26s 364ms 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 128ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 356ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 039ms
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 3s 333ms
When Click button advice in transport table "CONTAINER" 082ms
And Set advice window in schedule 2s 576ms
And Fill advice form 16s 780ms
And Click advice save button and wait for advice form to disappear 30s 678ms
And Go to "TRANSPORT_TABLE" 198ms
And Go to transport details "CONTAINER" 2s 510ms
Then Check are advice values equals 4s 330ms
After Hooks.deleteTransportAfterTest() 097ms
After Hooks.cleanUserDetailsAfterTest() 297ms
@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 948ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 375ms
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 408ms
When Click button advice in transport table "OWN_COLLECTION" 092ms
And Set advice window in schedule 2s 580ms
And Fill advice form 16s 784ms
And Click advice save button and wait for advice form to disappear 30s 725ms
And Go to "TRANSPORT_TABLE" 169ms
And Go to transport details "OWN_COLLECTION" 2s 451ms
Then Check are advice values equals 4s 349ms
After Hooks.deleteTransportAfterTest() 122ms
After Hooks.cleanUserDetailsAfterTest() 296ms
@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 947ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 379ms
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 "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 800ms
When Click button advice in transport table "TRANSPORT_ORDER" 086ms
And Set advice window in schedule 2s 569ms
And Fill advice form 16s 825ms
And Click advice save button and wait for advice form to disappear 30s 715ms
And Go to "TRANSPORT_TABLE" 209ms
And Go to transport details "TRANSPORT_ORDER" 2s 439ms
Then Check are advice values equals 4s 348ms
After Hooks.deleteTransportAfterTest() 119ms
After Hooks.cleanUserDetailsAfterTest() 297ms
@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) 002ms
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 318ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 491ms
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 2s 864ms
When Click button advice in transport table "TRANSPORT_ORDER" 086ms
And Set advice window in schedule 2s 545ms
And Fill advice form 16s 719ms
And Click advice save button and wait for advice form to disappear 30s 690ms
And Go to "TRANSPORT_TABLE" 266ms
And Go to transport details "TRANSPORT_ORDER" 2s 464ms
Then Check are advice values equals 4s 323ms
After Hooks.deleteTransportAfterTest() 127ms
After Hooks.cleanUserDetailsAfterTest() 359ms
@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 841ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 242ms
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" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 917ms
When Click button advice in transport table "TRANSPORT_ORDER" 089ms
And Set advice window in schedule 30s 085ms
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.kvqJxu}, 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: 4173b0ad7ec9fb2f65894ed44dba0448
*** 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() 099ms
After Hooks.cleanUserDetailsAfterTest() 223ms
@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 843ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 351ms
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" 039ms
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" 092ms
And Set advice window in schedule 2s 538ms
And Fill advice form 16s 830ms
And Click advice save button and wait for advice form to disappear 30s 684ms
And Go to "TRANSPORT_TABLE" 184ms
Then Check advice data in SK API database "OWN_COLLECTION" 164ms
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 "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 962ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 354ms
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 "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 340ms
When Click button advice in transport table "CONTAINER" 086ms
And Set advice window in schedule 2s 579ms
And Fill advice form 16s 740ms
And Click advice save button and wait for advice form to disappear 30s 719ms
And Go to "TRANSPORT_TABLE" 184ms
Then Check advice data in SK API database "CONTAINER" 089ms
After Hooks.deleteTransportAfterTest() 103ms
After Hooks.cleanUserDetailsAfterTest() 296ms
@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 955ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 358ms
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 791ms
When Click button advice in transport table "TRANSPORT_ORDER" 086ms
And Set advice window in schedule 2s 553ms
And Fill advice form 16s 698ms
And Click advice save button and wait for advice form to disappear 30s 715ms
And Go to "TRANSPORT_TABLE" 221ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 038ms
After Hooks.deleteTransportAfterTest() 099ms
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 810ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 483ms
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" 035ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 857ms
When Click button advice in transport table "TRANSPORT_ORDER" 108ms
And Set advice window in schedule 2s 557ms
And Fill advice form 16s 792ms
And Click advice save button and wait for advice form to disappear 30s 719ms
And Go to "TRANSPORT_TABLE" 251ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 032ms
After Hooks.deleteTransportAfterTest() 126ms
After Hooks.cleanUserDetailsAfterTest() 375ms
@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 105ms
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" 039ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 002ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 039ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 916ms
When Click button advice in transport table "TRANSPORT_ORDER" 086ms
And Set advice window in schedule 2s 570ms
And Fill advice form 16s 795ms
And Click advice save button and wait for advice form to disappear 30s 732ms
And Go to "TRANSPORT_TABLE" 179ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 084ms
After Hooks.deleteTransportAfterTest() 114ms
After Hooks.cleanUserDetailsAfterTest() 235ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 952ms
And Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id 3s 334ms
When Click button advice in transport table "CONTAINER" 098ms
And Set advice window in schedule in the past 2s 565ms
And Fill advice form 16s 881ms
And Click advice save button to check error message 090ms
Then Check if possible advice alert is displayed 020ms
After Hooks.deleteTransportAfterTest() 067ms
@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 280ms
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" 033ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 398ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 50s 169ms
And Go to "TRANSPORT_TABLE" 188ms
When Go to transport details "OWN_COLLECTION" 2s 461ms
And Expand advice panel 109ms
And Edit advice in transport details 16s 091ms
And Fill arrival date field 2s 291ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 099ms
Then Check advice data in database after edition "OWN_COLLECTION" 034ms
After Hooks.deleteTransportAfterTest() 115ms
@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 531ms
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" 033ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 333ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 50s 119ms
And Go to "TRANSPORT_TABLE" 215ms
When Go to transport details "CONTAINER" 2s 521ms
And Expand advice panel 109ms
And Edit advice in transport details 16s 093ms
And Fill arrival date field 2s 287ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 107ms
Then Check advice data in database after edition "CONTAINER" 033ms
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 260ms
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 3s 196ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 50s 082ms
And Go to "TRANSPORT_TABLE" 237ms
When Go to transport details "TRANSPORT_ORDER" 2s 495ms
And Expand advice panel 090ms
And Edit advice in transport details 16s 102ms
And Fill arrival date field 2s 284ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 071ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 034ms
After Hooks.deleteTransportAfterTest() 117ms