Project Number Date
ApolloFullRunnerReport 2021.AT1.53 08 sie 2021, 05:27

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 23s 464ms 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" 1s 082ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 371ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 309ms
When Click button advice in transport table "CONTAINER" 081ms
And Set advice window in schedule 2s 556ms
And Fill advice form 16s 757ms
And Click advice save button and wait for advice form to disappear 30s 689ms
And Go to "TRANSPORT_TABLE" 179ms
And Go to transport details "CONTAINER" 2s 433ms
Then Check are advice values equals 4s 362ms
After Hooks.deleteTransportAfterTest() 117ms
After Hooks.cleanUserDetailsAfterTest() 298ms
@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" 1s 931ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 341ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 361ms
When Click button advice in transport table "OWN_COLLECTION" 087ms
And Set advice window in schedule 2s 533ms
And Fill advice form 16s 725ms
And Click advice save button and wait for advice form to disappear 30s 734ms
And Go to "TRANSPORT_TABLE" 207ms
And Go to transport details "OWN_COLLECTION" 2s 463ms
Then Check are advice values equals 4s 345ms
After Hooks.deleteTransportAfterTest() 111ms
After Hooks.cleanUserDetailsAfterTest() 289ms
@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) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 861ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 333ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 824ms
When Click button advice in transport table "TRANSPORT_ORDER" 093ms
And Set advice window in schedule 2s 567ms
And Fill advice form 16s 756ms
And Click advice save button and wait for advice form to disappear 30s 737ms
And Go to "TRANSPORT_TABLE" 223ms
And Go to transport details "TRANSPORT_ORDER" 2s 431ms
Then Check are advice values equals 4s 343ms
After Hooks.deleteTransportAfterTest() 105ms
After Hooks.cleanUserDetailsAfterTest() 266ms
@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) 000ms
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 052ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 514ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 035ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 837ms
When Click button advice in transport table "TRANSPORT_ORDER" 092ms
And Set advice window in schedule 2s 528ms
And Fill advice form 16s 704ms
And Click advice save button and wait for advice form to disappear 30s 703ms
And Go to "TRANSPORT_TABLE" 196ms
And Go to transport details "TRANSPORT_ORDER" 2s 425ms
Then Check are advice values equals 4s 306ms
After Hooks.deleteTransportAfterTest() 107ms
After Hooks.cleanUserDetailsAfterTest() 382ms
@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" 1s 846ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 249ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 909ms
When Click button advice in transport table "TRANSPORT_ORDER" 101ms
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', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-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-2/temp/buildTmp/.com.google.Chrome.VuF74C}, 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: 3aebfea12f6369bf3463b915382edcfe
*** 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.deleteTransportAfterTest() 080ms
After Hooks.cleanUserDetailsAfterTest() 210ms
@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" 1s 810ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 328ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 361ms
When Click button advice in transport table "OWN_COLLECTION" 089ms
And Set advice window in schedule 2s 528ms
And Fill advice form 16s 725ms
And Click advice save button and wait for advice form to disappear 30s 713ms
And Go to "TRANSPORT_TABLE" 222ms
Then Check advice data in SK API database "OWN_COLLECTION" 107ms
After Hooks.deleteTransportAfterTest() 118ms
After Hooks.cleanUserDetailsAfterTest() 302ms
@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" 1s 897ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 330ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 321ms
When Click button advice in transport table "CONTAINER" 094ms
And Set advice window in schedule 2s 591ms
And Fill advice form 16s 832ms
And Click advice save button and wait for advice form to disappear 30s 746ms
And Go to "TRANSPORT_TABLE" 173ms
Then Check advice data in SK API database "CONTAINER" 112ms
After Hooks.deleteTransportAfterTest() 113ms
After Hooks.cleanUserDetailsAfterTest() 276ms
@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" 1s 879ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 351ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1s 153ms
When Click button advice in transport table "TRANSPORT_ORDER" 103ms
And Set advice window in schedule 2s 557ms
And Fill advice form 16s 699ms
And Click advice save button and wait for advice form to disappear 30s 708ms
And Go to "TRANSPORT_TABLE" 244ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 038ms
After Hooks.deleteTransportAfterTest() 126ms
After Hooks.cleanUserDetailsAfterTest() 275ms
@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" 1s 739ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 491ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 042ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 803ms
When Click button advice in transport table "TRANSPORT_ORDER" 098ms
And Set advice window in schedule 2s 586ms
And Fill advice form 16s 762ms
And Click advice save button and wait for advice form to disappear 30s 736ms
And Go to "TRANSPORT_TABLE" 193ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 041ms
After Hooks.deleteTransportAfterTest() 096ms
After Hooks.cleanUserDetailsAfterTest() 324ms
@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-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 973ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 259ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 926ms
When Click button advice in transport table "TRANSPORT_ORDER" 086ms
And Set advice window in schedule 2s 574ms
And Fill advice form 16s 770ms
And Click advice save button and wait for advice form to disappear 30s 707ms
And Go to "TRANSPORT_TABLE" 188ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 115ms
After Hooks.deleteTransportAfterTest() 115ms
After Hooks.cleanUserDetailsAfterTest() 219ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 825ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 323ms
When Click button advice in transport table "CONTAINER" 096ms
And Set advice window in schedule in the past 2s 536ms
And Fill advice form 16s 802ms
And Click advice save button to check error message 099ms
Then Check if possible advice alert is displayed 022ms
After Hooks.deleteTransportAfterTest() 068ms
@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" 1s 212ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 036ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 391ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 50s 014ms
And Go to "TRANSPORT_TABLE" 217ms
When Go to transport details "OWN_COLLECTION" 2s 470ms
And Expand advice panel 091ms
And Edit advice in transport details 16s 068ms
And Fill arrival date field 2s 306ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 133ms
Then Check advice data in database after edition "OWN_COLLECTION" 034ms
After Hooks.deleteTransportAfterTest() 119ms
@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" 1s 200ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "" 005ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 037ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 315ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 50s 076ms
And Go to "TRANSPORT_TABLE" 175ms
When Go to transport details "CONTAINER" 2s 505ms
And Expand advice panel 103ms
And Edit advice in transport details 16s 086ms
And Fill arrival date field 2s 305ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 109ms
Then Check advice data in database after edition "CONTAINER" 031ms
After Hooks.deleteTransportAfterTest() 103ms
@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" 1s 223ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 167ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 50s 093ms
And Go to "TRANSPORT_TABLE" 221ms
When Go to transport details "TRANSPORT_ORDER" 2s 446ms
And Expand advice panel 099ms
And Edit advice in transport details 16s 081ms
And Fill arrival date field 2s 283ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 113ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 033ms
After Hooks.deleteTransportAfterTest() 116ms