Project Number Date
ApolloFullRunnerReport apollo-test-2.118 14 sie 2021, 06:07

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 41s 527ms 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 668ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 406ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
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 930ms
When Click button advice in transport table "CONTAINER" 267ms
And Set advice window in schedule 3s 450ms
And Fill advice form 20s 383ms
And Click advice save button and wait for advice form to disappear 33s 249ms
And Go to "TRANSPORT_TABLE" 478ms
And Go to transport details "CONTAINER" 2s 921ms
Then Check are advice values equals 5s 022ms
After Hooks.deleteTransportAfterTest() 810ms
After Hooks.cleanUserDetailsAfterTest() 2s 260ms
@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 655ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 284ms
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" 017ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 163ms
When Click button advice in transport table "OWN_COLLECTION" 243ms
And Set advice window in schedule 3s 354ms
And Fill advice form 20s 377ms
And Click advice save button and wait for advice form to disappear 33s 261ms
And Go to "TRANSPORT_TABLE" 469ms
And Go to transport details "OWN_COLLECTION" 2s 850ms
Then Check are advice values equals 5s 047ms
After Hooks.deleteTransportAfterTest() 804ms
After Hooks.cleanUserDetailsAfterTest() 2s 164ms
@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 508ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 350ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 035ms
And Add transport by SKApi in "MGW" assigned to "" 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 321ms
When Click button advice in transport table "TRANSPORT_ORDER" 214ms
And Set advice window in schedule 3s 400ms
And Fill advice form 20s 579ms
And Click advice save button and wait for advice form to disappear 33s 263ms
And Go to "TRANSPORT_TABLE" 470ms
And Go to transport details "TRANSPORT_ORDER" 2s 874ms
Then Check are advice values equals 4s 974ms
After Hooks.deleteTransportAfterTest() 844ms
After Hooks.cleanUserDetailsAfterTest() 2s 370ms
@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" 8s 617ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 306ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 027ms
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 069ms
When Click button advice in transport table "TRANSPORT_ORDER" 229ms
And Set advice window in schedule 3s 378ms
And Fill advice form 20s 471ms
And Click advice save button and wait for advice form to disappear 33s 447ms
And Go to "TRANSPORT_TABLE" 487ms
And Go to transport details "TRANSPORT_ORDER" 2s 949ms
Then Check are advice values equals 4s 903ms
After Hooks.deleteTransportAfterTest() 840ms
After Hooks.cleanUserDetailsAfterTest() 2s 735ms
@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 422ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 741ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 023ms
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 7s 610ms
When Click button advice in transport table "TRANSPORT_ORDER" 216ms
And Set advice window in schedule 30s 161ms
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-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=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.pNHmdw}, 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: b6a9056a276d095ebf1872182c9c6190
*** 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() 554ms
After Hooks.cleanUserDetailsAfterTest() 1s 764ms
@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 614ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 402ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 018ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 257ms
When Click button advice in transport table "OWN_COLLECTION" 209ms
And Set advice window in schedule 3s 398ms
And Fill advice form 20s 409ms
And Click advice save button and wait for advice form to disappear 33s 275ms
And Go to "TRANSPORT_TABLE" 476ms
Then Check advice data in SK API database "OWN_COLLECTION" 441ms
After Hooks.deleteTransportAfterTest() 809ms
After Hooks.cleanUserDetailsAfterTest() 2s 196ms
@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 383ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 357ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "CONTAINER" created in transport table and set transport id 4s 174ms
When Click button advice in transport table "CONTAINER" 238ms
And Set advice window in schedule 3s 388ms
And Fill advice form 20s 564ms
And Click advice save button and wait for advice form to disappear 33s 248ms
And Go to "TRANSPORT_TABLE" 433ms
Then Check advice data in SK API database "CONTAINER" 241ms
After Hooks.deleteTransportAfterTest() 850ms
After Hooks.cleanUserDetailsAfterTest() 2s 261ms
@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 635ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 462ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 018ms
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 7s 268ms
When Click button advice in transport table "TRANSPORT_ORDER" 221ms
And Set advice window in schedule 3s 392ms
And Fill advice form 20s 476ms
And Click advice save button and wait for advice form to disappear 33s 290ms
And Go to "TRANSPORT_TABLE" 476ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 096ms
After Hooks.deleteTransportAfterTest() 863ms
After Hooks.cleanUserDetailsAfterTest() 2s 161ms
@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 351ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 359ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 017ms
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 025ms
When Click button advice in transport table "TRANSPORT_ORDER" 232ms
And Set advice window in schedule 3s 497ms
And Fill advice form 20s 495ms
And Click advice save button and wait for advice form to disappear 18s 346ms
And Go to "TRANSPORT_TABLE" 495ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 091ms
After Hooks.deleteTransportAfterTest() 939ms
After Hooks.cleanUserDetailsAfterTest() 2s 911ms
@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 712ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 742ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 017ms
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 4s 534ms
When Click button advice in transport table "TRANSPORT_ORDER" 214ms
And Set advice window in schedule 3s 433ms
And Fill advice form 20s 383ms
And Click advice save button and wait for advice form to disappear 33s 780ms
And Go to "TRANSPORT_TABLE" 420ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 305ms
After Hooks.deleteTransportAfterTest() 865ms
After Hooks.cleanUserDetailsAfterTest() 1s 668ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 518ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 956ms
When Click button advice in transport table "CONTAINER" 267ms
And Set advice window in schedule in the past 3s 408ms
And Fill advice form 20s 427ms
And Click advice save button to check error message 207ms
Then Check if possible advice alert is displayed 076ms
After Hooks.deleteTransportAfterTest() 566ms
@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 736ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 015ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 154ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 398ms
And Go to "TRANSPORT_TABLE" 484ms
When Go to transport details "OWN_COLLECTION" 2s 923ms
And Expand advice panel 295ms
And Edit advice in transport details 18s 911ms
And Fill arrival date field 2s 639ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 211ms
Then Check advice data in database after edition "OWN_COLLECTION" 094ms
After Hooks.deleteTransportAfterTest() 800ms
@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 693ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 017ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 969ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 536ms
And Go to "TRANSPORT_TABLE" 479ms
When Go to transport details "CONTAINER" 3s 001ms
And Expand advice panel 233ms
And Edit advice in transport details 18s 912ms
And Fill arrival date field 2s 617ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 221ms
Then Check advice data in database after edition "CONTAINER" 102ms
After Hooks.deleteTransportAfterTest() 823ms
@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 748ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 025ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 019ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 631ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 57s 420ms
And Go to "TRANSPORT_TABLE" 491ms
When Go to transport details "TRANSPORT_ORDER" 2s 894ms
And Expand advice panel 308ms
And Edit advice in transport details 18s 981ms
And Fill arrival date field 2s 636ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 246ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 113ms
After Hooks.deleteTransportAfterTest() 807ms