Project Number Date
ApolloFullRunnerReport 2021.AT1.56 11 sie 2021, 05:39

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 25s 030ms 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 124ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 372ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 036ms
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 3s 306ms
When Click button advice in transport table "CONTAINER" 096ms
And Set advice window in schedule 2s 577ms
And Fill advice form 16s 626ms
And Click advice save button and wait for advice form to disappear 30s 695ms
And Go to "TRANSPORT_TABLE" 220ms
And Go to transport details "CONTAINER" 2s 512ms
Then Check are advice values equals 4s 342ms
After Hooks.deleteTransportAfterTest() 102ms
After Hooks.cleanUserDetailsAfterTest() 264ms
@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 879ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 352ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 040ms
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 "OWN_COLLECTION" created in transport table and set transport id 3s 377ms
When Click button advice in transport table "OWN_COLLECTION" 090ms
And Set advice window in schedule 2s 532ms
And Fill advice form 16s 742ms
And Click advice save button and wait for advice form to disappear 30s 739ms
And Go to "TRANSPORT_TABLE" 178ms
And Go to transport details "OWN_COLLECTION" 2s 457ms
Then Check are advice values equals 4s 344ms
After Hooks.deleteTransportAfterTest() 105ms
After Hooks.cleanUserDetailsAfterTest() 275ms
@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 939ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 329ms
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" 033ms
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" 083ms
And Set advice window in schedule 2s 544ms
And Fill advice form 16s 645ms
And Click advice save button and wait for advice form to disappear 30s 690ms
And Go to "TRANSPORT_TABLE" 260ms
And Go to transport details "TRANSPORT_ORDER" 2s 448ms
Then Check are advice values equals 4s 348ms
After Hooks.deleteTransportAfterTest() 106ms
After Hooks.cleanUserDetailsAfterTest() 274ms
@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 079ms
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" 037ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
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 3s 842ms
When Click button advice in transport table "TRANSPORT_ORDER" 093ms
And Set advice window in schedule 2s 559ms
And Fill advice form 16s 668ms
And Click advice save button and wait for advice form to disappear 30s 703ms
And Go to "TRANSPORT_TABLE" 236ms
And Go to transport details "TRANSPORT_ORDER" 2s 467ms
Then Check are advice values equals 4s 329ms
After Hooks.deleteTransportAfterTest() 139ms
After Hooks.cleanUserDetailsAfterTest() 403ms
@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 843ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 235ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms
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 924ms
When Click button advice in transport table "TRANSPORT_ORDER" 094ms
And Set advice window in schedule 30s 076ms
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.FuIOjL}, 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: f310b3d69c7adcb9a73d5f8efc7381a2
*** 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.deleteTransportAfterTest() 097ms
After Hooks.cleanUserDetailsAfterTest() 233ms
@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 864ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 348ms
And Get inputs from database "CREATE_OWN_COLLECTION" "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 "OWN_COLLECTION" created in transport table and set transport id 3s 362ms
When Click button advice in transport table "OWN_COLLECTION" 081ms
And Set advice window in schedule 2s 558ms
And Fill advice form 16s 663ms
And Click advice save button and wait for advice form to disappear 30s 668ms
And Go to "TRANSPORT_TABLE" 194ms
Then Check advice data in SK API database "OWN_COLLECTION" 144ms
After Hooks.deleteTransportAfterTest() 128ms
After Hooks.cleanUserDetailsAfterTest() 284ms
@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 850ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 338ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 004ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 347ms
When Click button advice in transport table "CONTAINER" 078ms
And Set advice window in schedule 2s 545ms
And Fill advice form 16s 752ms
And Click advice save button and wait for advice form to disappear 30s 725ms
And Go to "TRANSPORT_TABLE" 175ms
Then Check advice data in SK API database "CONTAINER" 091ms
After Hooks.deleteTransportAfterTest() 115ms
After Hooks.cleanUserDetailsAfterTest() 287ms
@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 861ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 349ms
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" 033ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 794ms
When Click button advice in transport table "TRANSPORT_ORDER" 094ms
And Set advice window in schedule 2s 574ms
And Fill advice form 16s 791ms
And Click advice save button and wait for advice form to disappear 30s 703ms
And Go to "TRANSPORT_TABLE" 239ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 034ms
After Hooks.deleteTransportAfterTest() 095ms
After Hooks.cleanUserDetailsAfterTest() 297ms
@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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 723ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 466ms
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 2s 860ms
When Click button advice in transport table "TRANSPORT_ORDER" 103ms
And Set advice window in schedule 2s 511ms
And Fill advice form 16s 687ms
And Click advice save button and wait for advice form to disappear 30s 751ms
And Go to "TRANSPORT_TABLE" 250ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 033ms
After Hooks.deleteTransportAfterTest() 093ms
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) 001ms
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 005ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 263ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 5s 891ms
When Click button advice in transport table "TRANSPORT_ORDER" 088ms
And Set advice window in schedule 2s 555ms
And Fill advice form 16s 693ms
And Click advice save button and wait for advice form to disappear 30s 749ms
And Go to "TRANSPORT_TABLE" 174ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 091ms
After Hooks.deleteTransportAfterTest() 106ms
After Hooks.cleanUserDetailsAfterTest() 254ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 830ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 005ms
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 312ms
When Click button advice in transport table "CONTAINER" 099ms
And Set advice window in schedule in the past 2s 589ms
And Fill advice form 16s 657ms
And Click advice save button to check error message 084ms
Then Check if possible advice alert is displayed 022ms
After Hooks.deleteTransportAfterTest() 079ms
@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 227ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 034ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 390ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 50s 153ms
And Go to "TRANSPORT_TABLE" 181ms
When Go to transport details "OWN_COLLECTION" 2s 436ms
And Expand advice panel 076ms
And Edit advice in transport details 16s 088ms
And Fill arrival date field 2s 272ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 048ms
Then Check advice data in database after edition "OWN_COLLECTION" 028ms
After Hooks.deleteTransportAfterTest() 099ms
@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 259ms
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 "EDIT_ADVICE" "super-admin-skz" 034ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 334ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 50s 031ms
And Go to "TRANSPORT_TABLE" 174ms
When Go to transport details "CONTAINER" 2s 518ms
And Expand advice panel 094ms
And Edit advice in transport details 16s 093ms
And Fill arrival date field 2s 300ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 102ms
Then Check advice data in database after edition "CONTAINER" 033ms
After Hooks.deleteTransportAfterTest() 136ms
@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 489ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 038ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 153ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 50s 126ms
And Go to "TRANSPORT_TABLE" 219ms
When Go to transport details "TRANSPORT_ORDER" 2s 430ms
And Expand advice panel 092ms
And Edit advice in transport details 16s 118ms
And Fill arrival date field 2s 279ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 101ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 034ms
After Hooks.deleteTransportAfterTest() 142ms