Project Number Date
ApolloFullRunnerReport apollo-test-2.120 16 sie 2021, 06: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 18m 31s 187ms 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 538ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 523ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms
And Check is transport "CONTAINER" created in transport table and set transport id 7s 128ms
When Click button advice in transport table "CONTAINER" 263ms
And Set advice window in schedule 3s 432ms
And Fill advice form 20s 535ms
And Click advice save button and wait for advice form to disappear 33s 363ms
And Go to "TRANSPORT_TABLE" 455ms
And Go to transport details "CONTAINER" 2s 898ms
Then Check are advice values equals 4s 976ms
After Hooks.cleanUserDetailsAfterTest() 2s 378ms
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 "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 684ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 392ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms
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 "OWN_COLLECTION" created in transport table and set transport id 4s 157ms
When Click button advice in transport table "OWN_COLLECTION" 221ms
And Set advice window in schedule 3s 387ms
And Fill advice form 20s 404ms
And Click advice save button and wait for advice form to disappear 33s 203ms
And Go to "TRANSPORT_TABLE" 508ms
And Go to transport details "OWN_COLLECTION" 2s 984ms
Then Check are advice values equals 4s 967ms
After Hooks.cleanUserDetailsAfterTest() 2s 170ms
After Hooks.deleteTransportAfterTest() 835ms
@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 458ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 364ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
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 338ms
When Click button advice in transport table "TRANSPORT_ORDER" 219ms
And Set advice window in schedule 3s 411ms
And Fill advice form 20s 523ms
And Click advice save button and wait for advice form to disappear 33s 263ms
And Go to "TRANSPORT_TABLE" 477ms
And Go to transport details "TRANSPORT_ORDER" 2s 849ms
Then Check are advice values equals 5s 036ms
After Hooks.cleanUserDetailsAfterTest() 2s 232ms
After Hooks.deleteTransportAfterTest() 779ms
@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 834ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 490ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms
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 4s 761ms
When Click button advice in transport table "TRANSPORT_ORDER" 194ms
And Set advice window in schedule 3s 412ms
And Fill advice form 20s 534ms
And Click advice save button and wait for advice form to disappear 33s 255ms
And Go to "TRANSPORT_TABLE" 470ms
And Go to transport details "TRANSPORT_ORDER" 2s 818ms
Then Check are advice values equals 4s 983ms
After Hooks.cleanUserDetailsAfterTest() 2s 713ms
After Hooks.deleteTransportAfterTest() 905ms
@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 724ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 751ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 019ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 497ms
When Click button advice in transport table "TRANSPORT_ORDER" 235ms
And Set advice window in schedule 30s 100ms
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=92.0.4515.131)
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=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.3zdI0E}, 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=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a54bcfb9f282785de8230b0d9aa78078
*** 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 817ms
After Hooks.deleteTransportAfterTest() 538ms
@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 943ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 430ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 019ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 169ms
When Click button advice in transport table "OWN_COLLECTION" 230ms
And Set advice window in schedule 3s 417ms
And Fill advice form 20s 458ms
And Click advice save button and wait for advice form to disappear 33s 282ms
And Go to "TRANSPORT_TABLE" 454ms
Then Check advice data in SK API database "OWN_COLLECTION" 419ms
After Hooks.cleanUserDetailsAfterTest() 2s 132ms
After Hooks.deleteTransportAfterTest() 815ms
@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 471ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 354ms
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" 019ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 917ms
When Click button advice in transport table "CONTAINER" 239ms
And Set advice window in schedule 3s 426ms
And Fill advice form 20s 303ms
And Click advice save button and wait for advice form to disappear 33s 303ms
And Go to "TRANSPORT_TABLE" 461ms
Then Check advice data in SK API database "CONTAINER" 208ms
After Hooks.cleanUserDetailsAfterTest() 2s 269ms
After Hooks.deleteTransportAfterTest() 811ms
@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 813ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 366ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 024ms
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 304ms
When Click button advice in transport table "TRANSPORT_ORDER" 283ms
And Set advice window in schedule 3s 375ms
And Fill advice form 20s 575ms
And Click advice save button and wait for advice form to disappear 18s 382ms
And Go to "TRANSPORT_TABLE" 482ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 103ms
After Hooks.cleanUserDetailsAfterTest() 2s 233ms
After Hooks.deleteTransportAfterTest() 809ms
@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 425ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 552ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 018ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 840ms
When Click button advice in transport table "TRANSPORT_ORDER" 233ms
And Set advice window in schedule 3s 513ms
And Fill advice form 20s 508ms
And Click advice save button and wait for advice form to disappear 33s 231ms
And Go to "TRANSPORT_TABLE" 505ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 090ms
After Hooks.cleanUserDetailsAfterTest() 3s 167ms
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-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 8s 830ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 910ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 566ms
When Click button advice in transport table "TRANSPORT_ORDER" 220ms
And Set advice window in schedule 3s 429ms
And Fill advice form 20s 275ms
And Click advice save button and wait for advice form to disappear 33s 769ms
And Go to "TRANSPORT_TABLE" 481ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 274ms
After Hooks.cleanUserDetailsAfterTest() 1s 785ms
After Hooks.deleteTransportAfterTest() 781ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 599ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "" 018ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 015ms
And Check is transport "CONTAINER" created in transport table and set transport id 7s 007ms
When Click button advice in transport table "CONTAINER" 227ms
And Set advice window in schedule in the past 3s 379ms
And Fill advice form 20s 427ms
And Click advice save button to check error message 167ms
Then Check if possible advice alert is displayed 065ms
After Hooks.deleteTransportAfterTest() 590ms
@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 777ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 017ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 164ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 285ms
And Go to "TRANSPORT_TABLE" 440ms
When Go to transport details "OWN_COLLECTION" 2s 877ms
And Expand advice panel 306ms
And Edit advice in transport details 18s 843ms
And Fill arrival date field 2s 648ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 251ms
Then Check advice data in database after edition "OWN_COLLECTION" 093ms
After Hooks.deleteTransportAfterTest() 787ms
@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 803ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 024ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 018ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 929ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 408ms
And Go to "TRANSPORT_TABLE" 473ms
When Go to transport details "CONTAINER" 2s 974ms
And Expand advice panel 269ms
And Edit advice in transport details 18s 834ms
And Fill arrival date field 2s 621ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 252ms
Then Check advice data in database after edition "CONTAINER" 098ms
After Hooks.deleteTransportAfterTest() 810ms
@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 675ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 023ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 017ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 635ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 42s 356ms
And Go to "TRANSPORT_TABLE" 515ms
When Go to transport details "TRANSPORT_ORDER" 2s 980ms
And Expand advice panel 261ms
And Edit advice in transport details 18s 844ms
And Fill arrival date field 2s 631ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 237ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 101ms
After Hooks.deleteTransportAfterTest() 807ms