Project Number Date
ApolloFullRunnerReport apollo-test-2.71 17 sie 2021, 09:11

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 475ms 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 632ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 494ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
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 944ms
When Click button advice in transport table "CONTAINER" 226ms
And Set advice window in schedule 3s 335ms
And Fill advice form 20s 396ms
And Click advice save button and wait for advice form to disappear 33s 248ms
And Go to "TRANSPORT_TABLE" 494ms
And Go to transport details "CONTAINER" 2s 930ms
Then Check are advice values equals 5s 001ms
After Hooks.deleteTransportAfterTest() 846ms
After Hooks.cleanUserDetailsAfterTest() 2s 292ms
@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 615ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 407ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms
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 "OWN_COLLECTION" created in transport table and set transport id 7s 170ms
When Click button advice in transport table "OWN_COLLECTION" 226ms
And Set advice window in schedule 3s 378ms
And Fill advice form 20s 344ms
And Click advice save button and wait for advice form to disappear 33s 244ms
And Go to "TRANSPORT_TABLE" 481ms
And Go to transport details "OWN_COLLECTION" 2s 878ms
Then Check are advice values equals 5s 007ms
After Hooks.deleteTransportAfterTest() 777ms
After Hooks.cleanUserDetailsAfterTest() 2s 145ms
@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 350ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 528ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "" 024ms
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 153ms
When Click button advice in transport table "TRANSPORT_ORDER" 243ms
And Set advice window in schedule 3s 357ms
And Fill advice form 20s 551ms
And Click advice save button and wait for advice form to disappear 33s 291ms
And Go to "TRANSPORT_TABLE" 505ms
And Go to transport details "TRANSPORT_ORDER" 2s 977ms
Then Check are advice values equals 4s 895ms
After Hooks.deleteTransportAfterTest() 806ms
After Hooks.cleanUserDetailsAfterTest() 2s 299ms
@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 700ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 570ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
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 717ms
When Click button advice in transport table "TRANSPORT_ORDER" 252ms
And Set advice window in schedule 3s 528ms
And Fill advice form 20s 469ms
And Click advice save button and wait for advice form to disappear 33s 201ms
And Go to "TRANSPORT_TABLE" 489ms
And Go to transport details "TRANSPORT_ORDER" 2s 880ms
Then Check are advice values equals 5s 023ms
After Hooks.deleteTransportAfterTest() 795ms
After Hooks.cleanUserDetailsAfterTest() 2s 731ms
@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 589ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 744ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 7s 623ms
When Click button advice in transport table "TRANSPORT_ORDER" 240ms
And Set advice window in schedule 30s 183ms
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.R7BaJQ}, 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: 54f7e2e06dcf601f80c66fa6cd4b793a
*** 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.deleteTransportAfterTest() 552ms
After Hooks.cleanUserDetailsAfterTest() 1s 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) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 557ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 360ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms
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 171ms
When Click button advice in transport table "OWN_COLLECTION" 225ms
And Set advice window in schedule 3s 410ms
And Fill advice form 20s 412ms
And Click advice save button and wait for advice form to disappear 33s 290ms
And Go to "TRANSPORT_TABLE" 450ms
Then Check advice data in SK API database "OWN_COLLECTION" 445ms
After Hooks.deleteTransportAfterTest() 820ms
After Hooks.cleanUserDetailsAfterTest() 2s 161ms
@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-admin" and set token of apiUsername "super-admin-skz" 7s 439ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 548ms
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 6s 985ms
When Click button advice in transport table "CONTAINER" 194ms
And Set advice window in schedule 3s 498ms
And Fill advice form 20s 433ms
And Click advice save button and wait for advice form to disappear 33s 294ms
And Go to "TRANSPORT_TABLE" 490ms
Then Check advice data in SK API database "CONTAINER" 202ms
After Hooks.deleteTransportAfterTest() 871ms
After Hooks.cleanUserDetailsAfterTest() 2s 241ms
@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 688ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 490ms
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 4s 182ms
When Click button advice in transport table "TRANSPORT_ORDER" 223ms
And Set advice window in schedule 3s 405ms
And Fill advice form 20s 547ms
And Click advice save button and wait for advice form to disappear 33s 270ms
And Go to "TRANSPORT_TABLE" 465ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms
After Hooks.deleteTransportAfterTest() 838ms
After Hooks.cleanUserDetailsAfterTest() 2s 174ms
@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 434ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 307ms
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" 016ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 099ms
When Click button advice in transport table "TRANSPORT_ORDER" 214ms
And Set advice window in schedule 3s 365ms
And Fill advice form 20s 465ms
And Click advice save button and wait for advice form to disappear 33s 817ms
And Go to "TRANSPORT_TABLE" 496ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms
After Hooks.deleteTransportAfterTest() 823ms
After Hooks.cleanUserDetailsAfterTest() 2s 942ms
@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 673ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 867ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 028ms
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 548ms
When Click button advice in transport table "TRANSPORT_ORDER" 224ms
And Set advice window in schedule 3s 414ms
And Fill advice form 20s 503ms
And Click advice save button and wait for advice form to disappear 33s 876ms
And Go to "TRANSPORT_TABLE" 440ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 271ms
After Hooks.deleteTransportAfterTest() 856ms
After Hooks.cleanUserDetailsAfterTest() 1s 640ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 531ms
And Get inputs from database "CREATE_CONTAINER" "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 "CONTAINER" created in transport table and set transport id 6s 975ms
When Click button advice in transport table "CONTAINER" 194ms
And Set advice window in schedule in the past 3s 373ms
And Fill advice form 20s 379ms
And Click advice save button to check error message 181ms
Then Check if possible advice alert is displayed 065ms
After Hooks.deleteTransportAfterTest() 565ms
@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 852ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 023ms
And Add transport by SKApi in "MGW" assigned to "" 025ms
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 132ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 251ms
And Go to "TRANSPORT_TABLE" 469ms
When Go to transport details "OWN_COLLECTION" 2s 929ms
And Expand advice panel 266ms
And Edit advice in transport details 18s 736ms
And Fill arrival date field 2s 677ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 234ms
Then Check advice data in database after edition "OWN_COLLECTION" 104ms
After Hooks.deleteTransportAfterTest() 817ms
@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 647ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 015ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 970ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 373ms
And Go to "TRANSPORT_TABLE" 457ms
When Go to transport details "CONTAINER" 2s 940ms
And Expand advice panel 295ms
And Edit advice in transport details 18s 945ms
And Fill arrival date field 2s 650ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 231ms
Then Check advice data in database after edition "CONTAINER" 104ms
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 681ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 017ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 015ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 636ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 57s 297ms
And Go to "TRANSPORT_TABLE" 487ms
When Go to transport details "TRANSPORT_ORDER" 2s 921ms
And Expand advice panel 239ms
And Edit advice in transport details 19s 037ms
And Fill arrival date field 2s 636ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 188ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 107ms
After Hooks.deleteTransportAfterTest() 812ms