Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.154	11 wrz 2021, 06:36

	Steps	Scenarios	Features
@rollbackSettings	134	1	1	0	0	136	14	1	15	6m 10s 758ms	Failed

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 236ms

And Set token of apiUsername "super-admin-piast" 233ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 224ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 277ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 769ms

Then Login as "super-admin-piast" 7s 179ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 408ms

Hooks

After Hooks.deleteTransportAfterApiTest() 672ms

After Hooks.rollbackSettings() 199ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 239ms

And Set token of apiUsername "super-admin-piast" 254ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 159ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 764ms

Then Login as "super-admin-piast" 2s 471ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 399ms

Hooks

After Hooks.deleteTransportAfterApiTest() 675ms

After Hooks.rollbackSettings() 148ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 232ms

And Set token of apiUsername "super-admin-piast" 239ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 160ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 119ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 757ms

Then Login as "super-admin-piast" 2s 600ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 328ms

Hooks

After Hooks.deleteTransportAfterApiTest() 627ms

After Hooks.rollbackSettings() 102ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 255ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 143ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 167ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 247ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 761ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 718ms

After Hooks.rollbackSettings() 152ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 246ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 134ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 148ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 256ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 699ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 860ms

Then Check if response status code equals "422" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 627ms

After Hooks.rollbackSettings() 129ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Set token of apiUsername "super-admin-piast" 224ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 134ms

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" 250ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 701ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 343ms

Then Check if response status code equals "404" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 684ms

After Hooks.rollbackSettings() 140ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Set token of apiUsername "super-admin-piast" 246ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 161ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 268ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 705ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 035ms

Then Check if response status code equals "401" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 639ms

After Hooks.rollbackSettings() 124ms

View Feature API Transport

@deleteApiTransportsAfterTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api with non unique erpIdentifier [A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 891ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 153ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 133ms

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 706ms

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 620ms

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" 341ms

Then Check if response status code equals "422" 000ms

Hooks

After Hooks.deleteApiTransportsAfterTest() 1s 311ms

After Hooks.rollbackSettings() 086ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if custom fields map is correct after creating a transport by Public API [A-7508]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 249ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 122ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 162ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 249ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 658ms

And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 276ms

Hooks

After Hooks.deleteTransportAfterApiTest() 595ms

After Hooks.rollbackSettings() 142ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it possible to edit transport by API [A-4167]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Set token of apiUsername "super-admin-piast" 243ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 135ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 157ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 330ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 712ms

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 242ms

And Show all transport types 1s 184ms

And Click button advice in transport table "DELIVERY" 255ms

And Set advice window in schedule 3s 708ms

And Fill advice form 13s 342ms

And Click advice save button and wait for advice form to disappear 33s 801ms

When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 795ms

And Check if response status code equals "200" 000ms

And Go to "TRANSPORT_TABLE" 474ms

And Go to transport details "DELIVERY" 2s 997ms

And Expand advice panel 542ms

Then Check are transport values equals 2s 438ms

Hooks

After Hooks.deleteTransportAfterApiTest() 889ms

After Hooks.rollbackSettings() 143ms

View Feature Filters

@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

Scenario Outline Check if sorting by "Finished" status is working correctly [A-7517]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 232ms

And Get custom field settings for "DELIVERY" transport type and "neuca" company 118ms

And Mark custom fields as not obligatory 007ms

And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 132ms

And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 129ms

When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 062ms

Then Login as "neuca-admin" 2s 374ms

And Go to "TRANSPORT_TABLE" 510ms

And Confirm statuses until reach "process-ended" 3s 988ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=93.0.4577.63)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.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=93.0.4577.63 (ff5c0da2ec0adeaed5550e6c7e98417dac77d98a-refs/branch-heads/4577@{#1135}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.jmHEYW}, 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=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 71dd6aa921b779f6ffe9792924bce038
	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.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.getAttribute(RemoteWebElement.java:128)
	at Utils.StatusUtil.waitUntilAttributeOfWebElementChangeValue(StatusUtil.java:38)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:312)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:299)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:88)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Filters/Filter.feature:170)

Then Check if sorting by 'Finished' status is working correctly 000ms

Hooks

After Hooks.deleteTransportsAfterTest() 4s 478ms

After Hooks.rollbackAllCustomFieldsSettings() 304ms

After Hooks.rollbackSettings() 110ms

View Feature Invitation

@rollbackSettings @deleteInvitationAfterTest

Scenario Outline Check if expired invitation is visible in expired tab

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 231ms

And Delete invitations with email "automaty31415@test.pl" 093ms

And If user is login then logout 235ms

Given Set token of apiUsername "super-admin-piast" 251ms

And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 141ms

Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 192ms

And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 353ms

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 772ms

Then Go to "INVITATIONS_TAB" 470ms

And Go to "EXPIRED_TAB" invitation status tab 260ms

Then Invitation is displayed on list "automaty31415@test.pl" 415ms

Hooks

After Hooks.deleteInvitationAfterTest() 151ms

After Hooks.rollbackSettings() 123ms

View Feature DedicatedWindow

@rollbackSettings

Scenario Outline Check if dedicated window is automatically deleted from schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 217ms

And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 138ms

And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 284ms

And Prepare setting for automatic time window delete with "super-admin-skz" 221ms

When Login as "swisskrono-admin" 7s 805ms

And Go to "WAREHOUSE_TAB" 940ms

Then Check if dedicated window is deleted from schedule 51s 353ms

Hooks

After Hooks.rollbackSettings() 194ms

View Feature Move transport to archive

@rollbackSettings @deleteTransportAfterTest

Scenario Outline Check if delayed transport is moved to archived and can be restored

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 7s 098ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 014ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 133ms

And Set proper delay time to move order to archive after task timeout 144ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 952ms

And Go to "WAREHOUSE_TAB" 927ms

And Change warehouse in schedule to: "Katowice" 1s 245ms

And Wait "60" seconds 1m

And Verify that transport window is grey 079ms

And Verify that transport is in archive 7s 185ms

Then Restore transport from archive 2s 840ms

And Verify that transport has been successfully restored 1s 729ms

Hooks

After Hooks.deleteTransportAfterTest() 783ms

After Hooks.rollbackSettings() 114ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

Scenario Outline Check if confirming transport status removed it to the archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-dayco" 218ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 120ms

And Mark custom fields as not obligatory 005ms

And Login as "dayco-admin" 2s 248ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 054ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 123ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 189ms

When Go to "TRANSPORT_TABLE" 405ms

And Click button advice in transport table "OWN_COLLECTION" 1s 312ms

And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 499ms

And Go to "TRANSPORT_TABLE" 397ms

And Find transport in table with status "planned-magazyn-tychy" 3s 719ms

And Confirm statuses until reach "process-ended" 16s 643ms

And Wait until transport disappear from transport table 37s 425ms

Then Go to "ARCHIVE_TAB" 547ms

And Show "OWN_COLLECTION" 167ms

And Verify that created transport is "true" in transport table 15s 107ms

Hooks

After Hooks.deleteTransportAfterTest() 738ms

After Hooks.rollbackAllCustomFieldsSettings() 520ms

After Hooks.rollbackSettings() 125ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackSettings	134	1	1	0	0	136	14	1	15	6m 10s 758ms	Failed

Tag Report