Project Number Date
ApolloFullRunnerReport apollo-test-2.147 06 wrz 2021, 06:13

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 18s 555ms Passed
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" 264ms
And Set token of apiUsername "super-admin-piast" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 181ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 243ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 715ms
Then Login as "super-admin-piast" 8s 239ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 372ms
After Hooks.deleteTransportAfterApiTest() 559ms
After Hooks.rollbackSettings() 167ms
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" 238ms
And Set token of apiUsername "super-admin-piast" 239ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 158ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 154ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 761ms
Then Login as "super-admin-piast" 2s 397ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 399ms
After Hooks.deleteTransportAfterApiTest() 672ms
After Hooks.rollbackSettings() 139ms
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" 232ms
And Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 143ms
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 746ms
Then Login as "super-admin-piast" 2s 500ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 362ms
After Hooks.deleteTransportAfterApiTest() 663ms
After Hooks.rollbackSettings() 109ms
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" 148ms
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" 243ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 659ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 904ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 671ms
After Hooks.rollbackSettings() 167ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 148ms
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" 247ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 698ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 828ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 629ms
After Hooks.rollbackSettings() 127ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 168ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 246ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 711ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 361ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 648ms
After Hooks.rollbackSettings() 125ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 256ms
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" 264ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 704ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 030ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 655ms
After Hooks.rollbackSettings() 142ms
View Feature API Transport
@deleteApiTransportsAfterTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 864ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 152ms
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 681ms
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 671ms
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" 333ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 275ms
After Hooks.rollbackSettings() 095ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 248ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 135ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 159ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 240ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 657ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 273ms
After Hooks.deleteTransportAfterApiTest() 611ms
After Hooks.rollbackSettings() 129ms
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" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 166ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 343ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 660ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 048ms
And Show all transport types 1s 178ms
And Click button advice in transport table "DELIVERY" 216ms
And Set advice window in schedule 3s 827ms
And Fill advice form 13s 331ms
And Click advice save button and wait for advice form to disappear 33s 873ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 733ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 485ms
And Go to transport details "DELIVERY" 2s 975ms
And Expand advice panel 451ms
Then Check are transport values equals 2s 351ms
After Hooks.deleteTransportAfterApiTest() 888ms
After Hooks.rollbackSettings() 147ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 250ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 107ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 128ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 137ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 376ms
Then Login as "neuca-admin" 2s 340ms
And Go to "TRANSPORT_TABLE" 509ms
And Confirm statuses until reach "process-ended" 22s 358ms
Then Check if sorting by 'Finished' status is working correctly 318ms
After Hooks.deleteTransportsAfterTest() 4s 562ms
After Hooks.rollbackAllCustomFieldsSettings() 358ms
After Hooks.rollbackSettings() 111ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 250ms
And Delete invitations with email "automaty31415@test.pl" 097ms
And If user is login then logout 223ms
Given Set token of apiUsername "super-admin-piast" 244ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 140ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 218ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 397ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 667ms
Then Go to "INVITATIONS_TAB" 509ms
And Go to "EXPIRED_TAB" invitation status tab 303ms
Then Invitation is displayed on list "automaty31415@test.pl" 458ms
After Hooks.deleteInvitationAfterTest() 154ms
After Hooks.rollbackSettings() 130ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 237ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 125ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 328ms
And Prepare setting for automatic time window delete with "super-admin-skz" 216ms
When Login as "swisskrono-admin" 7s 746ms
And Go to "WAREHOUSE_TAB" 915ms
Then Check if dedicated window is deleted from schedule 54s 356ms
After Hooks.rollbackSettings() 191ms
View Feature Move transport to archive
@rollbackSettings @deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 7s 191ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 017ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 251ms
And Set proper delay time to move order to archive after task timeout 145ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 2s 108ms
And Go to "WAREHOUSE_TAB" 1s 001ms
And Change warehouse in schedule to: "Katowice" 1s 259ms
And Wait "60" seconds 1m
And Verify that transport window is grey 087ms
And Verify that transport is in archive 7s 351ms
Then Restore transport from archive 2s 713ms
And Verify that transport has been successfully restored 1s 749ms
After Hooks.deleteTransportAfterTest() 790ms
After Hooks.rollbackSettings() 118ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 008ms
Given Set token of apiUsername "super-admin-dayco" 209ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 121ms
And Mark custom fields as not obligatory 013ms
And Login as "dayco-admin" 2s 144ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 068ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 132ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 196ms
When Go to "TRANSPORT_TABLE" 361ms
And Click button advice in transport table "OWN_COLLECTION" 1s 367ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 651ms
And Go to "TRANSPORT_TABLE" 374ms
And Find transport in table with status "planned-magazyn-tychy" 3s 698ms
And Confirm statuses until reach "process-ended" 16s 633ms
And Wait until transport disappear from transport table 22s 257ms
Then Go to "ARCHIVE_TAB" 494ms
And Show "OWN_COLLECTION" 194ms
And Verify that created transport is "true" in transport table 15s 152ms
After Hooks.deleteTransportAfterTest() 713ms
After Hooks.rollbackAllCustomFieldsSettings() 558ms
After Hooks.rollbackSettings() 142ms