Project Number Date
ApolloFullRunnerReport apollo-test-2.118 14 sie 2021, 06:07

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 14s 956ms 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" 243ms
And Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 117ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 252ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 590ms
Then Login as "super-admin-piast" 7s 617ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 377ms
After Hooks.deleteTransportAfterApiTest() 574ms
After Hooks.rollbackSettings() 167ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 246ms
And Set token of apiUsername "super-admin-piast" 234ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 148ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 168ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 794ms
Then Login as "super-admin-piast" 2s 492ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 373ms
After Hooks.deleteTransportAfterApiTest() 667ms
After Hooks.rollbackSettings() 143ms
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" 235ms
And Set token of apiUsername "super-admin-piast" 236ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 131ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 529ms
Then Login as "super-admin-piast" 2s 411ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 413ms
After Hooks.deleteTransportAfterApiTest() 666ms
After Hooks.rollbackSettings() 112ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 260ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 127ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 184ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 241ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 696ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 786ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 640ms
After Hooks.rollbackSettings() 136ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 230ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 154ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 162ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 244ms
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_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 822ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 656ms
After Hooks.rollbackSettings() 129ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 262ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 147ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 241ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 724ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 345ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 630ms
After Hooks.rollbackSettings() 134ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
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" 239ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 580ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 038ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 664ms
After Hooks.rollbackSettings() 125ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 243ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 151ms
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" 244ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 615ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 271ms
After Hooks.deleteTransportAfterApiTest() 676ms
After Hooks.rollbackSettings() 135ms
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" 148ms
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 164ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 614ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 603ms
And Show all transport types 1s 179ms
And Click button advice in transport table "DELIVERY" 268ms
And Set advice window in schedule 3s 887ms
And Fill advice form 13s 233ms
And Click advice save button and wait for advice form to disappear 33s 905ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 555ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 496ms
And Go to transport details "DELIVERY" 2s 946ms
And Expand advice panel 633ms
Then Check are transport values equals 2s 412ms
After Hooks.deleteTransportAfterApiTest() 895ms
After Hooks.rollbackSettings() 145ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 241ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 109ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 132ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 126ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 018ms
Then Login as "neuca-admin" 2s 282ms
And Go to "TRANSPORT_TABLE" 538ms
And Confirm statuses until reach "process-ended" 22s 389ms
Then Check if sorting by 'Finished' status is working correctly 251ms
After Hooks.deleteTransportsAfterTest() 4s 431ms
After Hooks.rollbackAllCustomFieldsSettings() 344ms
After Hooks.rollbackSettings() 105ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 241ms
And Delete invitations with email "automaty31415@test.pl" 078ms
And If user is login then logout 243ms
Given Set token of apiUsername "super-admin-piast" 264ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 136ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 215ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 399ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 831ms
Then Go to "INVITATIONS_TAB" 472ms
And Go to "EXPIRED_TAB" invitation status tab 243ms
Then Invitation is displayed on list "automaty31415@test.pl" 414ms
After Hooks.deleteInvitationAfterTest() 158ms
After Hooks.rollbackSettings() 128ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 236ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 128ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 316ms
And Prepare setting for automatic time window delete with "super-admin-skz" 216ms
When Login as "swisskrono-admin" 8s 108ms
And Go to "WAREHOUSE_TAB" 936ms
Then Check if dedicated window is deleted from schedule 54s 302ms
After Hooks.rollbackSettings() 191ms
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 833ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 021ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 163ms
And Set proper delay time to move order to archive after task timeout 163ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 996ms
And Go to "WAREHOUSE_TAB" 994ms
And Change warehouse in schedule to: "Katowice" 1s 703ms
And Wait "60" seconds 1m
And Verify that transport window is grey 074ms
And Verify that transport is in archive 7s 281ms
Then Restore transport from archive 2s 913ms
And Verify that transport has been successfully restored 1s 738ms
After Hooks.deleteTransportAfterTest() 794ms
After Hooks.rollbackSettings() 127ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 233ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 118ms
And Mark custom fields as not obligatory 006ms
And Login as "dayco-admin" 2s 184ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 068ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 140ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 199ms
When Go to "TRANSPORT_TABLE" 403ms
And Click button advice in transport table "OWN_COLLECTION" 1s 282ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 48s 312ms
And Go to "TRANSPORT_TABLE" 458ms
And Find transport in table with status "planned-magazyn-tychy" 3s 692ms
And Confirm statuses until reach "process-ended" 16s 685ms
And Wait until transport disappear from transport table 37s 609ms
Then Go to "ARCHIVE_TAB" 542ms
And Show "OWN_COLLECTION" 171ms
And Verify that created transport is "true" in transport table 15s 132ms
After Hooks.deleteTransportAfterTest() 731ms
After Hooks.rollbackAllCustomFieldsSettings() 494ms
After Hooks.rollbackSettings() 135ms