Project Number Date
ApolloFullRunnerReport apollo-test-2.135 27 sie 2021, 06:00

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 32s 854ms 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" 246ms
And Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 290ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 264ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 731ms
Then Login as "super-admin-piast" 8s 526ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 401ms
After Hooks.deleteTransportAfterApiTest() 674ms
After Hooks.rollbackSettings() 201ms
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" 250ms
And Set token of apiUsername "super-admin-piast" 249ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 156ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 737ms
Then Login as "super-admin-piast" 2s 574ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 365ms
After Hooks.deleteTransportAfterApiTest() 670ms
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" 237ms
And Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 152ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 114ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 717ms
Then Login as "super-admin-piast" 2s 482ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 421ms
After Hooks.deleteTransportAfterApiTest() 659ms
After Hooks.rollbackSettings() 108ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 250ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
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" 236ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 745ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 886ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 659ms
After Hooks.rollbackSettings() 144ms
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" 138ms
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" 234ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 707ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 867ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 655ms
After Hooks.rollbackSettings() 136ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 233ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
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" 243ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 732ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 384ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 655ms
After Hooks.rollbackSettings() 131ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 253ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 170ms
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 697ms
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() 631ms
After Hooks.rollbackSettings() 133ms
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 751ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 155ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 135ms
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 666ms
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 692ms
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" 350ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 308ms
After Hooks.rollbackSettings() 094ms
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" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 149ms
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 741ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 255ms
After Hooks.deleteTransportAfterApiTest() 609ms
After Hooks.rollbackSettings() 134ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 258ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 167ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 378ms
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" 008ms
And Show all transport types 1s 158ms
And Click button advice in transport table "DELIVERY" 237ms
And Set advice window in schedule 3s 724ms
And Fill advice form 13s 280ms
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 707ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 469ms
And Go to transport details "DELIVERY" 2s 933ms
And Expand advice panel 499ms
Then Check are transport values equals 2s 392ms
After Hooks.deleteTransportAfterApiTest() 883ms
After Hooks.rollbackSettings() 136ms
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 113ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 143ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 122ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 046ms
Then Login as "neuca-admin" 2s 332ms
And Go to "TRANSPORT_TABLE" 516ms
And Confirm statuses until reach "process-ended" 21s 412ms
Then Check if sorting by 'Finished' status is working correctly 273ms
After Hooks.deleteTransportsAfterTest() 4s 504ms
After Hooks.rollbackAllCustomFieldsSettings() 334ms
After Hooks.rollbackSettings() 103ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 226ms
And Delete invitations with email "automaty31415@test.pl" 091ms
And If user is login then logout 277ms
Given Set token of apiUsername "super-admin-piast" 249ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 142ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 189ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 360ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 834ms
Then Go to "INVITATIONS_TAB" 528ms
And Go to "EXPIRED_TAB" invitation status tab 280ms
Then Invitation is displayed on list "automaty31415@test.pl" 581ms
After Hooks.deleteInvitationAfterTest() 155ms
After Hooks.rollbackSettings() 128ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 244ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 135ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 318ms
And Prepare setting for automatic time window delete with "super-admin-skz" 225ms
When Login as "swisskrono-admin" 7s 901ms
And Go to "WAREHOUSE_TAB" 949ms
Then Check if dedicated window is deleted from schedule 51s 336ms
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 774ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 023ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 290ms
And Set proper delay time to move order to archive after task timeout 157ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 2s 101ms
And Go to "WAREHOUSE_TAB" 904ms
And Change warehouse in schedule to: "Katowice" 1s 600ms
And Wait "60" seconds 1m
And Verify that transport window is grey 076ms
And Verify that transport is in archive 7s 655ms
Then Restore transport from archive 2s 695ms
And Verify that transport has been successfully restored 1s 804ms
After Hooks.deleteTransportAfterTest() 768ms
After Hooks.rollbackSettings() 130ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 230ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 118ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 276ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 067ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 127ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 196ms
When Go to "TRANSPORT_TABLE" 367ms
And Click button advice in transport table "OWN_COLLECTION" 1s 345ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 552ms
And Go to "TRANSPORT_TABLE" 371ms
And Find transport in table with status "planned-magazyn-tychy" 3s 671ms
And Confirm statuses until reach "process-ended" 16s 752ms
And Wait until transport disappear from transport table 37s 585ms
Then Go to "ARCHIVE_TAB" 524ms
And Show "OWN_COLLECTION" 170ms
And Verify that created transport is "true" in transport table 15s 148ms
After Hooks.deleteTransportAfterTest() 798ms
After Hooks.rollbackAllCustomFieldsSettings() 546ms
After Hooks.rollbackSettings() 139ms