Project Number Date
ApolloFullRunnerReport apollo-test-2.111 09 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 18m 56s 166ms 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" 2s 574ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 378ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 915ms
When Click button advice in transport table "CONTAINER" 204ms
And Set advice window in schedule 3s 305ms
And Fill advice form 20s 214ms
And Click advice save button and wait for advice form to disappear 33s 229ms
And Go to "TRANSPORT_TABLE" 469ms
And Go to transport details "CONTAINER" 2s 898ms
Then Check are advice values equals 5s 002ms
After Hooks.deleteTransportAfterTest() 789ms
After Hooks.cleanUserDetailsAfterTest() 2s 383ms
@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" 7s 640ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 367ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 017ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 014ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 095ms
When Click button advice in transport table "OWN_COLLECTION" 221ms
And Set advice window in schedule 3s 350ms
And Fill advice form 20s 378ms
And Click advice save button and wait for advice form to disappear 33s 303ms
And Go to "TRANSPORT_TABLE" 471ms
And Go to transport details "OWN_COLLECTION" 2s 893ms
Then Check are advice values equals 5s
After Hooks.deleteTransportAfterTest() 775ms
After Hooks.cleanUserDetailsAfterTest() 2s 211ms
@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" 7s 474ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 163ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 018ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 475ms
When Click button advice in transport table "TRANSPORT_ORDER" 208ms
And Set advice window in schedule 3s 423ms
And Fill advice form 20s 292ms
And Click advice save button and wait for advice form to disappear 33s 291ms
And Go to "TRANSPORT_TABLE" 503ms
And Go to transport details "TRANSPORT_ORDER" 2s 863ms
Then Check are advice values equals 5s 102ms
After Hooks.deleteTransportAfterTest() 698ms
After Hooks.cleanUserDetailsAfterTest() 2s 096ms
@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" 8s 701ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 384ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 018ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 019ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 921ms
When Click button advice in transport table "TRANSPORT_ORDER" 217ms
And Set advice window in schedule 3s 381ms
And Fill advice form 20s 353ms
And Click advice save button and wait for advice form to disappear 33s 891ms
And Go to "TRANSPORT_TABLE" 419ms
And Go to transport details "TRANSPORT_ORDER" 2s 857ms
Then Check are advice values equals 4s 957ms
After Hooks.deleteTransportAfterTest() 810ms
After Hooks.cleanUserDetailsAfterTest() 2s 731ms
@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" 7s 525ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 708ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 020ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 015ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 545ms
When Click button advice in transport table "TRANSPORT_ORDER" 225ms
And Set advice window in schedule 30s 150ms
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=91.0.4472.164)
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-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.AUHjQE}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.164, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: b80da82a8a4ffcf080d1071ff95c2641
*** 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() 569ms
After Hooks.cleanUserDetailsAfterTest() 1s 775ms
@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" 7s 481ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 367ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 203ms
When Click button advice in transport table "OWN_COLLECTION" 216ms
And Set advice window in schedule 3s 353ms
And Fill advice form 20s 418ms
And Click advice save button and wait for advice form to disappear 33s 371ms
And Go to "TRANSPORT_TABLE" 447ms
Then Check advice data in SK API database "OWN_COLLECTION" 436ms
After Hooks.deleteTransportAfterTest() 814ms
After Hooks.cleanUserDetailsAfterTest() 2s 104ms
@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" 7s 515ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 608ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 018ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 904ms
When Click button advice in transport table "CONTAINER" 221ms
And Set advice window in schedule 3s 381ms
And Fill advice form 20s 305ms
And Click advice save button and wait for advice form to disappear 33s 350ms
And Go to "TRANSPORT_TABLE" 449ms
Then Check advice data in SK API database "CONTAINER" 191ms
After Hooks.deleteTransportAfterTest() 832ms
After Hooks.cleanUserDetailsAfterTest() 2s 384ms
@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" 7s 765ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 453ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 194ms
When Click button advice in transport table "TRANSPORT_ORDER" 210ms
And Set advice window in schedule 3s 298ms
And Fill advice form 20s 165ms
And Click advice save button and wait for advice form to disappear 33s 343ms
And Go to "TRANSPORT_TABLE" 471ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 092ms
After Hooks.deleteTransportAfterTest() 850ms
After Hooks.cleanUserDetailsAfterTest() 2s 097ms
@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" 6s 511ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 665ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 750ms
When Click button advice in transport table "TRANSPORT_ORDER" 223ms
And Set advice window in schedule 3s 556ms
And Fill advice form 20s 213ms
And Click advice save button and wait for advice form to disappear 33s 260ms
And Go to "TRANSPORT_TABLE" 473ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 090ms
After Hooks.deleteTransportAfterTest() 909ms
After Hooks.cleanUserDetailsAfterTest() 2s 883ms
@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" 8s 751ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 923ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 021ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 612ms
When Click button advice in transport table "TRANSPORT_ORDER" 264ms
And Set advice window in schedule 3s 365ms
And Fill advice form 20s 260ms
And Click advice save button and wait for advice form to disappear 33s 785ms
And Go to "TRANSPORT_TABLE" 469ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 272ms
After Hooks.deleteTransportAfterTest() 839ms
After Hooks.cleanUserDetailsAfterTest() 1s 705ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 513ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 018ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 908ms
When Click button advice in transport table "CONTAINER" 236ms
And Set advice window in schedule in the past 3s 265ms
And Fill advice form 20s 209ms
And Click advice save button to check error message 185ms
Then Check if possible advice alert is displayed 073ms
After Hooks.deleteTransportAfterTest() 658ms
@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" 2s 639ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 030ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 017ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 087ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 156ms
And Go to "TRANSPORT_TABLE" 446ms
When Go to transport details "OWN_COLLECTION" 2s 913ms
And Expand advice panel 308ms
And Edit advice in transport details 18s 689ms
And Fill arrival date field 2s 603ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 221ms
Then Check advice data in database after edition "OWN_COLLECTION" 101ms
After Hooks.deleteTransportAfterTest() 846ms
@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" 2s 587ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 023ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 016ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 922ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 167ms
And Go to "TRANSPORT_TABLE" 456ms
When Go to transport details "CONTAINER" 2s 830ms
And Expand advice panel 295ms
And Edit advice in transport details 18s 817ms
And Fill arrival date field 2s 648ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 242ms
Then Check advice data in database after edition "CONTAINER" 107ms
After Hooks.deleteTransportAfterTest() 833ms
@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" 2s 636ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 017ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 632ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 57s 364ms
And Go to "TRANSPORT_TABLE" 475ms
When Go to transport details "TRANSPORT_ORDER" 2s 840ms
And Expand advice panel 288ms
And Edit advice in transport details 18s 877ms
And Fill arrival date field 2s 589ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 253ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 098ms
After Hooks.deleteTransportAfterTest() 830ms