Project Number Date
ApolloFullRunnerReport apollo-test-2.157 14 wrz 2021, 06:50

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 25s 751ms 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" 318ms
And Set token of apiUsername "super-admin-piast" 290ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 249ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 253ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 738ms
Then Login as "super-admin-piast" 7s 248ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 369ms
After Hooks.deleteTransportAfterApiTest() 631ms
After Hooks.rollbackSettings() 165ms
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" 299ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 163ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 169ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 735ms
Then Login as "super-admin-piast" 2s 594ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 394ms
After Hooks.deleteTransportAfterApiTest() 622ms
After Hooks.rollbackSettings() 136ms
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" 284ms
And 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: "ERP_IDENTIFIER" with "super-admin-piast" 123ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 784ms
Then Login as "super-admin-piast" 2s 524ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 365ms
After Hooks.deleteTransportAfterApiTest() 635ms
After Hooks.rollbackSettings() 095ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 281ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 167ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 282ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 695ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 939ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 633ms
After Hooks.rollbackSettings() 133ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 279ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
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" 281ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 733ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 896ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 592ms
After Hooks.rollbackSettings() 128ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 283ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 149ms
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" 286ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 761ms
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() 616ms
After Hooks.rollbackSettings() 136ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 296ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 157ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 152ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 303ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 667ms
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() 609ms
After Hooks.rollbackSettings() 127ms
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 906ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 128ms
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 675ms
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 730ms
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" 389ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 319ms
After Hooks.rollbackSettings() 093ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 288ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 156ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 288ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 709ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 241ms
After Hooks.deleteTransportAfterApiTest() 613ms
After Hooks.rollbackSettings() 130ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 279ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 151ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 947ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 667ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 010ms
And Show all transport types 1s 177ms
And Click button advice in transport table "DELIVERY" 276ms
And Set advice window in schedule 3s 672ms
And Fill advice form 13s 363ms
And Click advice save button and wait for advice form to disappear 33s 345ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 750ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 449ms
And Go to transport details "DELIVERY" 2s 899ms
And Expand advice panel 465ms
Then Check are transport values equals 2s 391ms
After Hooks.deleteTransportAfterApiTest() 814ms
After Hooks.rollbackSettings() 131ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 287ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 107ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 140ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 120ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 6s 869ms
Then Login as "neuca-admin" 2s 215ms
And Go to "TRANSPORT_TABLE" 489ms
And Confirm statuses until reach "process-ended" 21s 557ms
Then Check if sorting by 'Finished' status is working correctly 297ms
After Hooks.deleteTransportsAfterTest() 4s 220ms
After Hooks.rollbackAllCustomFieldsSettings() 334ms
After Hooks.rollbackSettings() 102ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 268ms
And Delete invitations with email "automaty31415@test.pl" 090ms
And If user is login then logout 273ms
Given Set token of apiUsername "super-admin-piast" 290ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 134ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 187ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 348ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 760ms
Then Go to "INVITATIONS_TAB" 539ms
And Go to "EXPIRED_TAB" invitation status tab 310ms
Then Invitation is displayed on list "automaty31415@test.pl" 426ms
After Hooks.deleteInvitationAfterTest() 153ms
After Hooks.rollbackSettings() 120ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 286ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 138ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 328ms
And Prepare setting for automatic time window delete with "super-admin-skz" 230ms
When Login as "swisskrono-admin" 7s 799ms
And Go to "WAREHOUSE_TAB" 884ms
Then Check if dedicated window is deleted from schedule 51s 291ms
After Hooks.rollbackSettings() 201ms
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 161ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 017ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 177ms
And Set proper delay time to move order to archive after task timeout 155ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 900ms
And Go to "WAREHOUSE_TAB" 967ms
And Change warehouse in schedule to: "Katowice" 1s 124ms
And Wait "60" seconds 1m
And Verify that transport window is grey 087ms
And Verify that transport is in archive 7s 621ms
Then Restore transport from archive 2s 779ms
And Verify that transport has been successfully restored 1s 786ms
After Hooks.deleteTransportAfterTest() 797ms
After Hooks.rollbackSettings() 188ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 268ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 116ms
And Mark custom fields as not obligatory 004ms
And Login as "dayco-admin" 2s 273ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 018ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 131ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 193ms
When Go to "TRANSPORT_TABLE" 358ms
And Click button advice in transport table "OWN_COLLECTION" 1s 384ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 262ms
And Go to "TRANSPORT_TABLE" 367ms
And Find transport in table with status "planned-magazyn-tychy" 3s 703ms
And Confirm statuses until reach "process-ended" 16s 693ms
And Wait until transport disappear from transport table 34s 615ms
Then Go to "ARCHIVE_TAB" 566ms
And Show "OWN_COLLECTION" 181ms
And Verify that created transport is "true" in transport table 15s 099ms
After Hooks.deleteTransportAfterTest() 722ms
After Hooks.rollbackAllCustomFieldsSettings() 603ms
After Hooks.rollbackSettings() 141ms