Project Number Date
ApolloFullRunnerReport apollo-test-2.119 15 sie 2021, 05:58

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 31s 693ms 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 610ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 461ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 022ms
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 987ms
When Click button advice in transport table "CONTAINER" 262ms
And Set advice window in schedule 3s 422ms
And Fill advice form 20s 673ms
And Click advice save button and wait for advice form to disappear 33s 283ms
And Go to "TRANSPORT_TABLE" 426ms
And Go to transport details "CONTAINER" 2s 894ms
Then Check are advice values equals 5s 010ms
After Hooks.cleanUserDetailsAfterTest() 2s 366ms
After Hooks.deleteTransportAfterTest() 812ms
@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 680ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 420ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 017ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 018ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 174ms
When Click button advice in transport table "OWN_COLLECTION" 215ms
And Set advice window in schedule 3s 386ms
And Fill advice form 20s 679ms
And Click advice save button and wait for advice form to disappear 33s 333ms
And Go to "TRANSPORT_TABLE" 444ms
And Go to transport details "OWN_COLLECTION" 2s 891ms
Then Check are advice values equals 4s 995ms
After Hooks.cleanUserDetailsAfterTest() 2s 132ms
After Hooks.deleteTransportAfterTest() 797ms
@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 578ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 351ms
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" 017ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 366ms
When Click button advice in transport table "TRANSPORT_ORDER" 224ms
And Set advice window in schedule 3s 399ms
And Fill advice form 20s 501ms
And Click advice save button and wait for advice form to disappear 33s 361ms
And Go to "TRANSPORT_TABLE" 475ms
And Go to transport details "TRANSPORT_ORDER" 2s 918ms
Then Check are advice values equals 4s 980ms
After Hooks.cleanUserDetailsAfterTest() 2s 283ms
After Hooks.deleteTransportAfterTest() 792ms
@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 651ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 390ms
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" 017ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 892ms
When Click button advice in transport table "TRANSPORT_ORDER" 240ms
And Set advice window in schedule 3s 393ms
And Fill advice form 20s 389ms
And Click advice save button and wait for advice form to disappear 33s 833ms
And Go to "TRANSPORT_TABLE" 497ms
And Go to transport details "TRANSPORT_ORDER" 2s 850ms
Then Check are advice values equals 5s 013ms
After Hooks.cleanUserDetailsAfterTest() 2s 711ms
After Hooks.deleteTransportAfterTest() 794ms
@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 673ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 826ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 019ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 021ms
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 887ms
When Click button advice in transport table "TRANSPORT_ORDER" 223ms
And Set advice window in schedule 30s 154ms
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.Uctaot}, 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: 59b464e42b904934710a44439613d6ac
*** 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() 531ms
@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 774ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 402ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 022ms
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 133ms
When Click button advice in transport table "OWN_COLLECTION" 223ms
And Set advice window in schedule 3s 365ms
And Fill advice form 20s 569ms
And Click advice save button and wait for advice form to disappear 33s 241ms
And Go to "TRANSPORT_TABLE" 462ms
Then Check advice data in SK API database "OWN_COLLECTION" 421ms
After Hooks.cleanUserDetailsAfterTest() 2s 139ms
After Hooks.deleteTransportAfterTest() 822ms
@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 523ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 392ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 022ms
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 3s 971ms
When Click button advice in transport table "CONTAINER" 227ms
And Set advice window in schedule 3s 449ms
And Fill advice form 20s 480ms
And Click advice save button and wait for advice form to disappear 33s 271ms
And Go to "TRANSPORT_TABLE" 471ms
Then Check advice data in SK API database "CONTAINER" 206ms
After Hooks.cleanUserDetailsAfterTest() 2s 316ms
After Hooks.deleteTransportAfterTest() 837ms
@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 546ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 439ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 023ms
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 4s 217ms
When Click button advice in transport table "TRANSPORT_ORDER" 214ms
And Set advice window in schedule 3s 381ms
And Fill advice form 20s 476ms
And Click advice save button and wait for advice form to disappear 18s 421ms
And Go to "TRANSPORT_TABLE" 493ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 097ms
After Hooks.cleanUserDetailsAfterTest() 2s 121ms
After Hooks.deleteTransportAfterTest() 805ms
@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 448ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 3s 261ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
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 062ms
When Click button advice in transport table "TRANSPORT_ORDER" 237ms
And Set advice window in schedule 3s 334ms
And Fill advice form 20s 471ms
And Click advice save button and wait for advice form to disappear 18s 388ms
And Go to "TRANSPORT_TABLE" 492ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 096ms
After Hooks.cleanUserDetailsAfterTest() 2s 941ms
After Hooks.deleteTransportAfterTest() 869ms
@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 825ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 1s 855ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 560ms
When Click button advice in transport table "TRANSPORT_ORDER" 218ms
And Set advice window in schedule 3s 383ms
And Fill advice form 20s 390ms
And Click advice save button and wait for advice form to disappear 33s 831ms
And Go to "TRANSPORT_TABLE" 460ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 273ms
After Hooks.cleanUserDetailsAfterTest() 1s 751ms
After Hooks.deleteTransportAfterTest() 788ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 591ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
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 942ms
When Click button advice in transport table "CONTAINER" 249ms
And Set advice window in schedule in the past 3s 364ms
And Fill advice form 20s 470ms
And Click advice save button to check error message 198ms
Then Check if possible advice alert is displayed 069ms
After Hooks.deleteTransportAfterTest() 589ms
@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 745ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 022ms
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 "OWN_COLLECTION" created in transport table and set transport id 7s 193ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 57s 336ms
And Go to "TRANSPORT_TABLE" 497ms
When Go to transport details "OWN_COLLECTION" 2s 972ms
And Expand advice panel 272ms
And Edit advice in transport details 18s 785ms
And Fill arrival date field 2s 722ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 248ms
Then Check advice data in database after edition "OWN_COLLECTION" 108ms
After Hooks.deleteTransportAfterTest() 890ms
@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 751ms
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" 019ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 961ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 57s 376ms
And Go to "TRANSPORT_TABLE" 468ms
When Go to transport details "CONTAINER" 2s 917ms
And Expand advice panel 288ms
And Edit advice in transport details 19s 011ms
And Fill arrival date field 2s 637ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 235ms
Then Check advice data in database after edition "CONTAINER" 111ms
After Hooks.deleteTransportAfterTest() 823ms
@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 770ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 019ms
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 "TRANSPORT_ORDER" created in transport table and set transport id 3s 632ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 57s 568ms
And Go to "TRANSPORT_TABLE" 468ms
When Go to transport details "TRANSPORT_ORDER" 2s 948ms
And Expand advice panel 251ms
And Edit advice in transport details 18s 925ms
And Fill arrival date field 2s 661ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 189ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 108ms
After Hooks.deleteTransportAfterTest() 863ms