Project Number Date
ApolloFullRunnerReport apollo-test-2.114 12 sie 2021, 06:02

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 41s 412ms 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 532ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 460ms
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 "CREATE_ADVICE" "super-admin-skz" 016ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 928ms
When Click button advice in transport table "CONTAINER" 210ms
And Set advice window in schedule 3s 365ms
And Fill advice form 20s 406ms
And Click advice save button and wait for advice form to disappear 33s 253ms
And Go to "TRANSPORT_TABLE" 436ms
And Go to transport details "CONTAINER" 2s 982ms
Then Check are advice values equals 4s 967ms
After Hooks.cleanUserDetailsAfterTest() 2s 293ms
After Hooks.deleteTransportAfterTest() 803ms
@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) 002ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 827ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 399ms
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" 016ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 212ms
When Click button advice in transport table "OWN_COLLECTION" 225ms
And Set advice window in schedule 3s 414ms
And Fill advice form 20s 425ms
And Click advice save button and wait for advice form to disappear 33s 292ms
And Go to "TRANSPORT_TABLE" 490ms
And Go to transport details "OWN_COLLECTION" 2s 921ms
Then Check are advice values equals 4s 984ms
After Hooks.cleanUserDetailsAfterTest() 2s 109ms
After Hooks.deleteTransportAfterTest() 779ms
@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 507ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 341ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
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 374ms
When Click button advice in transport table "TRANSPORT_ORDER" 231ms
And Set advice window in schedule 3s 432ms
And Fill advice form 20s 568ms
And Click advice save button and wait for advice form to disappear 33s 347ms
And Go to "TRANSPORT_TABLE" 490ms
And Go to transport details "TRANSPORT_ORDER" 2s 868ms
Then Check are advice values equals 4s 983ms
After Hooks.cleanUserDetailsAfterTest() 2s 302ms
After Hooks.deleteTransportAfterTest() 778ms
@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 773ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 474ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 023ms
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 3s 845ms
When Click button advice in transport table "TRANSPORT_ORDER" 226ms
And Set advice window in schedule 3s 380ms
And Fill advice form 20s 749ms
And Click advice save button and wait for advice form to disappear 33s 841ms
And Go to "TRANSPORT_TABLE" 451ms
And Go to transport details "TRANSPORT_ORDER" 2s 838ms
Then Check are advice values equals 4s 977ms
After Hooks.cleanUserDetailsAfterTest() 2s 712ms
After Hooks.deleteTransportAfterTest() 809ms
@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 618ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 733ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 024ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 022ms
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 549ms
When Click button advice in transport table "TRANSPORT_ORDER" 205ms
And Set advice window in schedule 30s 085ms
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.LvIige}, 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: 9ebdc2f1001d94b48960ea9db301ccc5
*** 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 775ms
After Hooks.deleteTransportAfterTest() 604ms
@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 604ms
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" 024ms
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 199ms
When Click button advice in transport table "OWN_COLLECTION" 199ms
And Set advice window in schedule 3s 398ms
And Fill advice form 20s 514ms
And Click advice save button and wait for advice form to disappear 33s 268ms
And Go to "TRANSPORT_TABLE" 438ms
Then Check advice data in SK API database "OWN_COLLECTION" 408ms
After Hooks.cleanUserDetailsAfterTest() 2s 055ms
After Hooks.deleteTransportAfterTest() 826ms
@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 524ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 387ms
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" 018ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 899ms
When Click button advice in transport table "CONTAINER" 211ms
And Set advice window in schedule 3s 352ms
And Fill advice form 20s 489ms
And Click advice save button and wait for advice form to disappear 33s 334ms
And Go to "TRANSPORT_TABLE" 398ms
Then Check advice data in SK API database "CONTAINER" 218ms
After Hooks.cleanUserDetailsAfterTest() 2s 290ms
After Hooks.deleteTransportAfterTest() 787ms
@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 537ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 399ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 016ms
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 277ms
When Click button advice in transport table "TRANSPORT_ORDER" 218ms
And Set advice window in schedule 3s 399ms
And Fill advice form 20s 467ms
And Click advice save button and wait for advice form to disappear 33s 259ms
And Go to "TRANSPORT_TABLE" 490ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 087ms
After Hooks.cleanUserDetailsAfterTest() 2s 225ms
After Hooks.deleteTransportAfterTest() 799ms
@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 615ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 356ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 017ms
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 018ms
When Click button advice in transport table "TRANSPORT_ORDER" 234ms
And Set advice window in schedule 3s 378ms
And Fill advice form 20s 396ms
And Click advice save button and wait for advice form to disappear 33s 235ms
And Go to "TRANSPORT_TABLE" 504ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms
After Hooks.cleanUserDetailsAfterTest() 2s 974ms
After Hooks.deleteTransportAfterTest() 824ms
@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 632ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 839ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 017ms
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 563ms
When Click button advice in transport table "TRANSPORT_ORDER" 220ms
And Set advice window in schedule 3s 427ms
And Fill advice form 20s 318ms
And Click advice save button and wait for advice form to disappear 33s 816ms
And Go to "TRANSPORT_TABLE" 437ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 274ms
After Hooks.cleanUserDetailsAfterTest() 1s 687ms
After Hooks.deleteTransportAfterTest() 829ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 386ms
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" 017ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 996ms
When Click button advice in transport table "CONTAINER" 223ms
And Set advice window in schedule in the past 3s 383ms
And Fill advice form 20s 424ms
And Click advice save button to check error message 188ms
Then Check if possible advice alert is displayed 073ms
After Hooks.deleteTransportAfterTest() 580ms
@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 720ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 023ms
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 "OWN_COLLECTION" created in transport table and set transport id 7s 130ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 254ms
And Go to "TRANSPORT_TABLE" 454ms
When Go to transport details "OWN_COLLECTION" 2s 952ms
And Expand advice panel 264ms
And Edit advice in transport details 18s 863ms
And Fill arrival date field 2s 618ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 233ms
Then Check advice data in database after edition "OWN_COLLECTION" 096ms
After Hooks.deleteTransportAfterTest() 793ms
@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 760ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 025ms
And Add transport by SKApi in "MGW" assigned to "" 027ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 020ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 977ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 330ms
And Go to "TRANSPORT_TABLE" 466ms
When Go to transport details "CONTAINER" 2s 925ms
And Expand advice panel 306ms
And Edit advice in transport details 18s 877ms
And Fill arrival date field 2s 621ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 178ms
Then Check advice data in database after edition "CONTAINER" 096ms
After Hooks.deleteTransportAfterTest() 856ms
@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 657ms
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" 016ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 643ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 42s 551ms
And Go to "TRANSPORT_TABLE" 504ms
When Go to transport details "TRANSPORT_ORDER" 2s 916ms
And Expand advice panel 264ms
And Edit advice in transport details 18s 875ms
And Fill arrival date field 2s 625ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 268ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 099ms
After Hooks.deleteTransportAfterTest() 807ms