Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.159	16 wrz 2021, 07:01

	Steps	Scenarios	Features
@rollbackSettings	162	1	1	0	0	164	18	1	19	8m 11s 284ms	Failed

View Feature Public Api - Statuses confirmation

Scenario Outline Check if it is not possible to confirm status with incorrect status data by Public API [A-8210]

Hooks

Before Hooks.showScenarioName(Scenario) 037ms

Steps

Given Set token of apiUsername "super-admin-piast" 1s 060ms

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

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 17s 286ms

And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 5s 626ms

And Confirm status "ADVICE" by Public API "v1" and expect "422" 768ms

Then Check if response message contains "Nie można potwierdzić statusu ADVICE. Status ten został już potwierdzony wcześniej." in "errors" on status confirmation 011ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 310ms

After Hooks.rollbackSettings() 186ms

View Feature Public Api - Statuses confirmation

@deleteTransportAfterTest @rollbackSettings @TmsLink=A-8210

Scenario Outline Check if it is not possible to confirm status with incorrect status data by Public API [A-8210]

Hooks

Before Hooks.showScenarioName(Scenario) 007ms

Steps

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

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

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 15s 985ms

And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 4s 061ms

And Confirm status "ORDER_CREATION" by Public API "v1" and expect "422" 239ms

Then Check if response message contains "Nie można potwierdzić statusu ORDER_CREATION. Status ten został już potwierdzony wcześniej." in "errors" on status confirmation 008ms

Hooks

After Hooks.deleteTransportAfterTest() 997ms

After Hooks.rollbackSettings() 126ms

View Feature Public Api - Statuses confirmation

@deleteTransportAfterTest @rollbackSettings @TmsLink=A-8210

Scenario Outline Check if it is not possible to confirm status with incorrect status data by Public API [A-8210]

Hooks

Before Hooks.showScenarioName(Scenario) 004ms

Steps

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

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

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 16s 022ms

And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 3s 876ms

And Confirm status "BAD_STATUS_NAME" by Public API "v1" and expect "422" 267ms

Then Check if response message contains "Nie można potwierdzić statusu. Nie znaleziono wybranego statusu." in "errors" on status confirmation 008ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 017ms

After Hooks.rollbackSettings() 131ms

View Feature Public Api - Statuses confirmation

@deleteTransportAfterTest @rollbackSettings @TmsLink=A-8210

Scenario Outline Check if it is not possible to confirm status with incorrect status data by Public API [A-8210]

Hooks

Before Hooks.showScenarioName(Scenario) 005ms

Steps

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

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

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP" with "super-admin-piast" 160ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 15s 972ms

And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 4s 117ms

And Confirm status "ARRIVAL" by Public API "v1" and expect "404" 130ms

Then Check if response message contains "Nie znaleziono transportu o podanym identyfikatorze" in "text" on status confirmation 010ms

Hooks

After Hooks.deleteTransportAfterTest() 985ms

After Hooks.rollbackSettings() 147ms

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

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

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

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

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

Then Login as "super-admin-piast" 6s 848ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 660ms

After Hooks.rollbackSettings() 138ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 664ms

After Hooks.rollbackSettings() 145ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 661ms

After Hooks.rollbackSettings() 099ms

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

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

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

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 850ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 658ms

After Hooks.rollbackSettings() 131ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 601ms

After Hooks.rollbackSettings() 115ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 624ms

After Hooks.rollbackSettings() 122ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 682ms

After Hooks.rollbackSettings() 128ms

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) 001ms

Steps

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

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

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

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

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

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

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

Hooks

After Hooks.deleteApiTransportsAfterTest() 1s 238ms

After Hooks.rollbackSettings() 097ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 638ms

After Hooks.rollbackSettings() 141ms

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

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

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

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

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

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

And Show all transport types 1s 173ms

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

And Set advice window in schedule 3s 709ms

And Fill advice form 13s 583ms

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

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

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

And Go to "TRANSPORT_TABLE" 529ms

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

And Expand advice panel 656ms

Then Check are transport values equals 2s 410ms

Hooks

After Hooks.deleteTransportAfterApiTest() 918ms

After Hooks.rollbackSettings() 140ms

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 497ms

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

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/temp/buildTmp/.com.google.Chrome.iZv8El}, 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: 2f6929344068bebcb852b82e76cd0251
	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:89)
	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 538ms

After Hooks.rollbackAllCustomFieldsSettings() 347ms

After Hooks.rollbackSettings() 109ms

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

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

And If user is login then logout 236ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 474ms

And Go to "EXPIRED_TAB" invitation status tab 254ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 130ms

After Hooks.rollbackSettings() 135ms

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

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

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

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

When Login as "swisskrono-admin" 8s 039ms

And Go to "WAREHOUSE_TAB" 857ms

Then Check if dedicated window is deleted from schedule 1m 18s 475ms

Hooks

After Hooks.rollbackSettings() 195ms

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

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

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

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

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

And Go to "WAREHOUSE_TAB" 999ms

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

And Wait "60" seconds 1m

And Verify that transport window is grey 080ms

And Verify that transport is in archive 7s 856ms

Then Restore transport from archive 2s 659ms

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

Hooks

After Hooks.deleteTransportAfterTest() 824ms

After Hooks.rollbackSettings() 116ms

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 371ms

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

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

And Go to "TRANSPORT_TABLE" 350ms

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

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

And Wait until transport disappear from transport table 40s 568ms

Then Go to "ARCHIVE_TAB" 519ms

And Show "OWN_COLLECTION" 165ms

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

Hooks

After Hooks.deleteTransportAfterTest() 745ms

After Hooks.rollbackAllCustomFieldsSettings() 578ms

After Hooks.rollbackSettings() 168ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackSettings	162	1	1	0	0	164	18	1	19	8m 11s 284ms	Failed

Tag Report