Project Number Date
ApolloFullRunnerReport apollo-test-2.129 23 sie 2021, 05:13

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@rollbackSettings 129 2 5 0 0 136 13 2 15 6m 38s 499ms Failed
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 241ms
And Set token of apiUsername "super-admin-piast" 233ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 301ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 237ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 603ms
Then Login as "super-admin-piast" 8s 520ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 373ms
After Hooks.deleteTransportAfterApiTest() 560ms
After Hooks.rollbackSettings() 184ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 244ms
And Set token of apiUsername "super-admin-piast" 231ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 153ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 167ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 609ms
Then Login as "super-admin-piast" 2s 422ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 396ms
After Hooks.deleteTransportAfterApiTest() 661ms
After Hooks.rollbackSettings() 158ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 239ms
And Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 127ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 663ms
Then Login as "super-admin-piast" 2s 400ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 380ms
After Hooks.deleteTransportAfterApiTest() 645ms
After Hooks.rollbackSettings() 095ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 251ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 177ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 251ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 633ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 862ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 768ms
After Hooks.rollbackSettings() 129ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 246ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 143ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 163ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 246ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 591ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 872ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 637ms
After Hooks.rollbackSettings() 160ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 243ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 151ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 252ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 633ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 336ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 646ms
After Hooks.rollbackSettings() 125ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 249ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 156ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 262ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 643ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 033ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 636ms
After Hooks.rollbackSettings() 133ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 3s 012ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 134ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" with erp identifier "5345467712" 1s 621ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" with erp identifier "5345467712" 1s 584ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_WITH_FILLED_ERP_IDENTIFIER" as "super-admin-piast" for api version "v1" by identifier "5345467712" 324ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportsAfterTest() 000ms
After Hooks.rollbackSettings() 092ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 249ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 149ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 154ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 261ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 672ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 289ms
After Hooks.deleteTransportAfterApiTest() 638ms
After Hooks.rollbackSettings() 133ms
View Feature API Transport
Scenario Outline Check if it possible to edit transport by API [A-4167]
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Set token of apiUsername "super-admin-piast" 254ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 159ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 350ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 578ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 022ms
And Show all transport types 1s 183ms
And Click button advice in transport table "DELIVERY" 281ms
And Set advice window in schedule 3s 725ms
And Fill advice form 13s 339ms
And Click advice save button and wait for advice form to disappear 33s 855ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 1s 657ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 517ms
And Go to transport details "DELIVERY" 2s 906ms
And Expand advice panel 15s 112ms
org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@id='advice-panel']"}
  (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.8hDyVp}, 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: 06a06e739653df18588b7b7cabd64f20
*** Element info: {Using=xpath, value=//div[@id='advice-panel']}
	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.expandAdvicePanel(AdviceTransport.java:142)
	at ✽.Expand advice panel(file:Features/Api/Transport.feature:170)
Then Check are transport values equals 000ms
After Hooks.deleteTransportAfterApiTest() 537ms
After Hooks.rollbackSettings() 145ms
View Feature Filters
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 240ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 110ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 131ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 112ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 133ms
Then Login as "neuca-admin" 2s 330ms
And Go to "TRANSPORT_TABLE" 493ms
And Confirm statuses until reach "process-ended" 22s 416ms
Then Check if sorting by 'Finished' status is working correctly 325ms
After Hooks.deleteTransportsAfterTest() 4s 377ms
After Hooks.rollbackAllCustomFieldsSettings() 350ms
After Hooks.rollbackSettings() 102ms
View Feature Invitation
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 300ms
And Delete invitations with email "automaty31415@test.pl" 112ms
And If user is login then logout 592ms
Given Set token of apiUsername "super-admin-piast" 238ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 138ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 195ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 407ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 855ms
Then Go to "INVITATIONS_TAB" 528ms
And Go to "EXPIRED_TAB" invitation status tab 315ms
Then Invitation is displayed on list "automaty31415@test.pl" 466ms
After Hooks.deleteInvitationAfterTest() 164ms
After Hooks.rollbackSettings() 124ms
View Feature DedicatedWindow
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 239ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 127ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 311ms
And Prepare setting for automatic time window delete with "super-admin-skz" 216ms
When Login as "swisskrono-admin" 7s 771ms
And Go to "WAREHOUSE_TAB" 974ms
Then Check if dedicated window is deleted from schedule 1m 18s 197ms
After Hooks.rollbackSettings() 189ms
View Feature Move transport to archive
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 751ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 021ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 138ms
And Set proper delay time to move order to archive after task timeout 143ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 932ms
And Go to "WAREHOUSE_TAB" 996ms
And Change warehouse in schedule to: "Katowice" 1s 658ms
And Wait "60" seconds 1m
And Verify that transport window is grey 077ms
And Verify that transport is in archive 6s 899ms
Then Restore transport from archive 2s 646ms
And Verify that transport has been successfully restored 1s 816ms
After Hooks.deleteTransportAfterTest() 746ms
After Hooks.rollbackSettings() 123ms
View Feature Move transport to archive
Scenario Outline Check if confirming transport status removed it to the archive
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Set token of apiUsername "super-admin-dayco" 220ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 128ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 308ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 078ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 135ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 202ms
When Go to "TRANSPORT_TABLE" 363ms
And Click button advice in transport table "OWN_COLLECTION" 1s 318ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 531ms
And Go to "TRANSPORT_TABLE" 357ms
And Find transport in table with status "planned-magazyn-tychy" 3s 713ms
And Confirm statuses until reach "process-ended" 38s 300ms
java.lang.AssertionError: Wartość on-the-area-magazyn-tychy atrybutu data-status-name nie zmieniła się w webelemencie [[ChromeDriver: chrome on LINUX (06a06e739653df18588b7b7cabd64f20)] -> xpath: //td[contains(@data-status-name, 'planned-magazyn-tychy')]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.StatusUtil.waitUntilAttributeOfWebElementChangeValue(StatusUtil.java:43)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:310)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:297)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:88)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Transport/Archive.feature:49)
And Wait until transport disappear from transport table 000ms
Then Go to "ARCHIVE_TAB" 000ms
And Show "OWN_COLLECTION" 000ms
And Verify that created transport is "true" in transport table 000ms
After Hooks.deleteTransportAfterTest() 867ms
After Hooks.rollbackAllCustomFieldsSettings() 525ms
After Hooks.rollbackSettings() 122ms