Project Number Date
ApolloFullRunnerReport apollo-test-2.148 07 wrz 2021, 06:21

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 16m 27s 586ms 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 596ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 439ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 916ms
When Click button advice in transport table "CONTAINER" 234ms
And Set advice window in schedule 3s 369ms
And Fill advice form 20s 397ms
And Click advice save button and wait for advice form to disappear 33s 284ms
And Go to "TRANSPORT_TABLE" 452ms
And Go to transport details "CONTAINER" 2s 913ms
Then Check are advice values equals 4s 997ms
After Hooks.cleanUserDetailsAfterTest() 2s 289ms
After Hooks.deleteTransportAfterTest() 788ms
@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 597ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 344ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 116ms
When Click button advice in transport table "OWN_COLLECTION" 229ms
And Set advice window in schedule 3s 431ms
And Fill advice form 20s 388ms
And Click advice save button and wait for advice form to disappear 33s 262ms
And Go to "TRANSPORT_TABLE" 452ms
And Go to transport details "OWN_COLLECTION" 2s 884ms
Then Check are advice values equals 4s 943ms
After Hooks.cleanUserDetailsAfterTest() 2s 141ms
After Hooks.deleteTransportAfterTest() 794ms
@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 197ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 469ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 245ms
When Click button advice in transport table "TRANSPORT_ORDER" 232ms
And Set advice window in schedule 3s 468ms
And Fill advice form 20s 468ms
And Click advice save button and wait for advice form to disappear 33s 317ms
And Go to "TRANSPORT_TABLE" 431ms
And Go to transport details "TRANSPORT_ORDER" 2s 974ms
Then Check are advice values equals 4s 933ms
After Hooks.cleanUserDetailsAfterTest() 2s 345ms
After Hooks.deleteTransportAfterTest() 814ms
@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 547ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 411ms
And Add transport by SKApi in "MGW" assigned to "" 018ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 006ms
When Click button advice in transport table "TRANSPORT_ORDER" 236ms
And Set advice window in schedule 3s 400ms
And Fill advice form 20s 467ms
And Click advice save button and wait for advice form to disappear 33s 857ms
And Go to "TRANSPORT_TABLE" 439ms
And Go to transport details "TRANSPORT_ORDER" 2s 832ms
Then Check are advice values equals 4s 931ms
After Hooks.cleanUserDetailsAfterTest() 2s 721ms
After Hooks.deleteTransportAfterTest() 806ms
@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 390ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 751ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 019ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 663ms
When Click button advice in transport table "TRANSPORT_ORDER" 273ms
And Set advice window in schedule 30s 122ms
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=93.0.4577.63)
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=93.0.4577.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.pT0sMq}, 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=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: e5d58e1fdd819e571fce73e37d49ce81
*** 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:325)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:82)
	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 816ms
After Hooks.deleteTransportAfterTest() 574ms
@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 569ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 364ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 165ms
When Click button advice in transport table "OWN_COLLECTION" 218ms
And Set advice window in schedule 3s 441ms
And Fill advice form 20s 622ms
And Click advice save button and wait for advice form to disappear 33s 224ms
And Go to "TRANSPORT_TABLE" 451ms
Then Check advice data in SK API database "OWN_COLLECTION" 434ms
After Hooks.cleanUserDetailsAfterTest() 2s 181ms
After Hooks.deleteTransportAfterTest() 805ms
@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 149ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 429ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 924ms
When Click button advice in transport table "CONTAINER" 240ms
And Set advice window in schedule 3s 363ms
And Fill advice form 20s 672ms
And Click advice save button and wait for advice form to disappear 33s 307ms
And Go to "TRANSPORT_TABLE" 463ms
Then Check advice data in SK API database "CONTAINER" 198ms
After Hooks.cleanUserDetailsAfterTest() 2s 320ms
After Hooks.deleteTransportAfterTest() 887ms
@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 663ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 367ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 351ms
When Click button advice in transport table "TRANSPORT_ORDER" 220ms
And Set advice window in schedule 3s 409ms
And Fill advice form 20s 488ms
And Click advice save button and wait for advice form to disappear 33s 350ms
And Go to "TRANSPORT_TABLE" 498ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 096ms
After Hooks.cleanUserDetailsAfterTest() 2s 200ms
After Hooks.deleteTransportAfterTest() 874ms
@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 276ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 491ms
And Add transport by SKApi in "MGW" assigned to "" 025ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 001ms
When Click button advice in transport table "TRANSPORT_ORDER" 214ms
And Set advice window in schedule 3s 375ms
And Fill advice form 20s 402ms
And Click advice save button and wait for advice form to disappear 33s 275ms
And Go to "TRANSPORT_TABLE" 489ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 093ms
After Hooks.cleanUserDetailsAfterTest() 3s 006ms
After Hooks.deleteTransportAfterTest() 845ms
@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 713ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 861ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 019ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 582ms
When Click button advice in transport table "TRANSPORT_ORDER" 269ms
And Set advice window in schedule 3s 443ms
And Fill advice form 20s 387ms
And Click advice save button and wait for advice form to disappear 33s 860ms
And Go to "TRANSPORT_TABLE" 430ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 259ms
After Hooks.cleanUserDetailsAfterTest() 1s 725ms
After Hooks.deleteTransportAfterTest() 791ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 231ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 967ms
When Click button advice in transport table "CONTAINER" 210ms
And Set advice window in schedule in the past 3s 428ms
And Fill advice form 20s 330ms
And Click advice save button to check error message 204ms
Then Check if possible advice alert is displayed 071ms
After Hooks.deleteTransportAfterTest() 626ms
@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 Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz" 000ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 231ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-skz" 3s 981ms
And Go to "TRANSPORT_TABLE" 403ms
When Go to transport details "OWN_COLLECTION" 3s 025ms
And Expand advice panel 282ms
And Edit advice in transport details 19s 182ms
And Fill arrival date field 2s 651ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 244ms
Then Check advice data in database after edition "OWN_COLLECTION" 089ms
After Hooks.deleteTransportAfterTest() 807ms
@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 806ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz" 000ms
And Check is transport "CONTAINER" created in transport table and set transport id 7s 040ms
And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-skz" 4s 764ms
And Go to "TRANSPORT_TABLE" 370ms
When Go to transport details "CONTAINER" 2s 898ms
And Expand advice panel 352ms
And Edit advice in transport details 19s 233ms
And Fill arrival date field 2s 626ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 195ms
Then Check advice data in database after edition "CONTAINER" 100ms
After Hooks.deleteTransportAfterTest() 849ms
@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 858ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Add transport by SKApi in "MGW" assigned to "" 024ms
And Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 431ms
And Create advice by JSON file "CREATE_ADVICE_FOR_TRANSPORT_ORDER" as "super-admin-skz" 4s 914ms
And Go to "TRANSPORT_TABLE" 516ms
When Go to transport details "TRANSPORT_ORDER" 3s 019ms
And Expand advice panel 282ms
And Edit advice in transport details 19s 255ms
And Fill arrival date field 2s 650ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 216ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 099ms
After Hooks.deleteTransportAfterTest() 884ms