Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.132	25 sie 2021, 05:54

	Steps	Scenarios	Features
@rollbackSettings	131	1	4	0	0	136	14	1	15	6m 19s 212ms	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) 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" 240ms

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

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

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

Then Login as "super-admin-piast" 5s 293ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 683ms

After Hooks.rollbackSettings() 186ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 658ms

After Hooks.rollbackSettings() 139ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 662ms

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

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

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

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

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 "none" for api version "v1" 1s 946ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 653ms

After Hooks.rollbackSettings() 146ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 619ms

After Hooks.rollbackSettings() 137ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 625ms

After Hooks.rollbackSettings() 135ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 683ms

After Hooks.rollbackSettings() 123ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteApiTransportsAfterTest() 1s 367ms

After Hooks.rollbackSettings() 101ms

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

Steps

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 574ms

After Hooks.rollbackSettings() 116ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 3s 081ms

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

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

And Show all transport types 1s 171ms

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

And Set advice window in schedule 4s 002ms

And Fill advice form 13s 465ms

And Click advice save button and wait for advice form to disappear 34s 014ms

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

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

And Go to "TRANSPORT_TABLE" 481ms

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

And Expand advice panel 694ms

Then Check are transport values equals 2s 409ms

Hooks

After Hooks.deleteTransportAfterApiTest() 920ms

After Hooks.rollbackSettings() 131ms

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 544ms

And Confirm statuses until reach "process-ended" 21s 400ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 4s 464ms

After Hooks.rollbackAllCustomFieldsSettings() 333ms

After Hooks.rollbackSettings() 106ms

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

And If user is login then logout 272ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 530ms

And Go to "EXPIRED_TAB" invitation status tab 280ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 147ms

After Hooks.rollbackSettings() 119ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 007ms

Then Check if dedicated window is deleted from schedule 1m 15s 323ms

Hooks

After Hooks.rollbackSettings() 196ms

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" 8s 689ms

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

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

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

And Go to "WAREHOUSE_TAB" 986ms

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

And Wait "60" seconds 1m

And Verify that transport window is grey 089ms

And Verify that transport is in archive 7s 274ms

Then Restore transport from archive 2s 888ms

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

Hooks

After Hooks.deleteTransportAfterTest() 767ms

After Hooks.rollbackSettings() 127ms

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 361ms

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

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

And Go to "TRANSPORT_TABLE" 375ms

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

And Confirm statuses until reach "process-ended" 38s 365ms

Error message

java.lang.AssertionError: Wartość on-the-area-magazyn-tychy atrybutu data-status-name nie zmieniła się w webelemencie [[ChromeDriver: chrome on LINUX (cc46d83b08edba653bf87ec993385712)] -> 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

Hooks

After Hooks.deleteTransportAfterTest() 881ms

After Hooks.rollbackAllCustomFieldsSettings() 544ms

After Hooks.rollbackSettings() 120ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackSettings	131	1	4	0	0	136	14	1	15	6m 19s 212ms	Failed

Tag Report