Project Number Date
ApolloFullRunnerReport apollo-test-2.158 15 wrz 2021, 06:58

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 55s 841ms 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" 296ms
And Set token of apiUsername "super-admin-piast" 320ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 305ms
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 662ms
Then Login as "super-admin-piast" 6s 655ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 360ms
After Hooks.deleteTransportAfterApiTest() 641ms
After Hooks.rollbackSettings() 172ms
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" 306ms
And Set token of apiUsername "super-admin-piast" 280ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 167ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 782ms
Then Login as "super-admin-piast" 2s 529ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 401ms
After Hooks.deleteTransportAfterApiTest() 602ms
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" 288ms
And Set token of apiUsername "super-admin-piast" 275ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 116ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 678ms
Then Login as "super-admin-piast" 2s 540ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 376ms
After Hooks.deleteTransportAfterApiTest() 625ms
After Hooks.rollbackSettings() 100ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 297ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
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" 279ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 702ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 996ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 618ms
After Hooks.rollbackSettings() 124ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 282ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
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" 286ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 802ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 905ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 597ms
After Hooks.rollbackSettings() 133ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 290ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 148ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 289ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 699ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 399ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 626ms
After Hooks.rollbackSettings() 128ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 281ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 150ms
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" 290ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 688ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 029ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 584ms
After Hooks.rollbackSettings() 139ms
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 932ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
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 759ms
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 687ms
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" 375ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 236ms
After Hooks.rollbackSettings() 092ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 293ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 155ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 302ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 675ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 240ms
After Hooks.deleteTransportAfterApiTest() 607ms
After Hooks.rollbackSettings() 126ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 285ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 155ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 397ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 654ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 008ms
And Show all transport types 1s 174ms
And Click button advice in transport table "DELIVERY" 286ms
And Set advice window in schedule 3s 771ms
And Fill advice form 13s 327ms
And Click advice save button and wait for advice form to disappear 33s 287ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 802ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 454ms
And Go to transport details "DELIVERY" 2s 914ms
And Expand advice panel 560ms
Then Check are transport values equals 2s 389ms
After Hooks.deleteTransportAfterApiTest() 832ms
After Hooks.rollbackSettings() 133ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 300ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 105ms
And Mark custom fields as not obligatory 005ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 134ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 151ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 6s 967ms
Then Login as "neuca-admin" 2s 344ms
And Go to "TRANSPORT_TABLE" 492ms
And Confirm statuses until reach "process-ended" 21s 388ms
Then Check if sorting by 'Finished' status is working correctly 285ms
After Hooks.deleteTransportsAfterTest() 4s 177ms
After Hooks.rollbackAllCustomFieldsSettings() 332ms
After Hooks.rollbackSettings() 103ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 271ms
And Delete invitations with email "automaty31415@test.pl" 091ms
And If user is login then logout 259ms
Given Set token of apiUsername "super-admin-piast" 310ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 148ms
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 463ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 926ms
Then Go to "INVITATIONS_TAB" 485ms
And Go to "EXPIRED_TAB" invitation status tab 234ms
Then Invitation is displayed on list "automaty31415@test.pl" 417ms
After Hooks.deleteInvitationAfterTest() 142ms
After Hooks.rollbackSettings() 125ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 280ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 131ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 301ms
And Prepare setting for automatic time window delete with "super-admin-skz" 216ms
When Login as "swisskrono-admin" 7s 887ms
And Go to "WAREHOUSE_TAB" 906ms
Then Check if dedicated window is deleted from schedule 1m 18s 465ms
After Hooks.rollbackSettings() 188ms
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 257ms
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" 202ms
And Set proper delay time to move order to archive after task timeout 149ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 924ms
And Go to "WAREHOUSE_TAB" 917ms
And Change warehouse in schedule to: "Katowice" 1s 173ms
And Wait "60" seconds 1m
And Verify that transport window is grey 070ms
And Verify that transport is in archive 7s 568ms
Then Restore transport from archive 2s 646ms
And Verify that transport has been successfully restored 1s 803ms
After Hooks.deleteTransportAfterTest() 735ms
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" 255ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 116ms
And Mark custom fields as not obligatory 006ms
And Login as "dayco-admin" 2s 317ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 013ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 134ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 245ms
When Go to "TRANSPORT_TABLE" 381ms
And Click button advice in transport table "OWN_COLLECTION" 1s 307ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 171ms
And Go to "TRANSPORT_TABLE" 355ms
And Find transport in table with status "planned-magazyn-tychy" 3s 667ms
And Confirm statuses until reach "process-ended" 16s 600ms
And Wait until transport disappear from transport table 37s 441ms
Then Go to "ARCHIVE_TAB" 503ms
And Show "OWN_COLLECTION" 172ms
And Verify that created transport is "true" in transport table 15s 166ms
After Hooks.deleteTransportAfterTest() 688ms
After Hooks.rollbackAllCustomFieldsSettings() 575ms
After Hooks.rollbackSettings() 137ms