Project Number Date
ApolloFullRunnerReport apollo-test-2.112 10 sie 2021, 05:53

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 51s 640ms 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 520ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 505ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 923ms
When Click button advice in transport table "CONTAINER" 218ms
And Set advice window in schedule 3s 334ms
And Fill advice form 20s 372ms
And Click advice save button and wait for advice form to disappear 33s 316ms
And Go to "TRANSPORT_TABLE" 464ms
And Go to transport details "CONTAINER" 2s 872ms
Then Check are advice values equals 4s 986ms
After Hooks.cleanUserDetailsAfterTest() 2s 292ms
After Hooks.deleteTransportAfterTest() 787ms
@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 551ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 413ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 158ms
When Click button advice in transport table "OWN_COLLECTION" 231ms
And Set advice window in schedule 3s 409ms
And Fill advice form 20s 334ms
And Click advice save button and wait for advice form to disappear 33s 308ms
And Go to "TRANSPORT_TABLE" 469ms
And Go to transport details "OWN_COLLECTION" 2s 832ms
Then Check are advice values equals 4s 953ms
After Hooks.cleanUserDetailsAfterTest() 2s 153ms
After Hooks.deleteTransportAfterTest() 782ms
@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 396ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 443ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 014ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 223ms
When Click button advice in transport table "TRANSPORT_ORDER" 237ms
And Set advice window in schedule 3s 295ms
And Fill advice form 20s 339ms
And Click advice save button and wait for advice form to disappear 33s 256ms
And Go to "TRANSPORT_TABLE" 469ms
And Go to transport details "TRANSPORT_ORDER" 2s 844ms
Then Check are advice values equals 4s 940ms
After Hooks.cleanUserDetailsAfterTest() 2s 545ms
After Hooks.deleteTransportAfterTest() 858ms
@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 689ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 746ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
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 6s 699ms
When Click button advice in transport table "TRANSPORT_ORDER" 226ms
And Set advice window in schedule 3s 571ms
And Fill advice form 20s 290ms
And Click advice save button and wait for advice form to disappear 18s 364ms
And Go to "TRANSPORT_TABLE" 478ms
And Go to transport details "TRANSPORT_ORDER" 2s 932ms
Then Check are advice values equals 4s 941ms
After Hooks.cleanUserDetailsAfterTest() 2s 653ms
After Hooks.deleteTransportAfterTest() 888ms
@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 596ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 803ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 021ms
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 7s 527ms
When Click button advice in transport table "TRANSPORT_ORDER" 219ms
And Set advice window in schedule 30s 118ms
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=91.0.4472.164)
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=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.LZIrwc}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.164, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 42bf766b86c071969f04804edb2a59a0
*** 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 759ms
After Hooks.deleteTransportAfterTest() 564ms
@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 560ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 365ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 018ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 182ms
When Click button advice in transport table "OWN_COLLECTION" 238ms
And Set advice window in schedule 3s 394ms
And Fill advice form 20s 322ms
And Click advice save button and wait for advice form to disappear 33s 296ms
And Go to "TRANSPORT_TABLE" 493ms
Then Check advice data in SK API database "OWN_COLLECTION" 427ms
After Hooks.cleanUserDetailsAfterTest() 2s 144ms
After Hooks.deleteTransportAfterTest() 795ms
@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 549ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 375ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 018ms
And Check is transport "CONTAINER" created in transport table and set transport id 4s 007ms
When Click button advice in transport table "CONTAINER" 213ms
And Set advice window in schedule 3s 355ms
And Fill advice form 20s 438ms
And Click advice save button and wait for advice form to disappear 33s 231ms
And Go to "TRANSPORT_TABLE" 413ms
Then Check advice data in SK API database "CONTAINER" 206ms
After Hooks.cleanUserDetailsAfterTest() 2s 479ms
After Hooks.deleteTransportAfterTest() 814ms
@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 738ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 373ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
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 7s 380ms
When Click button advice in transport table "TRANSPORT_ORDER" 214ms
And Set advice window in schedule 3s 412ms
And Fill advice form 20s 367ms
And Click advice save button and wait for advice form to disappear 33s 268ms
And Go to "TRANSPORT_TABLE" 501ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 095ms
After Hooks.cleanUserDetailsAfterTest() 2s 140ms
After Hooks.deleteTransportAfterTest() 794ms
@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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 6s 413ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 304ms
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" 016ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 990ms
When Click button advice in transport table "TRANSPORT_ORDER" 208ms
And Set advice window in schedule 3s 437ms
And Fill advice form 20s 469ms
And Click advice save button and wait for advice form to disappear 33s 827ms
And Go to "TRANSPORT_TABLE" 471ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 095ms
After Hooks.cleanUserDetailsAfterTest() 2s 972ms
After Hooks.deleteTransportAfterTest() 793ms
@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 862ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 871ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 021ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 019ms
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" 230ms
And Set advice window in schedule 3s 407ms
And Fill advice form 20s 323ms
And Click advice save button and wait for advice form to disappear 33s 800ms
And Go to "TRANSPORT_TABLE" 458ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 269ms
After Hooks.cleanUserDetailsAfterTest() 1s 735ms
After Hooks.deleteTransportAfterTest() 776ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 475ms
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" 017ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 993ms
When Click button advice in transport table "CONTAINER" 216ms
And Set advice window in schedule in the past 3s 364ms
And Fill advice form 20s 460ms
And Click advice save button to check error message 181ms
Then Check if possible advice alert is displayed 069ms
After Hooks.deleteTransportAfterTest() 588ms
@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 680ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 016ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 170ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 305ms
And Go to "TRANSPORT_TABLE" 455ms
When Go to transport details "OWN_COLLECTION" 2s 872ms
And Expand advice panel 294ms
And Edit advice in transport details 18s 843ms
And Fill arrival date field 2s 594ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 192ms
Then Check advice data in database after edition "OWN_COLLECTION" 097ms
After Hooks.deleteTransportAfterTest() 862ms
@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 633ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 019ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 954ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 326ms
And Go to "TRANSPORT_TABLE" 455ms
When Go to transport details "CONTAINER" 2s 895ms
And Expand advice panel 293ms
And Edit advice in transport details 18s 833ms
And Fill arrival date field 2s 579ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 217ms
Then Check advice data in database after edition "CONTAINER" 092ms
After Hooks.deleteTransportAfterTest() 808ms
@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 666ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 016ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 623ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 57s 267ms
And Go to "TRANSPORT_TABLE" 484ms
When Go to transport details "TRANSPORT_ORDER" 2s 892ms
And Expand advice panel 315ms
And Edit advice in transport details 18s 866ms
And Fill arrival date field 2s 576ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 178ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 111ms
After Hooks.deleteTransportAfterTest() 836ms