Project Number Date
ApolloFullRunnerReport apollo-test-2.124 19 sie 2021, 06:07

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 19m 6s 776ms 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 628ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 450ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 023ms
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 973ms
When Click button advice in transport table "CONTAINER" 231ms
And Set advice window in schedule 3s 357ms
And Fill advice form 20s 404ms
And Click advice save button and wait for advice form to disappear 33s 245ms
And Go to "TRANSPORT_TABLE" 449ms
And Go to transport details "CONTAINER" 2s 917ms
Then Check are advice values equals 5s 001ms
After Hooks.cleanUserDetailsAfterTest() 2s 268ms
After Hooks.deleteTransportAfterTest() 851ms
@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" 8s 142ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 340ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 024ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
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 097ms
When Click button advice in transport table "OWN_COLLECTION" 213ms
And Set advice window in schedule 3s 383ms
And Fill advice form 20s 570ms
And Click advice save button and wait for advice form to disappear 33s 291ms
And Go to "TRANSPORT_TABLE" 461ms
And Go to transport details "OWN_COLLECTION" 2s 970ms
Then Check are advice values equals 4s 928ms
After Hooks.cleanUserDetailsAfterTest() 2s 225ms
After Hooks.deleteTransportAfterTest() 785ms
@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 341ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 400ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 025ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 251ms
When Click button advice in transport table "TRANSPORT_ORDER" 249ms
And Set advice window in schedule 3s 364ms
And Fill advice form 20s 409ms
And Click advice save button and wait for advice form to disappear 33s 393ms
And Go to "TRANSPORT_TABLE" 490ms
And Go to transport details "TRANSPORT_ORDER" 2s 855ms
Then Check are advice values equals 4s 965ms
After Hooks.cleanUserDetailsAfterTest() 2s 293ms
After Hooks.deleteTransportAfterTest() 784ms
@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 767ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 502ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 018ms
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 3s 931ms
When Click button advice in transport table "TRANSPORT_ORDER" 232ms
And Set advice window in schedule 3s 567ms
And Fill advice form 20s 529ms
And Click advice save button and wait for advice form to disappear 33s 274ms
And Go to "TRANSPORT_TABLE" 456ms
And Go to transport details "TRANSPORT_ORDER" 2s 865ms
Then Check are advice values equals 5s 042ms
After Hooks.cleanUserDetailsAfterTest() 2s 701ms
After Hooks.deleteTransportAfterTest() 799ms
@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) 000ms
Steps
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 624ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 856ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 023ms
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 576ms
When Click button advice in transport table "TRANSPORT_ORDER" 253ms
And Set advice window in schedule 30s 086ms
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.K4IZfJ}, 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: 4ec7d232f7c159b2a5822920825b61b3
*** 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: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 762ms
After Hooks.deleteTransportAfterTest() 552ms
@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 605ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 410ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 018ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 222ms
When Click button advice in transport table "OWN_COLLECTION" 235ms
And Set advice window in schedule 3s 404ms
And Fill advice form 20s 406ms
And Click advice save button and wait for advice form to disappear 33s 260ms
And Go to "TRANSPORT_TABLE" 385ms
Then Check advice data in SK API database "OWN_COLLECTION" 487ms
After Hooks.cleanUserDetailsAfterTest() 2s 217ms
After Hooks.deleteTransportAfterTest() 789ms
@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 421ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 344ms
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" 021ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 977ms
When Click button advice in transport table "CONTAINER" 237ms
And Set advice window in schedule 3s 334ms
And Fill advice form 20s 497ms
And Click advice save button and wait for advice form to disappear 33s 295ms
And Go to "TRANSPORT_TABLE" 447ms
Then Check advice data in SK API database "CONTAINER" 236ms
After Hooks.cleanUserDetailsAfterTest() 2s 256ms
After Hooks.deleteTransportAfterTest() 753ms
@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 714ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 396ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
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 4s 240ms
When Click button advice in transport table "TRANSPORT_ORDER" 218ms
And Set advice window in schedule 3s 404ms
And Fill advice form 20s 286ms
And Click advice save button and wait for advice form to disappear 33s 840ms
And Go to "TRANSPORT_TABLE" 506ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 089ms
After Hooks.cleanUserDetailsAfterTest() 2s 203ms
After Hooks.deleteTransportAfterTest() 835ms
@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 539ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 571ms
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" 015ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 734ms
When Click button advice in transport table "TRANSPORT_ORDER" 207ms
And Set advice window in schedule 3s 505ms
And Fill advice form 20s 381ms
And Click advice save button and wait for advice form to disappear 33s 357ms
And Go to "TRANSPORT_TABLE" 531ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 096ms
After Hooks.cleanUserDetailsAfterTest() 2s 975ms
After Hooks.deleteTransportAfterTest() 873ms
@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 832ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 853ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 024ms
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 682ms
When Click button advice in transport table "TRANSPORT_ORDER" 227ms
And Set advice window in schedule 3s 387ms
And Fill advice form 20s 495ms
And Click advice save button and wait for advice form to disappear 33s 785ms
And Go to "TRANSPORT_TABLE" 489ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 249ms
After Hooks.cleanUserDetailsAfterTest() 1s 838ms
After Hooks.deleteTransportAfterTest() 815ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 575ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 018ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 019ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 976ms
When Click button advice in transport table "CONTAINER" 233ms
And Set advice window in schedule in the past 3s 366ms
And Fill advice form 20s 633ms
And Click advice save button to check error message 186ms
Then Check if possible advice alert is displayed 067ms
After Hooks.deleteTransportAfterTest() 585ms
@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 757ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
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 147ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 225ms
And Go to "TRANSPORT_TABLE" 381ms
When Go to transport details "OWN_COLLECTION" 2s 918ms
And Expand advice panel 269ms
And Edit advice in transport details 18s 866ms
And Fill arrival date field 2s 665ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 244ms
Then Check advice data in database after edition "OWN_COLLECTION" 087ms
After Hooks.deleteTransportAfterTest() 923ms
@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 788ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
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 994ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 504ms
And Go to "TRANSPORT_TABLE" 471ms
When Go to transport details "CONTAINER" 2s 890ms
And Expand advice panel 316ms
And Edit advice in transport details 18s 944ms
And Fill arrival date field 2s 634ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 242ms
Then Check advice data in database after edition "CONTAINER" 094ms
After Hooks.deleteTransportAfterTest() 774ms
@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 735ms
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 "EDIT_ADVICE" "super-admin-skz" 017ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 655ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 57s 337ms
And Go to "TRANSPORT_TABLE" 464ms
When Go to transport details "TRANSPORT_ORDER" 2s 941ms
And Expand advice panel 261ms
And Edit advice in transport details 18s 895ms
And Fill arrival date field 2s 604ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 260ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 096ms
After Hooks.deleteTransportAfterTest() 747ms