Project Number Date
ApolloFullRunnerReport apollo-test-2.158 15 wrz 2021, 06:58

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 38s 900ms 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 696ms
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 422ms
And Add transport by SKApi in "MGW" assigned to "" 023ms
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 9s 948ms
When Click button advice in transport table "CONTAINER" 220ms
And Set advice window in schedule 3s 364ms
And Fill advice form 20s 246ms
And Click advice save button and wait for advice form to disappear 33s 262ms
And Go to "TRANSPORT_TABLE" 465ms
And Go to transport details "CONTAINER" 2s 893ms
Then Check are advice values equals 4s 948ms
After Hooks.cleanUserDetailsAfterTest() 2s 427ms
After Hooks.deleteTransportAfterTest() 750ms
@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 756ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 000ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 377ms
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 "OWN_COLLECTION" created in transport table and set transport id 7s 165ms
When Click button advice in transport table "OWN_COLLECTION" 214ms
And Set advice window in schedule 3s 335ms
And Fill advice form 20s 764ms
And Click advice save button and wait for advice form to disappear 33s 267ms
And Go to "TRANSPORT_TABLE" 451ms
And Go to transport details "OWN_COLLECTION" 2s 850ms
Then Check are advice values equals 4s 959ms
After Hooks.cleanUserDetailsAfterTest() 2s 121ms
After Hooks.deleteTransportAfterTest() 720ms
@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 443ms
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 375ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
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 397ms
When Click button advice in transport table "TRANSPORT_ORDER" 207ms
And Set advice window in schedule 3s 382ms
And Fill advice form 20s 390ms
And Click advice save button and wait for advice form to disappear 33s 210ms
And Go to "TRANSPORT_TABLE" 489ms
And Go to transport details "TRANSPORT_ORDER" 2s 824ms
Then Check are advice values equals 4s 991ms
After Hooks.cleanUserDetailsAfterTest() 2s 313ms
After Hooks.deleteTransportAfterTest() 833ms
@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" and set token of apiUsername "super-admin-skz" 8s 511ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "pskza1-carrier" details with all notifications and "" by JSON file 3s 609ms
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 7s 727ms
When Click button advice in transport table "TRANSPORT_ORDER" 209ms
And Set advice window in schedule 3s 389ms
And Fill advice form 20s 415ms
And Click advice save button and wait for advice form to disappear 33s 300ms
And Go to "TRANSPORT_TABLE" 517ms
And Go to transport details "TRANSPORT_ORDER" 2s 874ms
Then Check are advice values equals 4s 973ms
After Hooks.cleanUserDetailsAfterTest() 2s 694ms
After Hooks.deleteTransportAfterTest() 764ms
@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" and set token of apiUsername "super-admin-skz" 7s 449ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file 1s 730ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 021ms
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 530ms
When Click button advice in transport table "TRANSPORT_ORDER" 203ms
And Set advice window in schedule 30s 123ms
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.63 (ff5c0da2ec0adeaed5550e6c7e98417dac77d98a-refs/branch-heads/4577@{#1135}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.FGRir8}, 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: 1200fca61a4ea8963b6e3429618a28eb
*** 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:83)
	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 778ms
After Hooks.deleteTransportAfterTest() 498ms
@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 777ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 000ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 397ms
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 191ms
When Click button advice in transport table "OWN_COLLECTION" 226ms
And Set advice window in schedule 3s 332ms
And Fill advice form 20s 467ms
And Click advice save button and wait for advice form to disappear 33s 248ms
And Go to "TRANSPORT_TABLE" 464ms
Then Check advice data in SK API database "OWN_COLLECTION" 446ms
After Hooks.cleanUserDetailsAfterTest() 2s 270ms
After Hooks.deleteTransportAfterTest() 745ms
@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 532ms
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 382ms
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 3s 900ms
When Click button advice in transport table "CONTAINER" 220ms
And Set advice window in schedule 3s 323ms
And Fill advice form 20s 570ms
And Click advice save button and wait for advice form to disappear 33s 193ms
And Go to "TRANSPORT_TABLE" 447ms
Then Check advice data in SK API database "CONTAINER" 237ms
After Hooks.cleanUserDetailsAfterTest() 2s 340ms
After Hooks.deleteTransportAfterTest() 855ms
@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 682ms
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 417ms
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 292ms
When Click button advice in transport table "TRANSPORT_ORDER" 205ms
And Set advice window in schedule 3s 413ms
And Fill advice form 20s 393ms
And Click advice save button and wait for advice form to disappear 33s 300ms
And Go to "TRANSPORT_TABLE" 492ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 089ms
After Hooks.cleanUserDetailsAfterTest() 2s 145ms
After Hooks.deleteTransportAfterTest() 771ms
@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" and set token of apiUsername "super-admin-skz" 6s 486ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms
And Prepare user "pskza1-carrier" details with all notifications and "" by JSON file 3s 407ms
And Add transport by SKApi in "MGW" assigned to "" 027ms
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 788ms
When Click button advice in transport table "TRANSPORT_ORDER" 203ms
And Set advice window in schedule 3s 421ms
And Fill advice form 20s 449ms
And Click advice save button and wait for advice form to disappear 33s 196ms
And Go to "TRANSPORT_TABLE" 473ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 088ms
After Hooks.cleanUserDetailsAfterTest() 3s 039ms
After Hooks.deleteTransportAfterTest() 839ms
@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" and set token of apiUsername "super-admin-skz" 8s 776ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file 1s 856ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 023ms
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 551ms
When Click button advice in transport table "TRANSPORT_ORDER" 218ms
And Set advice window in schedule 3s 469ms
And Fill advice form 20s 462ms
And Click advice save button and wait for advice form to disappear 33s 832ms
And Go to "TRANSPORT_TABLE" 426ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 271ms
After Hooks.cleanUserDetailsAfterTest() 1s 674ms
After Hooks.deleteTransportAfterTest() 733ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 514ms
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 "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 978ms
When Click button advice in transport table "CONTAINER" 214ms
And Set advice window in schedule in the past 3s 341ms
And Fill advice form 20s 432ms
And Click advice save button to check error message 184ms
Then Check if possible advice alert is displayed 069ms
After Hooks.deleteTransportAfterTest() 556ms
@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 744ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id 7s 150ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-skz" with window starts at "07:00" and ends at "08:00" 3s 754ms
And Go to "TRANSPORT_TABLE" 355ms
When Go to transport details "OWN_COLLECTION" 2s 960ms
And Expand advice panel 259ms
And Edit advice in transport details 19s 147ms
And Fill arrival date field 2s 626ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 184ms
Then Check advice data in database after edition "OWN_COLLECTION" 086ms
After Hooks.deleteTransportAfterTest() 747ms
@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 856ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms
And Add transport by SKApi in "MGW" assigned to "" 035ms
And Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz" 001ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 955ms
And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-skz" with window starts at "07:00" and ends at "08:00" 4s 232ms
And Go to "TRANSPORT_TABLE" 350ms
When Go to transport details "CONTAINER" 2s 956ms
And Expand advice panel 319ms
And Edit advice in transport details 19s 226ms
And Fill arrival date field 2s 621ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 241ms
Then Check advice data in database after edition "CONTAINER" 092ms
After Hooks.deleteTransportAfterTest() 839ms
@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 811ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
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 6s 673ms
And Create advice by JSON file "CREATE_ADVICE_FOR_TRANSPORT_ORDER" as "super-admin-skz" with window starts at "07:00" and ends at "08:00" 4s 486ms
And Go to "TRANSPORT_TABLE" 349ms
When Go to transport details "TRANSPORT_ORDER" 3s 042ms
And Expand advice panel 277ms
And Edit advice in transport details 19s 186ms
And Fill arrival date field 2s 617ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 232ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 094ms
After Hooks.deleteTransportAfterTest() 807ms