Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.66	19 sie 2021, 05:10

	Steps	Scenarios	Features
@rollbackSettings	129	0	0	0	0	129	14	0	14	5m 33s 219ms	Passed

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 123ms

After Hooks.rollbackSettings() 063ms

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

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

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

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

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

Then Login as "super-admin-piast" 1s 173ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 101ms

After Hooks.rollbackSettings() 028ms

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

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

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

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

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

Then Login as "super-admin-piast" 1s 058ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 113ms

After Hooks.rollbackSettings() 025ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 076ms

After Hooks.rollbackSettings() 026ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 081ms

After Hooks.rollbackSettings() 028ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 071ms

After Hooks.rollbackSettings() 022ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 061ms

After Hooks.rollbackSettings() 025ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 067ms

After Hooks.rollbackSettings() 025ms

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

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

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

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 513ms

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

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

And Show all transport types 1s 067ms

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

And Set advice window in schedule 2s 896ms

And Fill advice form 10s 759ms

And Click advice save button and wait for advice form to disappear 31s 286ms

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

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

And Go to "TRANSPORT_TABLE" 254ms

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

And Expand advice panel 113ms

Then Check are transport values equals 2s 140ms

Hooks

After Hooks.deleteTransportAfterApiTest() 139ms

After Hooks.rollbackSettings() 026ms

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

Then Login as "neuca-admin" 1s 215ms

And Go to "TRANSPORT_TABLE" 469ms

And Confirm statuses until reach "process-ended" 31s 775ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 563ms

After Hooks.rollbackAllCustomFieldsSettings() 093ms

After Hooks.rollbackSettings() 027ms

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

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

And If user is login then logout 078ms

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

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

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

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

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 1s 119ms

Then Go to "INVITATIONS_TAB" 190ms

And Go to "EXPIRED_TAB" invitation status tab 078ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 025ms

After Hooks.rollbackSettings() 024ms

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

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

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

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

When Login as "swisskrono-admin" 1s 863ms

And Go to "WAREHOUSE_TAB" 457ms

Then Check if dedicated window is deleted from schedule 1m 23s 990ms

Hooks

After Hooks.rollbackSettings() 032ms

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" 1s 620ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 606ms

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

And Wait "60" seconds 1m

And Verify that transport window is grey 033ms

And Verify that transport is in archive 1s 617ms

Then Restore transport from archive 1s 226ms

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.rollbackSettings() 023ms

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

Steps

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

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

And Mark custom fields as not obligatory 004ms

And Login as "dayco-admin" 986ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 192ms

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

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

When Go to "TRANSPORT_TABLE" 124ms

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

And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 628ms

And Go to "TRANSPORT_TABLE" 117ms

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

And Confirm statuses until reach "process-ended" 27s 307ms

And Wait until transport disappear from transport table 20s 859ms

Then Go to "ARCHIVE_TAB" 283ms

And Show "OWN_COLLECTION" 075ms

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

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.rollbackAllCustomFieldsSettings() 081ms

After Hooks.rollbackSettings() 024ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackSettings	129	0	0	0	0	129	14	0	14	5m 33s 219ms	Passed

Tag Report