Project Number Date
ApolloFullRunnerReport apollo-test-2.156 13 wrz 2021, 06:47

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 28s 107ms 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" 265ms
And Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 290ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 268ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 733ms
Then Login as "super-admin-piast" 6s 621ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 361ms
After Hooks.deleteTransportAfterApiTest() 660ms
After Hooks.rollbackSettings() 199ms
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" 247ms
And Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 139ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 173ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 736ms
Then Login as "super-admin-piast" 2s 613ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 400ms
After Hooks.deleteTransportAfterApiTest() 640ms
After Hooks.rollbackSettings() 144ms
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" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 124ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 770ms
Then Login as "super-admin-piast" 2s 554ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 375ms
After Hooks.deleteTransportAfterApiTest() 656ms
After Hooks.rollbackSettings() 104ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 238ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 166ms
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 753ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 827ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 709ms
After Hooks.rollbackSettings() 144ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 246ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
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" 233ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 693ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 862ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 647ms
After Hooks.rollbackSettings() 132ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 231ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 175ms
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 752ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 333ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 622ms
After Hooks.rollbackSettings() 129ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 135ms
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" 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() 708ms
After Hooks.rollbackSettings() 145ms
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 820ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 156ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 129ms
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 642ms
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
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" 351ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 267ms
After Hooks.rollbackSettings() 098ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 244ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 119ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 144ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 225ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 656ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 264ms
After Hooks.deleteTransportAfterApiTest() 664ms
After Hooks.rollbackSettings() 128ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 161ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 345ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 719ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 009ms
And Show all transport types 1s 184ms
And Click button advice in transport table "DELIVERY" 246ms
And Set advice window in schedule 3s 766ms
And Fill advice form 13s 370ms
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" 2s 674ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 556ms
And Go to transport details "DELIVERY" 2s 914ms
And Expand advice panel 501ms
Then Check are transport values equals 2s 395ms
After Hooks.deleteTransportAfterApiTest() 879ms
After Hooks.rollbackSettings() 133ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 231ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 112ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 144ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 129ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 181ms
Then Login as "neuca-admin" 2s 292ms
And Go to "TRANSPORT_TABLE" 497ms
And Confirm statuses until reach "process-ended" 22s 367ms
Then Check if sorting by 'Finished' status is working correctly 299ms
After Hooks.deleteTransportsAfterTest() 4s 458ms
After Hooks.rollbackAllCustomFieldsSettings() 333ms
After Hooks.rollbackSettings() 104ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 227ms
And Delete invitations with email "automaty31415@test.pl" 089ms
And If user is login then logout 270ms
Given Set token of apiUsername "super-admin-piast" 241ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 150ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 198ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 420ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 698ms
Then Go to "INVITATIONS_TAB" 487ms
And Go to "EXPIRED_TAB" invitation status tab 305ms
Then Invitation is displayed on list "automaty31415@test.pl" 455ms
After Hooks.deleteInvitationAfterTest() 175ms
After Hooks.rollbackSettings() 123ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 237ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 133ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 342ms
And Prepare setting for automatic time window delete with "super-admin-skz" 228ms
When Login as "swisskrono-admin" 7s 842ms
And Go to "WAREHOUSE_TAB" 925ms
Then Check if dedicated window is deleted from schedule 47s 966ms
After Hooks.rollbackSettings() 232ms
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 140ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 018ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 151ms
And Set proper delay time to move order to archive after task timeout 142ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 927ms
And Go to "WAREHOUSE_TAB" 954ms
And Change warehouse in schedule to: "Katowice" 1s 250ms
And Wait "60" seconds 1m
And Verify that transport window is grey 077ms
And Verify that transport is in archive 7s 554ms
Then Restore transport from archive 2s 662ms
And Verify that transport has been successfully restored 1s 910ms
After Hooks.deleteTransportAfterTest() 770ms
After Hooks.rollbackSettings() 118ms
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 115ms
And Mark custom fields as not obligatory 007ms
And Login as "dayco-admin" 2s 253ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 182ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 147ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 193ms
When Go to "TRANSPORT_TABLE" 405ms
And Click button advice in transport table "OWN_COLLECTION" 1s 175ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 670ms
And Go to "TRANSPORT_TABLE" 392ms
And Find transport in table with status "planned-magazyn-tychy" 3s 695ms
And Confirm statuses until reach "process-ended" 16s 667ms
And Wait until transport disappear from transport table 40s 389ms
Then Go to "ARCHIVE_TAB" 563ms
And Show "OWN_COLLECTION" 184ms
And Verify that created transport is "true" in transport table 15s 193ms
After Hooks.deleteTransportAfterTest() 835ms
After Hooks.rollbackAllCustomFieldsSettings() 525ms
After Hooks.rollbackSettings() 119ms