Project Number Date
ApolloFullRunnerReport apollo-test-2.161 17 wrz 2021, 07:00

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 43s 696ms 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 655ms
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 432ms
And Add transport by SKApi in "MGW" assigned to "" 029ms
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 13s 109ms
When Click button advice in transport table "CONTAINER" 267ms
And Set advice window in schedule 3s 418ms
And Fill advice form 20s 392ms
And Click advice save button and wait for advice form to disappear 33s 213ms
And Go to "TRANSPORT_TABLE" 426ms
And Go to transport details "CONTAINER" 2s 841ms
Then Check are advice values equals 4s 919ms
After Hooks.cleanUserDetailsAfterTest() 2s 425ms
After Hooks.deleteTransportAfterTest() 863ms
@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 634ms
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 479ms
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 098ms
When Click button advice in transport table "OWN_COLLECTION" 220ms
And Set advice window in schedule 3s 277ms
And Fill advice form 20s 590ms
And Click advice save button and wait for advice form to disappear 33s 363ms
And Go to "TRANSPORT_TABLE" 467ms
And Go to transport details "OWN_COLLECTION" 2s 846ms
Then Check are advice values equals 5s
After Hooks.cleanUserDetailsAfterTest() 2s 104ms
After Hooks.deleteTransportAfterTest() 837ms
@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 305ms
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 379ms
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 410ms
When Click button advice in transport table "TRANSPORT_ORDER" 212ms
And Set advice window in schedule 3s 360ms
And Fill advice form 20s 408ms
And Click advice save button and wait for advice form to disappear 33s 758ms
And Go to "TRANSPORT_TABLE" 468ms
And Go to transport details "TRANSPORT_ORDER" 2s 937ms
Then Check are advice values equals 4s 924ms
After Hooks.cleanUserDetailsAfterTest() 2s 314ms
After Hooks.deleteTransportAfterTest() 859ms
@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 451ms
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 803ms
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 748ms
When Click button advice in transport table "TRANSPORT_ORDER" 212ms
And Set advice window in schedule 3s 296ms
And Fill advice form 20s 517ms
And Click advice save button and wait for advice form to disappear 33s 948ms
And Go to "TRANSPORT_TABLE" 463ms
And Go to transport details "TRANSPORT_ORDER" 2s 861ms
Then Check are advice values equals 4s 972ms
After Hooks.cleanUserDetailsAfterTest() 2s 761ms
After Hooks.deleteTransportAfterTest() 848ms
@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 402ms
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 726ms
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" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 563ms
When Click button advice in transport table "TRANSPORT_ORDER" 222ms
And Set advice window in schedule 30s 135ms
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.y4uQ3Z}, 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: fff6f85508e056c6680aae6c5effae26
*** 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 833ms
After Hooks.deleteTransportAfterTest() 567ms
@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 479ms
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 387ms
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 "OWN_COLLECTION" created in transport table and set transport id 7s 162ms
When Click button advice in transport table "OWN_COLLECTION" 218ms
And Set advice window in schedule 3s 334ms
And Fill advice form 20s 371ms
And Click advice save button and wait for advice form to disappear 33s 297ms
And Go to "TRANSPORT_TABLE" 449ms
Then Check advice data in SK API database "OWN_COLLECTION" 419ms
After Hooks.cleanUserDetailsAfterTest() 2s 109ms
After Hooks.deleteTransportAfterTest() 822ms
@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 327ms
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 387ms
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 6s 923ms
When Click button advice in transport table "CONTAINER" 235ms
And Set advice window in schedule 3s 302ms
And Fill advice form 20s 554ms
And Click advice save button and wait for advice form to disappear 33s 344ms
And Go to "TRANSPORT_TABLE" 454ms
Then Check advice data in SK API database "CONTAINER" 181ms
After Hooks.cleanUserDetailsAfterTest() 2s 365ms
After Hooks.deleteTransportAfterTest() 848ms
@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 610ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 395ms
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 "TRANSPORT_ORDER" created in transport table and set transport id 7s 330ms
When Click button advice in transport table "TRANSPORT_ORDER" 225ms
And Set advice window in schedule 3s 370ms
And Fill advice form 20s 433ms
And Click advice save button and wait for advice form to disappear 33s 293ms
And Go to "TRANSPORT_TABLE" 492ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 095ms
After Hooks.cleanUserDetailsAfterTest() 2s 231ms
After Hooks.deleteTransportAfterTest() 879ms
@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 490ms
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 831ms
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 "TRANSPORT_ORDER" created in transport table and set transport id 6s 741ms
When Click button advice in transport table "TRANSPORT_ORDER" 244ms
And Set advice window in schedule 3s 390ms
And Fill advice form 20s 299ms
And Click advice save button and wait for advice form to disappear 33s 327ms
And Go to "TRANSPORT_TABLE" 510ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 087ms
After Hooks.cleanUserDetailsAfterTest() 2s 953ms
After Hooks.deleteTransportAfterTest() 866ms
@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 577ms
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 975ms
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 572ms
When Click button advice in transport table "TRANSPORT_ORDER" 209ms
And Set advice window in schedule 3s 356ms
And Fill advice form 20s 464ms
And Click advice save button and wait for advice form to disappear 33s 867ms
And Go to "TRANSPORT_TABLE" 464ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 268ms
After Hooks.cleanUserDetailsAfterTest() 1s 678ms
After Hooks.deleteTransportAfterTest() 808ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 252ms
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 946ms
When Click button advice in transport table "CONTAINER" 231ms
And Set advice window in schedule in the past 3s 285ms
And Fill advice form 20s 517ms
And Click advice save button to check error message 189ms
Then Check if possible advice alert is displayed 063ms
After Hooks.deleteTransportAfterTest() 563ms
@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 860ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 000ms
And Add transport by SKApi in "MGW" assigned to "" 023ms
And Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz" 001ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 164ms
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" 4s 097ms
And Go to "TRANSPORT_TABLE" 362ms
When Go to transport details "OWN_COLLECTION" 2s 934ms
And Expand advice panel 322ms
And Edit advice in transport details 19s 246ms
And Fill arrival date field 2s 611ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 219ms
Then Check advice data in database after edition "OWN_COLLECTION" 090ms
After Hooks.deleteTransportAfterTest() 872ms
@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 959ms
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 "EDIT_ADVICE" "super-admin-skz" 000ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 947ms
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 886ms
And Go to "TRANSPORT_TABLE" 380ms
When Go to transport details "CONTAINER" 2s 922ms
And Expand advice panel 343ms
And Edit advice in transport details 19s 333ms
And Fill arrival date field 2s 628ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 208ms
Then Check advice data in database after edition "CONTAINER" 081ms
After Hooks.deleteTransportAfterTest() 867ms
@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 840ms
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" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 709ms
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 985ms
And Go to "TRANSPORT_TABLE" 355ms
When Go to transport details "TRANSPORT_ORDER" 2s 982ms
And Expand advice panel 251ms
And Edit advice in transport details 19s 319ms
And Fill arrival date field 2s 637ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 190ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 093ms
After Hooks.deleteTransportAfterTest() 815ms