Project Number Date
ApolloFullRunnerReport apollo-test-2.137 29 sie 2021, 05:53

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 5m 51s 338ms 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" 233ms
And Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 527ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 251ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 769ms
Then Login as "super-admin-piast" 5s 350ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 389ms
After Hooks.deleteTransportAfterApiTest() 715ms
After Hooks.rollbackSettings() 175ms
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" 256ms
And Set token of apiUsername "super-admin-piast" 261ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 193ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 193ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 772ms
Then Login as "super-admin-piast" 2s 540ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 387ms
After Hooks.deleteTransportAfterApiTest() 638ms
After Hooks.rollbackSettings() 134ms
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" 244ms
And Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
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 729ms
Then Login as "super-admin-piast" 2s 699ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 403ms
After Hooks.deleteTransportAfterApiTest() 678ms
After Hooks.rollbackSettings() 097ms
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" 155ms
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" 246ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 717ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 957ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 756ms
After Hooks.rollbackSettings() 137ms
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" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 169ms
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 711ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 908ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 630ms
After Hooks.rollbackSettings() 137ms
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" 135ms
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" 219ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 683ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 339ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 670ms
After Hooks.rollbackSettings() 146ms
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" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 176ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 252ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 747ms
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() 676ms
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 939ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms
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 658ms
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 758ms
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" 404ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 417ms
After Hooks.rollbackSettings() 095ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
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" 241ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 729ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 317ms
After Hooks.deleteTransportAfterApiTest() 715ms
After Hooks.rollbackSettings() 127ms
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" 148ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 140ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 3s 192ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 651ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 008ms
And Show all transport types 1s 159ms
And Click button advice in transport table "DELIVERY" 282ms
And Set advice window in schedule 3s 856ms
And Fill advice form 13s 351ms
And Click advice save button and wait for advice form to disappear 33s 864ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 3s 088ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 458ms
And Go to transport details "DELIVERY" 2s 943ms
And Expand advice panel 711ms
Then Check are transport values equals 2s 505ms
After Hooks.deleteTransportAfterApiTest() 869ms
After Hooks.rollbackSettings() 147ms
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 111ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 149ms
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 055ms
Then Login as "neuca-admin" 2s 304ms
And Go to "TRANSPORT_TABLE" 514ms
And Confirm statuses until reach "process-ended" 21s 414ms
Then Check if sorting by 'Finished' status is working correctly 286ms
After Hooks.deleteTransportsAfterTest() 4s 509ms
After Hooks.rollbackAllCustomFieldsSettings() 331ms
After Hooks.rollbackSettings() 102ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 234ms
And Delete invitations with email "automaty31415@test.pl" 100ms
And If user is login then logout 267ms
Given Set token of apiUsername "super-admin-piast" 266ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 143ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 199ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 509ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 763ms
Then Go to "INVITATIONS_TAB" 500ms
And Go to "EXPIRED_TAB" invitation status tab 284ms
Then Invitation is displayed on list "automaty31415@test.pl" 416ms
After Hooks.deleteInvitationAfterTest() 131ms
After Hooks.rollbackSettings() 106ms
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" 129ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 335ms
And Prepare setting for automatic time window delete with "super-admin-skz" 217ms
When Login as "swisskrono-admin" 7s 943ms
And Go to "WAREHOUSE_TAB" 891ms
Then Check if dedicated window is deleted from schedule 30s 281ms
After Hooks.rollbackSettings() 186ms
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 477ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 015ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 148ms
And Set proper delay time to move order to archive after task timeout 156ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 2s 013ms
And Go to "WAREHOUSE_TAB" 927ms
And Change warehouse in schedule to: "Katowice" 1s 603ms
And Wait "60" seconds 1m
And Verify that transport window is grey 077ms
And Verify that transport is in archive 4s 438ms
Then Restore transport from archive 2s 672ms
And Verify that transport has been successfully restored 1s 801ms
After Hooks.deleteTransportAfterTest() 790ms
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" 220ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 129ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 305ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 063ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 129ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 223ms
When Go to "TRANSPORT_TABLE" 359ms
And Click button advice in transport table "OWN_COLLECTION" 1s 330ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 564ms
And Go to "TRANSPORT_TABLE" 357ms
And Find transport in table with status "planned-magazyn-tychy" 3s 726ms
And Confirm statuses until reach "process-ended" 16s 721ms
And Wait until transport disappear from transport table 25s 403ms
Then Go to "ARCHIVE_TAB" 528ms
And Show "OWN_COLLECTION" 174ms
And Verify that created transport is "true" in transport table 15s 154ms
After Hooks.deleteTransportAfterTest() 724ms
After Hooks.rollbackAllCustomFieldsSettings() 586ms
After Hooks.rollbackSettings() 151ms