Project Number Date
ApolloFullRunnerReport apollo-test-2.138 30 sie 2021, 06:02

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 30s 958ms 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" 230ms
And Set token of apiUsername "super-admin-piast" 236ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 386ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 259ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 783ms
Then Login as "super-admin-piast" 5s 435ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 500ms
After Hooks.deleteTransportAfterApiTest() 580ms
After Hooks.rollbackSettings() 176ms
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" 251ms
And Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 169ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 160ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 724ms
Then Login as "super-admin-piast" 2s 419ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 388ms
After Hooks.deleteTransportAfterApiTest() 667ms
After Hooks.rollbackSettings() 138ms
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" 236ms
And Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 135ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 796ms
Then Login as "super-admin-piast" 2s 451ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 407ms
After Hooks.deleteTransportAfterApiTest() 654ms
After Hooks.rollbackSettings() 099ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 246ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 163ms
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 676ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 955ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 650ms
After Hooks.rollbackSettings() 135ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 139ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 172ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 235ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 757ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 918ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 643ms
After Hooks.rollbackSettings() 137ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 259ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 157ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 164ms
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 771ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 345ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 647ms
After Hooks.rollbackSettings() 137ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
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" 256ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 691ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 031ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 678ms
After Hooks.rollbackSettings() 144ms
View Feature API Transport
@deleteApiTransportsAfterTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 960ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 149ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 126ms
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 671ms
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" 340ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 315ms
After Hooks.rollbackSettings() 109ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 239ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 139ms
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 676ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 267ms
After Hooks.deleteTransportAfterApiTest() 628ms
After Hooks.rollbackSettings() 129ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 253ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 134ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 171ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 832ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 700ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 008ms
And Show all transport types 1s 197ms
And Click button advice in transport table "DELIVERY" 222ms
And Set advice window in schedule 3s 902ms
And Fill advice form 13s 338ms
And Click advice save button and wait for advice form to disappear 33s 825ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 722ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 513ms
And Go to transport details "DELIVERY" 2s 911ms
And Expand advice panel 573ms
Then Check are transport values equals 2s 401ms
After Hooks.deleteTransportAfterApiTest() 885ms
After Hooks.rollbackSettings() 139ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 222ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 110ms
And Mark custom fields as not obligatory 007ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 145ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 121ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 118ms
Then Login as "neuca-admin" 2s 329ms
And Go to "TRANSPORT_TABLE" 532ms
And Confirm statuses until reach "process-ended" 22s 392ms
Then Check if sorting by 'Finished' status is working correctly 302ms
After Hooks.deleteTransportsAfterTest() 4s 452ms
After Hooks.rollbackAllCustomFieldsSettings() 323ms
After Hooks.rollbackSettings() 109ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 224ms
And Delete invitations with email "automaty31415@test.pl" 093ms
And If user is login then logout 265ms
Given Set token of apiUsername "super-admin-piast" 249ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 138ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 213ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 425ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 819ms
Then Go to "INVITATIONS_TAB" 496ms
And Go to "EXPIRED_TAB" invitation status tab 289ms
Then Invitation is displayed on list "automaty31415@test.pl" 482ms
After Hooks.deleteInvitationAfterTest() 149ms
After Hooks.rollbackSettings() 129ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-skz" 220ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 128ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 326ms
And Prepare setting for automatic time window delete with "super-admin-skz" 219ms
When Login as "swisskrono-admin" 7s 834ms
And Go to "WAREHOUSE_TAB" 930ms
Then Check if dedicated window is deleted from schedule 51s 167ms
After Hooks.rollbackSettings() 189ms
View Feature Move transport to archive
@rollbackSettings @deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 610ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 020ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 150ms
And Set proper delay time to move order to archive after task timeout 157ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 909ms
And Go to "WAREHOUSE_TAB" 885ms
And Change warehouse in schedule to: "Katowice" 1s 558ms
And Wait "60" seconds 1m
And Verify that transport window is grey 087ms
And Verify that transport is in archive 7s 631ms
Then Restore transport from archive 2s 702ms
And Verify that transport has been successfully restored 1s 768ms
After Hooks.deleteTransportAfterTest() 771ms
After Hooks.rollbackSettings() 126ms
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 113ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 227ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 060ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 139ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 182ms
When Go to "TRANSPORT_TABLE" 359ms
And Click button advice in transport table "OWN_COLLECTION" 1s 356ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 533ms
And Go to "TRANSPORT_TABLE" 347ms
And Find transport in table with status "planned-magazyn-tychy" 3s 701ms
And Confirm statuses until reach "process-ended" 16s 635ms
And Wait until transport disappear from transport table 37s 599ms
Then Go to "ARCHIVE_TAB" 569ms
And Show "OWN_COLLECTION" 178ms
And Verify that created transport is "true" in transport table 15s 135ms
After Hooks.deleteTransportAfterTest() 712ms
After Hooks.rollbackAllCustomFieldsSettings() 563ms
After Hooks.rollbackSettings() 134ms