Project Number Date
ApolloFullRunnerReport apollo-test-2.110 08 sie 2021, 05:43

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 19m 1s 101ms 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 570ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 411ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
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 938ms
When Click button advice in transport table "CONTAINER" 205ms
And Set advice window in schedule 3s 327ms
And Fill advice form 20s 105ms
And Click advice save button and wait for advice form to disappear 33s 315ms
And Go to "TRANSPORT_TABLE" 443ms
And Go to transport details "CONTAINER" 2s 857ms
Then Check are advice values equals 4s 968ms
After Hooks.cleanUserDetailsAfterTest() 2s 440ms
After Hooks.deleteTransportAfterTest() 789ms
@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 365ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 395ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms
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 "OWN_COLLECTION" created in transport table and set transport id 7s 186ms
When Click button advice in transport table "OWN_COLLECTION" 231ms
And Set advice window in schedule 3s 352ms
And Fill advice form 20s 302ms
And Click advice save button and wait for advice form to disappear 33s 213ms
And Go to "TRANSPORT_TABLE" 468ms
And Go to transport details "OWN_COLLECTION" 2s 846ms
Then Check are advice values equals 4s 997ms
After Hooks.cleanUserDetailsAfterTest() 2s 110ms
After Hooks.deleteTransportAfterTest() 769ms
@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 276ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 385ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
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 295ms
When Click button advice in transport table "TRANSPORT_ORDER" 236ms
And Set advice window in schedule 3s 326ms
And Fill advice form 20s 305ms
And Click advice save button and wait for advice form to disappear 33s 805ms
And Go to "TRANSPORT_TABLE" 525ms
And Go to transport details "TRANSPORT_ORDER" 2s 860ms
Then Check are advice values equals 5s 044ms
After Hooks.cleanUserDetailsAfterTest() 2s 288ms
After Hooks.deleteTransportAfterTest() 757ms
@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 560ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 505ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "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 "TRANSPORT_ORDER" created in transport table and set transport id 7s 727ms
When Click button advice in transport table "TRANSPORT_ORDER" 214ms
And Set advice window in schedule 3s 305ms
And Fill advice form 20s 384ms
And Click advice save button and wait for advice form to disappear 33s 281ms
And Go to "TRANSPORT_TABLE" 511ms
And Go to transport details "TRANSPORT_ORDER" 2s 878ms
Then Check are advice values equals 4s 992ms
After Hooks.cleanUserDetailsAfterTest() 2s 779ms
After Hooks.deleteTransportAfterTest() 801ms
@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 239ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 711ms
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" 018ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 584ms
When Click button advice in transport table "TRANSPORT_ORDER" 221ms
And Set advice window in schedule 30s 132ms
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.3oPbFb}, 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: 36cadbb2edc2fd796a0d83765e8aed82
*** 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.cleanUserDetailsAfterTest() 1s 771ms
After Hooks.deleteTransportAfterTest() 550ms
@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 418ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 411ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
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 122ms
When Click button advice in transport table "OWN_COLLECTION" 216ms
And Set advice window in schedule 3s 374ms
And Fill advice form 20s 346ms
And Click advice save button and wait for advice form to disappear 33s 252ms
And Go to "TRANSPORT_TABLE" 460ms
Then Check advice data in SK API database "OWN_COLLECTION" 453ms
After Hooks.cleanUserDetailsAfterTest() 2s 074ms
After Hooks.deleteTransportAfterTest() 802ms
@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" 7s 437ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 341ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 023ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 948ms
When Click button advice in transport table "CONTAINER" 199ms
And Set advice window in schedule 3s 355ms
And Fill advice form 20s 242ms
And Click advice save button and wait for advice form to disappear 33s 312ms
And Go to "TRANSPORT_TABLE" 467ms
Then Check advice data in SK API database "CONTAINER" 205ms
After Hooks.cleanUserDetailsAfterTest() 2s 457ms
After Hooks.deleteTransportAfterTest() 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 527ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 389ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
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 "TRANSPORT_ORDER" created in transport table and set transport id 4s 208ms
When Click button advice in transport table "TRANSPORT_ORDER" 212ms
And Set advice window in schedule 3s 345ms
And Fill advice form 20s 383ms
And Click advice save button and wait for advice form to disappear 33s 250ms
And Go to "TRANSPORT_TABLE" 485ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 098ms
After Hooks.cleanUserDetailsAfterTest() 2s 118ms
After Hooks.deleteTransportAfterTest() 843ms
@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 288ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 244ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 016ms
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 048ms
When Click button advice in transport table "TRANSPORT_ORDER" 215ms
And Set advice window in schedule 3s 357ms
And Fill advice form 20s 326ms
And Click advice save button and wait for advice form to disappear 33s 914ms
And Go to "TRANSPORT_TABLE" 457ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 098ms
After Hooks.cleanUserDetailsAfterTest() 2s 989ms
After Hooks.deleteTransportAfterTest() 831ms
@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 614ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 857ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 019ms
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 546ms
When Click button advice in transport table "TRANSPORT_ORDER" 218ms
And Set advice window in schedule 3s 375ms
And Fill advice form 20s 336ms
And Click advice save button and wait for advice form to disappear 33s 826ms
And Go to "TRANSPORT_TABLE" 421ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 270ms
After Hooks.cleanUserDetailsAfterTest() 1s 692ms
After Hooks.deleteTransportAfterTest() 780ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 235ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 023ms
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 "CONTAINER" created in transport table and set transport id 6s 952ms
When Click button advice in transport table "CONTAINER" 192ms
And Set advice window in schedule in the past 3s 300ms
And Fill advice form 20s 358ms
And Click advice save button to check error message 186ms
Then Check if possible advice alert is displayed 064ms
After Hooks.deleteTransportAfterTest() 598ms
@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) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 538ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 016ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 123ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 192ms
And Go to "TRANSPORT_TABLE" 453ms
When Go to transport details "OWN_COLLECTION" 2s 836ms
And Expand advice panel 268ms
And Edit advice in transport details 18s 866ms
And Fill arrival date field 2s 649ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 215ms
Then Check advice data in database after edition "OWN_COLLECTION" 104ms
After Hooks.deleteTransportAfterTest() 851ms
@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 641ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 018ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 018ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 936ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 100ms
And Go to "TRANSPORT_TABLE" 455ms
When Go to transport details "CONTAINER" 2s 832ms
And Expand advice panel 271ms
And Edit advice in transport details 18s 878ms
And Fill arrival date field 2s 638ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 232ms
Then Check advice data in database after edition "CONTAINER" 104ms
After Hooks.deleteTransportAfterTest() 805ms
@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 653ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 015ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 611ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 57s 299ms
And Go to "TRANSPORT_TABLE" 464ms
When Go to transport details "TRANSPORT_ORDER" 2s 852ms
And Expand advice panel 287ms
And Edit advice in transport details 18s 893ms
And Fill arrival date field 2s 579ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 180ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 104ms
After Hooks.deleteTransportAfterTest() 815ms