Project Number Date
ApolloFullRunnerReport apollo-test-2.71 17 sie 2021, 09:11

Tag Report

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 7m 12s 449ms 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" 234ms
And Set token of apiUsername "super-admin-piast" 231ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 176ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 222ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 619ms
Then Login as "super-admin-piast" 8s 013ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 369ms
After Hooks.deleteTransportAfterApiTest() 679ms
After Hooks.rollbackSettings() 226ms
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" 250ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 165ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 164ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 609ms
Then Login as "super-admin-piast" 2s 549ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 393ms
After Hooks.deleteTransportAfterApiTest() 666ms
After Hooks.rollbackSettings() 162ms
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" 245ms
And Set token of apiUsername "super-admin-piast" 244ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 118ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 600ms
Then Login as "super-admin-piast" 2s 506ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 367ms
After Hooks.deleteTransportAfterApiTest() 631ms
After Hooks.rollbackSettings() 107ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 133ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 177ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 238ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 604ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 813ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 678ms
After Hooks.rollbackSettings() 135ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 244ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 134ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 175ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 234ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 583ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 819ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 639ms
After Hooks.rollbackSettings() 126ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 003ms
Given Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 174ms
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 594ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 332ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 640ms
After Hooks.rollbackSettings() 137ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 270ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 153ms
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 612ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 029ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 617ms
After Hooks.rollbackSettings() 144ms
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" 133ms
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" 239ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 584ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 283ms
After Hooks.deleteTransportAfterApiTest() 665ms
After Hooks.rollbackSettings() 138ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 266ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 139ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 024ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 538ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 660ms
And Show all transport types 1s 181ms
And Click button advice in transport table "DELIVERY" 225ms
And Set advice window in schedule 3s 938ms
And Fill advice form 13s 218ms
And Click advice save button and wait for advice form to disappear 33s 922ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 647ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 484ms
And Go to transport details "DELIVERY" 2s 953ms
And Expand advice panel 529ms
Then Check are transport values equals 2s 372ms
After Hooks.deleteTransportAfterApiTest() 872ms
After Hooks.rollbackSettings() 129ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 225ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 115ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 140ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 124ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 305ms
Then Login as "neuca-admin" 2s 343ms
And Go to "TRANSPORT_TABLE" 572ms
And Confirm statuses until reach "process-ended" 22s 349ms
Then Check if sorting by 'Finished' status is working correctly 266ms
After Hooks.deleteTransportsAfterTest() 4s 452ms
After Hooks.rollbackAllCustomFieldsSettings() 343ms
After Hooks.rollbackSettings() 113ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 224ms
And Delete invitations with email "automaty31415@test.pl" 100ms
And If user is login then logout 229ms
Given Set token of apiUsername "super-admin-piast" 337ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 145ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 251ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 460ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 797ms
Then Go to "INVITATIONS_TAB" 482ms
And Go to "EXPIRED_TAB" invitation status tab 284ms
Then Invitation is displayed on list "automaty31415@test.pl" 451ms
After Hooks.deleteInvitationAfterTest() 133ms
After Hooks.rollbackSettings() 122ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 235ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 144ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 342ms
And Prepare setting for automatic time window delete with "super-admin-skz" 238ms
When Login as "swisskrono-admin" 7s 922ms
And Go to "WAREHOUSE_TAB" 940ms
Then Check if dedicated window is deleted from schedule 51s 348ms
After Hooks.rollbackSettings() 199ms
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 890ms
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" 138ms
And Set proper delay time to move order to archive after task timeout 131ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 2s 019ms
And Go to "WAREHOUSE_TAB" 976ms
And Change warehouse in schedule to: "Katowice" 1s 734ms
And Wait "60" seconds 1m
And Verify that transport window is grey 078ms
And Verify that transport is in archive 7s 482ms
Then Restore transport from archive 2s 870ms
And Verify that transport has been successfully restored 1s 760ms
After Hooks.deleteTransportAfterTest() 773ms
After Hooks.rollbackSettings() 120ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 223ms
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 195ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 104ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 134ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 172ms
When Go to "TRANSPORT_TABLE" 420ms
And Click button advice in transport table "OWN_COLLECTION" 1s 243ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 48s 282ms
And Go to "TRANSPORT_TABLE" 477ms
And Find transport in table with status "planned-magazyn-tychy" 3s 707ms
And Confirm statuses until reach "process-ended" 16s 706ms
And Wait until transport disappear from transport table 37s 355ms
Then Go to "ARCHIVE_TAB" 524ms
And Show "OWN_COLLECTION" 191ms
And Verify that created transport is "true" in transport table 15s 144ms
After Hooks.deleteTransportAfterTest() 742ms
After Hooks.rollbackAllCustomFieldsSettings() 520ms
After Hooks.rollbackSettings() 142ms