Project Number Date
ApolloFullRunnerReport 2021.AT1.59 14 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 24s 849ms 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 130ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 404ms
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" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 328ms
When Click button advice in transport table "CONTAINER" 083ms
And Set advice window in schedule 2s 627ms
And Fill advice form 16s 828ms
And Click advice save button and wait for advice form to disappear 30s 727ms
And Go to "TRANSPORT_TABLE" 187ms
And Go to transport details "CONTAINER" 2s 503ms
Then Check are advice values equals 4s 337ms
After Hooks.deleteTransportAfterTest() 128ms
After Hooks.cleanUserDetailsAfterTest() 315ms
@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 935ms
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" 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 "OWN_COLLECTION" created in transport table and set transport id 6s 389ms
When Click button advice in transport table "OWN_COLLECTION" 080ms
And Set advice window in schedule 2s 553ms
And Fill advice form 16s 784ms
And Click advice save button and wait for advice form to disappear 30s 775ms
And Go to "TRANSPORT_TABLE" 187ms
And Go to transport details "OWN_COLLECTION" 2s 434ms
Then Check are advice values equals 4s 353ms
After Hooks.deleteTransportAfterTest() 114ms
After Hooks.cleanUserDetailsAfterTest() 309ms
@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 945ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 333ms
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 828ms
When Click button advice in transport table "TRANSPORT_ORDER" 083ms
And Set advice window in schedule 2s 589ms
And Fill advice form 16s 821ms
And Click advice save button and wait for advice form to disappear 30s 722ms
And Go to "TRANSPORT_TABLE" 235ms
And Go to transport details "TRANSPORT_ORDER" 2s 431ms
Then Check are advice values equals 4s 342ms
After Hooks.deleteTransportAfterTest() 109ms
After Hooks.cleanUserDetailsAfterTest() 267ms
@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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 156ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 482ms
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 "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 834ms
When Click button advice in transport table "TRANSPORT_ORDER" 088ms
And Set advice window in schedule 2s 550ms
And Fill advice form 16s 832ms
And Click advice save button and wait for advice form to disappear 30s 708ms
And Go to "TRANSPORT_TABLE" 215ms
And Go to transport details "TRANSPORT_ORDER" 2s 438ms
Then Check are advice values equals 4s 328ms
After Hooks.deleteTransportAfterTest() 113ms
After Hooks.cleanUserDetailsAfterTest() 368ms
@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) 002ms
Steps
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 762ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 276ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 040ms
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 3s 816ms
When Click button advice in transport table "TRANSPORT_ORDER" 073ms
And Set advice window in schedule 30s 043ms
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.MMqHmq}, 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: 50ff9f4d299490201cb806b899fcc9ff
*** 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() 063ms
After Hooks.cleanUserDetailsAfterTest() 197ms
@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 871ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 353ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 036ms
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 "OWN_COLLECTION" created in transport table and set transport id 3s 404ms
When Click button advice in transport table "OWN_COLLECTION" 094ms
And Set advice window in schedule 2s 583ms
And Fill advice form 16s 709ms
And Click advice save button and wait for advice form to disappear 30s 673ms
And Go to "TRANSPORT_TABLE" 203ms
Then Check advice data in SK API database "OWN_COLLECTION" 145ms
After Hooks.deleteTransportAfterTest() 102ms
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) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 844ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 286ms
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" 033ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 343ms
When Click button advice in transport table "CONTAINER" 087ms
And Set advice window in schedule 2s 552ms
And Fill advice form 16s 643ms
And Click advice save button and wait for advice form to disappear 30s 677ms
And Go to "TRANSPORT_TABLE" 213ms
Then Check advice data in SK API database "CONTAINER" 085ms
After Hooks.deleteTransportAfterTest() 108ms
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) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 935ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 347ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 043ms
And Add transport by SKApi in "MGW" assigned to "" 004ms
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" 081ms
And Set advice window in schedule 2s 564ms
And Fill advice form 16s 740ms
And Click advice save button and wait for advice form to disappear 30s 752ms
And Go to "TRANSPORT_TABLE" 222ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 032ms
After Hooks.deleteTransportAfterTest() 092ms
After Hooks.cleanUserDetailsAfterTest() 264ms
@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 767ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 463ms
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 138ms
When Click button advice in transport table "TRANSPORT_ORDER" 083ms
And Set advice window in schedule 2s 560ms
And Fill advice form 16s 714ms
And Click advice save button and wait for advice form to disappear 30s 695ms
And Go to "TRANSPORT_TABLE" 235ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 041ms
After Hooks.deleteTransportAfterTest() 132ms
After Hooks.cleanUserDetailsAfterTest() 399ms
@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 035ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 277ms
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 2s 880ms
When Click button advice in transport table "TRANSPORT_ORDER" 100ms
And Set advice window in schedule 2s 619ms
And Fill advice form 16s 716ms
And Click advice save button and wait for advice form to disappear 30s 691ms
And Go to "TRANSPORT_TABLE" 184ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 107ms
After Hooks.deleteTransportAfterTest() 125ms
After Hooks.cleanUserDetailsAfterTest() 238ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 815ms
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" 036ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 358ms
When Click button advice in transport table "CONTAINER" 107ms
And Set advice window in schedule in the past 2s 567ms
And Fill advice form 16s 829ms
And Click advice save button to check error message 096ms
Then Check if possible advice alert is displayed 018ms
After Hooks.deleteTransportAfterTest() 068ms
@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 269ms
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 "EDIT_ADVICE" "super-admin-skz" 033ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 378ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 50s 206ms
And Go to "TRANSPORT_TABLE" 213ms
When Go to transport details "OWN_COLLECTION" 2s 471ms
And Expand advice panel 103ms
And Edit advice in transport details 16s 097ms
And Fill arrival date field 2s 291ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 100ms
Then Check advice data in database after edition "OWN_COLLECTION" 032ms
After Hooks.deleteTransportAfterTest() 138ms
@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 303ms
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 327ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 50s 269ms
And Go to "TRANSPORT_TABLE" 180ms
When Go to transport details "CONTAINER" 2s 505ms
And Expand advice panel 101ms
And Edit advice in transport details 16s 135ms
And Fill arrival date field 2s 294ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 126ms
Then Check advice data in database after edition "CONTAINER" 033ms
After Hooks.deleteTransportAfterTest() 103ms
@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 249ms
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 "EDIT_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 209ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 50s 262ms
And Go to "TRANSPORT_TABLE" 218ms
When Go to transport details "TRANSPORT_ORDER" 2s 441ms
And Expand advice panel 105ms
And Edit advice in transport details 16s 093ms
And Fill arrival date field 2s 280ms
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" 035ms
After Hooks.deleteTransportAfterTest() 137ms