Project Number Date
ApolloFullRunnerReport apollo-test-2.139 31 sie 2021, 05:52

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 34s 996ms 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" 251ms
And Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 261ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 248ms
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" 8s 406ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 400ms
After Hooks.deleteTransportAfterApiTest() 560ms
After Hooks.rollbackSettings() 165ms
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" 248ms
And Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 161ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 809ms
Then Login as "super-admin-piast" 2s 568ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 395ms
After Hooks.deleteTransportAfterApiTest() 644ms
After Hooks.rollbackSettings() 136ms
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" 261ms
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" 122ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 739ms
Then Login as "super-admin-piast" 2s 511ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 398ms
After Hooks.deleteTransportAfterApiTest() 615ms
After Hooks.rollbackSettings() 106ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 238ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 155ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 164ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 236ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 672ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 835ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 686ms
After Hooks.rollbackSettings() 129ms
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" 134ms
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" 237ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 672ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 866ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 650ms
After Hooks.rollbackSettings() 136ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 246ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 165ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 146ms
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 706ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 336ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 647ms
After Hooks.rollbackSettings() 167ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
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" 163ms
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 708ms
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() 650ms
After Hooks.rollbackSettings() 123ms
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 958ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 148ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 126ms
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 672ms
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 632ms
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" 345ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 283ms
After Hooks.rollbackSettings() 103ms
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" 128ms
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" 261ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 773ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 272ms
After Hooks.deleteTransportAfterApiTest() 619ms
After Hooks.rollbackSettings() 140ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 154ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 159ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 218ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 672ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 009ms
And Show all transport types 1s 162ms
And Click button advice in transport table "DELIVERY" 276ms
And Set advice window in schedule 3s 789ms
And Fill advice form 13s 401ms
And Click advice save button and wait for advice form to disappear 33s 839ms
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" 532ms
And Go to transport details "DELIVERY" 3s 010ms
And Expand advice panel 488ms
Then Check are transport values equals 2s 419ms
After Hooks.deleteTransportAfterApiTest() 825ms
After Hooks.rollbackSettings() 125ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 219ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 105ms
And Mark custom fields as not obligatory 005ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 129ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 099ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 095ms
Then Login as "neuca-admin" 2s 321ms
And Go to "TRANSPORT_TABLE" 507ms
And Confirm statuses until reach "process-ended" 21s 550ms
Then Check if sorting by 'Finished' status is working correctly 318ms
After Hooks.deleteTransportsAfterTest() 4s 500ms
After Hooks.rollbackAllCustomFieldsSettings() 347ms
After Hooks.rollbackSettings() 111ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 228ms
And Delete invitations with email "automaty31415@test.pl" 089ms
And If user is login then logout 288ms
Given Set token of apiUsername "super-admin-piast" 247ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 138ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 208ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 480ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 659ms
Then Go to "INVITATIONS_TAB" 537ms
And Go to "EXPIRED_TAB" invitation status tab 271ms
Then Invitation is displayed on list "automaty31415@test.pl" 453ms
After Hooks.deleteInvitationAfterTest() 150ms
After Hooks.rollbackSettings() 117ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 219ms
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" 280ms
And Prepare setting for automatic time window delete with "super-admin-skz" 216ms
When Login as "swisskrono-admin" 7s 870ms
And Go to "WAREHOUSE_TAB" 937ms
Then Check if dedicated window is deleted from schedule 1m 12s 327ms
After Hooks.rollbackSettings() 196ms
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 725ms
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" 144ms
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" 1s 992ms
And Go to "WAREHOUSE_TAB" 1s 044ms
And Change warehouse in schedule to: "Katowice" 1s 659ms
And Wait "60" seconds 1m
And Verify that transport window is grey 087ms
And Verify that transport is in archive 3s 824ms
Then Restore transport from archive 2s 642ms
And Verify that transport has been successfully restored 1s 794ms
After Hooks.deleteTransportAfterTest() 795ms
After Hooks.rollbackSettings() 128ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 229ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 115ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 270ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 052ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 134ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 205ms
When Go to "TRANSPORT_TABLE" 363ms
And Click button advice in transport table "OWN_COLLECTION" 1s 375ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 594ms
And Go to "TRANSPORT_TABLE" 368ms
And Find transport in table with status "planned-magazyn-tychy" 3s 740ms
And Confirm statuses until reach "process-ended" 16s 676ms
And Wait until transport disappear from transport table 22s 549ms
Then Go to "ARCHIVE_TAB" 571ms
And Show "OWN_COLLECTION" 186ms
And Verify that created transport is "true" in transport table 15s 163ms
After Hooks.deleteTransportAfterTest() 721ms
After Hooks.rollbackAllCustomFieldsSettings() 552ms
After Hooks.rollbackSettings() 146ms