Project Number Date
ApolloFullRunnerReport apollo-test-2.162 18 wrz 2021, 06:45

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 15m 58s 358ms 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 676ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 000ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 623ms
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 6s 908ms
When Click button advice in transport table "CONTAINER" 224ms
And Set advice window in schedule 3s 306ms
And Fill advice form 20s 452ms
And Click advice save button and wait for advice form to disappear 18s 333ms
And Go to "TRANSPORT_TABLE" 431ms
And Go to transport details "CONTAINER" 2s 917ms
Then Check are advice values equals 4s 954ms
After Hooks.cleanUserDetailsAfterTest() 2s 313ms
After Hooks.deleteTransportAfterTest() 809ms
@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 631ms
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 430ms
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 4s 111ms
When Click button advice in transport table "OWN_COLLECTION" 243ms
And Set advice window in schedule 3s 365ms
And Fill advice form 20s 502ms
And Click advice save button and wait for advice form to disappear 33s 826ms
And Go to "TRANSPORT_TABLE" 433ms
And Go to transport details "OWN_COLLECTION" 2s 844ms
Then Check are advice values equals 4s 976ms
After Hooks.cleanUserDetailsAfterTest() 2s 166ms
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 "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 463ms
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 366ms
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 7s 496ms
When Click button advice in transport table "TRANSPORT_ORDER" 226ms
And Set advice window in schedule 3s 350ms
And Fill advice form 20s 385ms
And Click advice save button and wait for advice form to disappear 33s 772ms
And Go to "TRANSPORT_TABLE" 464ms
And Go to transport details "TRANSPORT_ORDER" 2s 868ms
Then Check are advice values equals 4s 996ms
After Hooks.cleanUserDetailsAfterTest() 2s 307ms
After Hooks.deleteTransportAfterTest() 823ms
@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 424ms
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 354ms
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 3s 967ms
When Click button advice in transport table "TRANSPORT_ORDER" 223ms
And Set advice window in schedule 3s 333ms
And Fill advice form 20s 412ms
And Click advice save button and wait for advice form to disappear 18s 374ms
And Go to "TRANSPORT_TABLE" 452ms
And Go to transport details "TRANSPORT_ORDER" 2s 854ms
Then Check are advice values equals 4s 927ms
After Hooks.cleanUserDetailsAfterTest() 2s 737ms
After Hooks.deleteTransportAfterTest() 839ms
@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 375ms
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 743ms
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 594ms
When Click button advice in transport table "TRANSPORT_ORDER" 242ms
And Set advice window in schedule 30s 129ms
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.D4viLm}, 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: 1a0924b5cf70a34fbe6c4f76f33173e5
*** 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 762ms
After Hooks.deleteTransportAfterTest() 553ms
@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 362ms
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 372ms
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 "OWN_COLLECTION" created in transport table and set transport id 7s 250ms
When Click button advice in transport table "OWN_COLLECTION" 196ms
And Set advice window in schedule 3s 362ms
And Fill advice form 20s 619ms
And Click advice save button and wait for advice form to disappear 33s 291ms
And Go to "TRANSPORT_TABLE" 440ms
Then Check advice data in SK API database "OWN_COLLECTION" 407ms
After Hooks.cleanUserDetailsAfterTest() 2s 311ms
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 "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 659ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 000ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 495ms
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 "CONTAINER" created in transport table and set transport id 6s 976ms
When Click button advice in transport table "CONTAINER" 216ms
And Set advice window in schedule 3s 368ms
And Fill advice form 20s 486ms
And Click advice save button and wait for advice form to disappear 33s 285ms
And Go to "TRANSPORT_TABLE" 412ms
Then Check advice data in SK API database "CONTAINER" 215ms
After Hooks.cleanUserDetailsAfterTest() 2s 309ms
After Hooks.deleteTransportAfterTest() 828ms
@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 517ms
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 359ms
And Add transport by SKApi in "MGW" assigned to "" 034ms
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 324ms
When Click button advice in transport table "TRANSPORT_ORDER" 227ms
And Set advice window in schedule 3s 460ms
And Fill advice form 20s 481ms
And Click advice save button and wait for advice form to disappear 33s 802ms
And Go to "TRANSPORT_TABLE" 454ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 090ms
After Hooks.cleanUserDetailsAfterTest() 2s 265ms
After Hooks.deleteTransportAfterTest() 836ms
@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 461ms
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 636ms
And Add transport by SKApi in "MGW" assigned to "" 024ms
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 3s 689ms
When Click button advice in transport table "TRANSPORT_ORDER" 196ms
And Set advice window in schedule 3s 351ms
And Fill advice form 20s 614ms
And Click advice save button and wait for advice form to disappear 33s 231ms
And Go to "TRANSPORT_TABLE" 478ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 092ms
After Hooks.cleanUserDetailsAfterTest() 3s 023ms
After Hooks.deleteTransportAfterTest() 819ms
@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 509ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms
And Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file 1s 891ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 7s 518ms
When Click button advice in transport table "TRANSPORT_ORDER" 241ms
And Set advice window in schedule 3s 320ms
And Fill advice form 20s 401ms
And Click advice save button and wait for advice form to disappear 33s 787ms
And Go to "TRANSPORT_TABLE" 495ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 282ms
After Hooks.cleanUserDetailsAfterTest() 1s 686ms
After Hooks.deleteTransportAfterTest() 832ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 776ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 000ms
And Add transport by SKApi in "MGW" assigned to "" 017ms
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 928ms
When Click button advice in transport table "CONTAINER" 231ms
And Set advice window in schedule in the past 3s 344ms
And Fill advice form 20s 553ms
And Click advice save button to check error message 168ms
Then Check if possible advice alert is displayed 064ms
After Hooks.deleteTransportAfterTest() 743ms
@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_OWN_COLLECTION" "super-admin-skz" 001ms
And Add transport by SKApi in "MGW" assigned to "" 023ms
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 123ms
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 298ms
And Go to "TRANSPORT_TABLE" 350ms
When Go to transport details "OWN_COLLECTION" 2s 920ms
And Expand advice panel 304ms
And Edit advice in transport details 19s 241ms
And Fill arrival date field 2s 642ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 243ms
Then Check advice data in database after edition "OWN_COLLECTION" 087ms
After Hooks.deleteTransportAfterTest() 881ms
@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 868ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms
And Add transport by SKApi in "MGW" assigned to "" 028ms
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 3s 926ms
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 800ms
And Go to "TRANSPORT_TABLE" 388ms
When Go to transport details "CONTAINER" 2s 937ms
And Expand advice panel 312ms
And Edit advice in transport details 19s 221ms
And Fill arrival date field 2s 585ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 215ms
Then Check advice data in database after edition "CONTAINER" 090ms
After Hooks.deleteTransportAfterTest() 888ms
@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 832ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Add transport by SKApi in "MGW" assigned to "" 026ms
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 686ms
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 973ms
And Go to "TRANSPORT_TABLE" 363ms
When Go to transport details "TRANSPORT_ORDER" 2s 964ms
And Expand advice panel 255ms
And Edit advice in transport details 19s 206ms
And Fill arrival date field 2s 618ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 229ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 091ms
After Hooks.deleteTransportAfterTest() 875ms