Project Number Date
ApolloFullRunnerReport apollo-test-2.113 11 sie 2021, 05:52

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 668ms 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 629ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 390ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 015ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 934ms
When Click button advice in transport table "CONTAINER" 213ms
And Set advice window in schedule 3s 542ms
And Fill advice form 20s 286ms
And Click advice save button and wait for advice form to disappear 33s 389ms
And Go to "TRANSPORT_TABLE" 438ms
And Go to transport details "CONTAINER" 3s
Then Check are advice values equals 4s 897ms
After Hooks.cleanUserDetailsAfterTest() 2s 249ms
After Hooks.deleteTransportAfterTest() 775ms
@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 580ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 366ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 017ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 014ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 239ms
When Click button advice in transport table "OWN_COLLECTION" 279ms
And Set advice window in schedule 3s 364ms
And Fill advice form 20s 077ms
And Click advice save button and wait for advice form to disappear 33s 277ms
And Go to "TRANSPORT_TABLE" 514ms
And Go to transport details "OWN_COLLECTION" 2s 944ms
Then Check are advice values equals 4s 967ms
After Hooks.cleanUserDetailsAfterTest() 2s 116ms
After Hooks.deleteTransportAfterTest() 791ms
@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 446ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 359ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 025ms
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 4s 327ms
When Click button advice in transport table "TRANSPORT_ORDER" 215ms
And Set advice window in schedule 3s 379ms
And Fill advice form 20s 435ms
And Click advice save button and wait for advice form to disappear 33s 269ms
And Go to "TRANSPORT_TABLE" 496ms
And Go to transport details "TRANSPORT_ORDER" 2s 931ms
Then Check are advice values equals 4s 899ms
After Hooks.cleanUserDetailsAfterTest() 2s 357ms
After Hooks.deleteTransportAfterTest() 775ms
@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 871ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 433ms
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" 016ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 986ms
When Click button advice in transport table "TRANSPORT_ORDER" 223ms
And Set advice window in schedule 3s 429ms
And Fill advice form 20s 062ms
And Click advice save button and wait for advice form to disappear 33s 774ms
And Go to "TRANSPORT_TABLE" 535ms
And Go to transport details "TRANSPORT_ORDER" 2s 913ms
Then Check are advice values equals 4s 932ms
After Hooks.cleanUserDetailsAfterTest() 2s 745ms
After Hooks.deleteTransportAfterTest() 820ms
@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 451ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 762ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 022ms
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 584ms
When Click button advice in transport table "TRANSPORT_ORDER" 229ms
And Set advice window in schedule 30s 120ms
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.kmn80O}, 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: 4c39e7bdb63d8f3c16f088da08e907bc
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.GeneratedConstructorAccessor215.newInstance(Unknown Source)
	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 743ms
After Hooks.deleteTransportAfterTest() 549ms
@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 622ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 394ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 025ms
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 "OWN_COLLECTION" created in transport table and set transport id 7s 143ms
When Click button advice in transport table "OWN_COLLECTION" 241ms
And Set advice window in schedule 3s 435ms
And Fill advice form 20s 615ms
And Click advice save button and wait for advice form to disappear 33s 304ms
And Go to "TRANSPORT_TABLE" 492ms
Then Check advice data in SK API database "OWN_COLLECTION" 462ms
After Hooks.cleanUserDetailsAfterTest() 2s 127ms
After Hooks.deleteTransportAfterTest() 800ms
@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 584ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 364ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 024ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 020ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 891ms
When Click button advice in transport table "CONTAINER" 232ms
And Set advice window in schedule 3s 405ms
And Fill advice form 20s 467ms
And Click advice save button and wait for advice form to disappear 33s 335ms
And Go to "TRANSPORT_TABLE" 469ms
Then Check advice data in SK API database "CONTAINER" 240ms
After Hooks.cleanUserDetailsAfterTest() 2s 298ms
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) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 607ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 461ms
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" 015ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 212ms
When Click button advice in transport table "TRANSPORT_ORDER" 207ms
And Set advice window in schedule 3s 350ms
And Fill advice form 20s 665ms
And Click advice save button and wait for advice form to disappear 33s 400ms
And Go to "TRANSPORT_TABLE" 502ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 095ms
After Hooks.cleanUserDetailsAfterTest() 2s 115ms
After Hooks.deleteTransportAfterTest() 766ms
@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 513ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 497ms
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" 015ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 774ms
When Click button advice in transport table "TRANSPORT_ORDER" 211ms
And Set advice window in schedule 3s 380ms
And Fill advice form 20s 589ms
And Click advice save button and wait for advice form to disappear 33s 353ms
And Go to "TRANSPORT_TABLE" 490ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 097ms
After Hooks.cleanUserDetailsAfterTest() 3s 028ms
After Hooks.deleteTransportAfterTest() 803ms
@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 810ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 870ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 019ms
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 593ms
When Click button advice in transport table "TRANSPORT_ORDER" 257ms
And Set advice window in schedule 3s 507ms
And Fill advice form 20s 385ms
And Click advice save button and wait for advice form to disappear 33s 835ms
And Go to "TRANSPORT_TABLE" 464ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 260ms
After Hooks.cleanUserDetailsAfterTest() 1s 591ms
After Hooks.deleteTransportAfterTest() 776ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 444ms
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" 017ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 997ms
When Click button advice in transport table "CONTAINER" 277ms
And Set advice window in schedule in the past 3s 384ms
And Fill advice form 20s 436ms
And Click advice save button to check error message 175ms
Then Check if possible advice alert is displayed 065ms
After Hooks.deleteTransportAfterTest() 573ms
@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 726ms
And Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id 7s 164ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 253ms
And Go to "TRANSPORT_TABLE" 480ms
When Go to transport details "OWN_COLLECTION" 2s 944ms
And Expand advice panel 279ms
And Edit advice in transport details 18s 941ms
And Fill arrival date field 2s 614ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 209ms
Then Check advice data in database after edition "OWN_COLLECTION" 097ms
After Hooks.deleteTransportAfterTest() 920ms
@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 683ms
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 "EDIT_ADVICE" "super-admin-skz" 015ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 950ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 441ms
And Go to "TRANSPORT_TABLE" 447ms
When Go to transport details "CONTAINER" 2s 917ms
And Expand advice panel 276ms
And Edit advice in transport details 18s 848ms
And Fill arrival date field 2s 646ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 185ms
Then Check advice data in database after edition "CONTAINER" 103ms
After Hooks.deleteTransportAfterTest() 818ms
@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 693ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 026ms
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 7s 571ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 57s 425ms
And Go to "TRANSPORT_TABLE" 478ms
When Go to transport details "TRANSPORT_ORDER" 2s 870ms
And Expand advice panel 313ms
And Edit advice in transport details 19s 041ms
And Fill arrival date field 2s 617ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 204ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 113ms
After Hooks.deleteTransportAfterTest() 844ms