Project Number Date
ApolloFullRunnerReport apollo-test-2.148 07 wrz 2021, 06:21

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 31s 327ms 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" 248ms
And Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 289ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 247ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 695ms
Then Login as "super-admin-piast" 7s 043ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 423ms
After Hooks.deleteTransportAfterApiTest() 568ms
After Hooks.rollbackSettings() 178ms
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" 228ms
And Set token of apiUsername "super-admin-piast" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
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 716ms
Then Login as "super-admin-piast" 2s 482ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 359ms
After Hooks.deleteTransportAfterApiTest() 681ms
After Hooks.rollbackSettings() 128ms
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" 243ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 163ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 129ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 721ms
Then Login as "super-admin-piast" 2s 515ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 382ms
After Hooks.deleteTransportAfterApiTest() 672ms
After Hooks.rollbackSettings() 109ms
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" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 161ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 250ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 714ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 2s 038ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 662ms
After Hooks.rollbackSettings() 157ms
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" 140ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 158ms
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 744ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 892ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 655ms
After Hooks.rollbackSettings() 134ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 257ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
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" 242ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 682ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 340ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 639ms
After Hooks.rollbackSettings() 141ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 263ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 195ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 230ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 742ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 027ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 657ms
After Hooks.rollbackSettings() 140ms
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 976ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 149ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 130ms
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 673ms
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 629ms
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" 348ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 228ms
After Hooks.rollbackSettings() 097ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
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" 248ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 645ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 258ms
After Hooks.deleteTransportAfterApiTest() 615ms
After Hooks.rollbackSettings() 127ms
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" 127ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 158ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 536ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 740ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 008ms
And Show all transport types 1s 191ms
And Click button advice in transport table "DELIVERY" 268ms
And Set advice window in schedule 3s 897ms
And Fill advice form 13s 335ms
And Click advice save button and wait for advice form to disappear 33s 854ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 692ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 557ms
And Go to transport details "DELIVERY" 3s
And Expand advice panel 561ms
Then Check are transport values equals 2s 363ms
After Hooks.deleteTransportAfterApiTest() 829ms
After Hooks.rollbackSettings() 138ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 235ms
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" 135ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 123ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 173ms
Then Login as "neuca-admin" 2s 283ms
And Go to "TRANSPORT_TABLE" 550ms
And Confirm statuses until reach "process-ended" 22s 399ms
Then Check if sorting by 'Finished' status is working correctly 254ms
After Hooks.deleteTransportsAfterTest() 4s 429ms
After Hooks.rollbackAllCustomFieldsSettings() 346ms
After Hooks.rollbackSettings() 111ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-piast" 230ms
And Delete invitations with email "automaty31415@test.pl" 088ms
And If user is login then logout 245ms
Given Set token of apiUsername "super-admin-piast" 258ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 152ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 210ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 378ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 688ms
Then Go to "INVITATIONS_TAB" 579ms
And Go to "EXPIRED_TAB" invitation status tab 270ms
Then Invitation is displayed on list "automaty31415@test.pl" 426ms
After Hooks.deleteInvitationAfterTest() 140ms
After Hooks.rollbackSettings() 117ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 240ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 140ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 312ms
And Prepare setting for automatic time window delete with "super-admin-skz" 237ms
When Login as "swisskrono-admin" 7s 891ms
And Go to "WAREHOUSE_TAB" 892ms
Then Check if dedicated window is deleted from schedule 51s 291ms
After Hooks.rollbackSettings() 179ms
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" 7s 274ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 019ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 167ms
And Set proper delay time to move order to archive after task timeout 146ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 2s 046ms
And Go to "WAREHOUSE_TAB" 978ms
And Change warehouse in schedule to: "Katowice" 1s 258ms
And Wait "60" seconds 1m
And Verify that transport window is grey 087ms
And Verify that transport is in archive 7s 810ms
Then Restore transport from archive 2s 681ms
And Verify that transport has been successfully restored 1s 798ms
After Hooks.deleteTransportAfterTest() 800ms
After Hooks.rollbackSettings() 121ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 224ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 129ms
And Mark custom fields as not obligatory 006ms
And Login as "dayco-admin" 2s 205ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 087ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 133ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 205ms
When Go to "TRANSPORT_TABLE" 353ms
And Click button advice in transport table "OWN_COLLECTION" 1s 314ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 756ms
And Go to "TRANSPORT_TABLE" 400ms
And Find transport in table with status "planned-magazyn-tychy" 3s 733ms
And Confirm statuses until reach "process-ended" 16s 768ms
And Wait until transport disappear from transport table 37s 564ms
Then Go to "ARCHIVE_TAB" 580ms
And Show "OWN_COLLECTION" 180ms
And Verify that created transport is "true" in transport table 15s 129ms
After Hooks.deleteTransportAfterTest() 745ms
After Hooks.rollbackAllCustomFieldsSettings() 523ms
After Hooks.rollbackSettings() 128ms