Project Number Date
ApolloFullRunnerReport apollo-test-2.143 03 wrz 2021, 07:47

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@rollbackSettings 136 0 0 0 0 136 15 0 15 6m 28s 707ms Passed
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
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" 255ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 147ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 226ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 712ms
Then Login as "super-admin-piast" 8s 418ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 384ms
After Hooks.deleteTransportAfterApiTest() 518ms
After Hooks.rollbackSettings() 166ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 248ms
And Set token of apiUsername "super-admin-piast" 234ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 158ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 172ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 772ms
Then Login as "super-admin-piast" 2s 559ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 370ms
After Hooks.deleteTransportAfterApiTest() 674ms
After Hooks.rollbackSettings() 148ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 243ms
And Set token of apiUsername "super-admin-piast" 255ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 121ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 719ms
Then Login as "super-admin-piast" 2s 494ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 378ms
After Hooks.deleteTransportAfterApiTest() 667ms
After Hooks.rollbackSettings() 104ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 236ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 135ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 169ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 239ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 687ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 872ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 667ms
After Hooks.rollbackSettings() 138ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 251ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 169ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 248ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 670ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 927ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 634ms
After Hooks.rollbackSettings() 137ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 244ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
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" 250ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 703ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 350ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 648ms
After Hooks.rollbackSettings() 163ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 256ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 135ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 160ms
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 671ms
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() 658ms
After Hooks.rollbackSettings() 141ms
View Feature API Transport
@deleteApiTransportsAfterTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 781ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 153ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 130ms
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 668ms
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 643ms
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" 349ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 274ms
After Hooks.rollbackSettings() 092ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 247ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 172ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 232ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 691ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 266ms
After Hooks.deleteTransportAfterApiTest() 628ms
After Hooks.rollbackSettings() 127ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 259ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 150ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 231ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 701ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 299ms
And Show all transport types 1s 167ms
And Click button advice in transport table "DELIVERY" 260ms
And Set advice window in schedule 3s 735ms
And Fill advice form 13s 351ms
And Click advice save button and wait for advice form to disappear 33s 872ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 679ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 470ms
And Go to transport details "DELIVERY" 2s 877ms
And Expand advice panel 526ms
Then Check are transport values equals 2s 382ms
After Hooks.deleteTransportAfterApiTest() 828ms
After Hooks.rollbackSettings() 155ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 224ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 109ms
And Mark custom fields as not obligatory 008ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 141ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 131ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 190ms
Then Login as "neuca-admin" 2s 436ms
And Go to "TRANSPORT_TABLE" 505ms
And Confirm statuses until reach "process-ended" 21s 364ms
Then Check if sorting by 'Finished' status is working correctly 186ms
After Hooks.deleteTransportsAfterTest() 4s 369ms
After Hooks.rollbackAllCustomFieldsSettings() 332ms
After Hooks.rollbackSettings() 116ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 231ms
And Delete invitations with email "automaty31415@test.pl" 096ms
And If user is login then logout 221ms
Given Set token of apiUsername "super-admin-piast" 300ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 147ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 190ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 383ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 839ms
Then Go to "INVITATIONS_TAB" 442ms
And Go to "EXPIRED_TAB" invitation status tab 264ms
Then Invitation is displayed on list "automaty31415@test.pl" 467ms
After Hooks.deleteInvitationAfterTest() 145ms
After Hooks.rollbackSettings() 128ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 242ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 113ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 351ms
And Prepare setting for automatic time window delete with "super-admin-skz" 243ms
When Login as "swisskrono-admin" 8s 001ms
And Go to "WAREHOUSE_TAB" 901ms
Then Check if dedicated window is deleted from schedule 1m 3s 057ms
After Hooks.rollbackSettings() 198ms
View Feature Move transport to archive
@rollbackSettings @deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 724ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 015ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 153ms
And Set proper delay time to move order to archive after task timeout 155ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 997ms
And Go to "WAREHOUSE_TAB" 982ms
And Change warehouse in schedule to: "Katowice" 1s 208ms
And Wait "60" seconds 1m
And Verify that transport window is grey 087ms
And Verify that transport is in archive 7s 671ms
Then Restore transport from archive 2s 676ms
And Verify that transport has been successfully restored 1s 790ms
After Hooks.deleteTransportAfterTest() 753ms
After Hooks.rollbackSettings() 129ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 222ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 131ms
And Mark custom fields as not obligatory 004ms
And Login as "dayco-admin" 2s 225ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 075ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 141ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 198ms
When Go to "TRANSPORT_TABLE" 353ms
And Click button advice in transport table "OWN_COLLECTION" 1s 352ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 716ms
And Go to "TRANSPORT_TABLE" 361ms
And Find transport in table with status "planned-magazyn-tychy" 3s 727ms
And Confirm statuses until reach "process-ended" 16s 613ms
And Wait until transport disappear from transport table 22s 520ms
Then Go to "ARCHIVE_TAB" 542ms
And Show "OWN_COLLECTION" 183ms
And Verify that created transport is "true" in transport table 15s 127ms
After Hooks.deleteTransportAfterTest() 753ms
After Hooks.rollbackAllCustomFieldsSettings() 571ms
After Hooks.rollbackSettings() 122ms