Project Number Date
ApolloFullRunnerReport 2021.AT1.64 17 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 21s 767ms 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 086ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 384ms
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 "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" 089ms
And Set advice window in schedule 2s 614ms
And Fill advice form 16s 809ms
And Click advice save button and wait for advice form to disappear 30s 709ms
And Go to "TRANSPORT_TABLE" 206ms
And Go to transport details "CONTAINER" 2s 524ms
Then Check are advice values equals 4s 334ms
After Hooks.deleteTransportAfterTest() 098ms
After Hooks.cleanUserDetailsAfterTest() 263ms
@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 950ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 331ms
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" 037ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 399ms
When Click button advice in transport table "OWN_COLLECTION" 094ms
And Set advice window in schedule 2s 573ms
And Fill advice form 16s 781ms
And Click advice save button and wait for advice form to disappear 30s 696ms
And Go to "TRANSPORT_TABLE" 173ms
And Go to transport details "OWN_COLLECTION" 2s 459ms
Then Check are advice values equals 4s 349ms
After Hooks.deleteTransportAfterTest() 113ms
After Hooks.cleanUserDetailsAfterTest() 295ms
@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 924ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 366ms
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 793ms
When Click button advice in transport table "TRANSPORT_ORDER" 082ms
And Set advice window in schedule 2s 578ms
And Fill advice form 16s 792ms
And Click advice save button and wait for advice form to disappear 30s 763ms
And Go to "TRANSPORT_TABLE" 203ms
And Go to transport details "TRANSPORT_ORDER" 2s 450ms
Then Check are advice values equals 4s 326ms
After Hooks.deleteTransportAfterTest() 095ms
After Hooks.cleanUserDetailsAfterTest() 274ms
@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 108ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 487ms
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 3s 832ms
When Click button advice in transport table "TRANSPORT_ORDER" 097ms
And Set advice window in schedule 2s 557ms
And Fill advice form 16s 709ms
And Click advice save button and wait for advice form to disappear 30s 678ms
And Go to "TRANSPORT_TABLE" 242ms
And Go to transport details "TRANSPORT_ORDER" 2s 449ms
Then Check are advice values equals 4s 317ms
After Hooks.deleteTransportAfterTest() 128ms
After Hooks.cleanUserDetailsAfterTest() 352ms
@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 917ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 262ms
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 904ms
When Click button advice in transport table "TRANSPORT_ORDER" 101ms
And Set advice window in schedule 30s 115ms
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.tQWkKe}, 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: 8750bd19a17fb9d97045e3531768dee5
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.GeneratedConstructorAccessor214.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:325)
	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() 081ms
After Hooks.cleanUserDetailsAfterTest() 222ms
@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 866ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 352ms
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" 033ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 394ms
When Click button advice in transport table "OWN_COLLECTION" 099ms
And Set advice window in schedule 2s 540ms
And Fill advice form 16s 699ms
And Click advice save button and wait for advice form to disappear 30s 695ms
And Go to "TRANSPORT_TABLE" 197ms
Then Check advice data in SK API database "OWN_COLLECTION" 129ms
After Hooks.deleteTransportAfterTest() 106ms
After Hooks.cleanUserDetailsAfterTest() 274ms
@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 960ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 329ms
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" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 327ms
When Click button advice in transport table "CONTAINER" 088ms
And Set advice window in schedule 2s 574ms
And Fill advice form 16s 771ms
And Click advice save button and wait for advice form to disappear 30s 725ms
And Go to "TRANSPORT_TABLE" 198ms
Then Check advice data in SK API database "CONTAINER" 087ms
After Hooks.deleteTransportAfterTest() 115ms
After Hooks.cleanUserDetailsAfterTest() 286ms
@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 891ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 357ms
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" 034ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 798ms
When Click button advice in transport table "TRANSPORT_ORDER" 092ms
And Set advice window in schedule 2s 585ms
And Fill advice form 16s 797ms
And Click advice save button and wait for advice form to disappear 30s 694ms
And Go to "TRANSPORT_TABLE" 217ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 036ms
After Hooks.deleteTransportAfterTest() 091ms
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) 000ms
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 820ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 503ms
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 1s 140ms
When Click button advice in transport table "TRANSPORT_ORDER" 094ms
And Set advice window in schedule 2s 585ms
And Fill advice form 16s 738ms
And Click advice save button and wait for advice form to disappear 30s 683ms
And Go to "TRANSPORT_TABLE" 246ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 035ms
After Hooks.deleteTransportAfterTest() 120ms
After Hooks.cleanUserDetailsAfterTest() 366ms
@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 038ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 258ms
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 2s 941ms
When Click button advice in transport table "TRANSPORT_ORDER" 096ms
And Set advice window in schedule 2s 568ms
And Fill advice form 16s 845ms
And Click advice save button and wait for advice form to disappear 30s 710ms
And Go to "TRANSPORT_TABLE" 199ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 092ms
After Hooks.deleteTransportAfterTest() 129ms
After Hooks.cleanUserDetailsAfterTest() 232ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 836ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 040ms
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 "CONTAINER" created in transport table and set transport id 3s 329ms
When Click button advice in transport table "CONTAINER" 093ms
And Set advice window in schedule in the past 2s 569ms
And Fill advice form 16s 806ms
And Click advice save button to check error message 086ms
Then Check if possible advice alert is displayed 021ms
After Hooks.deleteTransportAfterTest() 083ms
@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 253ms
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 369ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 50s 105ms
And Go to "TRANSPORT_TABLE" 191ms
When Go to transport details "OWN_COLLECTION" 2s 466ms
And Expand advice panel 092ms
And Edit advice in transport details 16s 057ms
And Fill arrival date field 2s 294ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 073ms
Then Check advice data in database after edition "OWN_COLLECTION" 025ms
After Hooks.deleteTransportAfterTest() 107ms
@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 290ms
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 "EDIT_ADVICE" "super-admin-skz" 033ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 328ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 50s 092ms
And Go to "TRANSPORT_TABLE" 188ms
When Go to transport details "CONTAINER" 2s 520ms
And Expand advice panel 091ms
And Edit advice in transport details 16s 094ms
And Fill arrival date field 2s 295ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 121ms
Then Check advice data in database after edition "CONTAINER" 038ms
After Hooks.deleteTransportAfterTest() 124ms
@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 242ms
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 3s 182ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 50s 131ms
And Go to "TRANSPORT_TABLE" 222ms
When Go to transport details "TRANSPORT_ORDER" 2s 478ms
And Expand advice panel 098ms
And Edit advice in transport details 16s 111ms
And Fill arrival date field 2s 296ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 109ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 038ms
After Hooks.deleteTransportAfterTest() 121ms