Project Number Date
ApolloFullRunnerReport apollo-test-2.123 18 sie 2021, 06:09

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@rollbackSettings 129 0 0 0 0 129 14 0 14 7m 22s 373ms 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" 249ms
And Set token of apiUsername "super-admin-piast" 244ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 177ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 270ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 586ms
Then Login as "super-admin-piast" 7s 721ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 416ms
After Hooks.deleteTransportAfterApiTest() 669ms
After Hooks.rollbackSettings() 184ms
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" 231ms
And Set token of apiUsername "super-admin-piast" 234ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 143ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 158ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 600ms
Then Login as "super-admin-piast" 2s 407ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 360ms
After Hooks.deleteTransportAfterApiTest() 589ms
After Hooks.rollbackSettings() 152ms
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" 241ms
And Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 121ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 684ms
Then Login as "super-admin-piast" 2s 534ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 369ms
After Hooks.deleteTransportAfterApiTest() 647ms
After Hooks.rollbackSettings() 129ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 230ms
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" 237ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 623ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 810ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 656ms
After Hooks.rollbackSettings() 189ms
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" 137ms
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" 224ms
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" 903ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 625ms
After Hooks.rollbackSettings() 139ms
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" 151ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 171ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 261ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 611ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 359ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 684ms
After Hooks.rollbackSettings() 137ms
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" 140ms
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" 225ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 607ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 032ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 625ms
After Hooks.rollbackSettings() 140ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 237ms
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" 240ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 578ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 252ms
After Hooks.deleteTransportAfterApiTest() 620ms
After Hooks.rollbackSettings() 124ms
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" 154ms
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" 5s 397ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 607ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 513ms
And Show all transport types 1s 168ms
And Click button advice in transport table "DELIVERY" 240ms
And Set advice window in schedule 3s 821ms
And Fill advice form 13s 281ms
And Click advice save button and wait for advice form to disappear 33s 883ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 522ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 513ms
And Go to transport details "DELIVERY" 2s 920ms
And Expand advice panel 489ms
Then Check are transport values equals 2s 415ms
After Hooks.deleteTransportAfterApiTest() 959ms
After Hooks.rollbackSettings() 131ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 216ms
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" 115ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 152ms
Then Login as "neuca-admin" 2s 381ms
And Go to "TRANSPORT_TABLE" 511ms
And Confirm statuses until reach "process-ended" 22s 445ms
Then Check if sorting by 'Finished' status is working correctly 303ms
After Hooks.deleteTransportsAfterTest() 4s 485ms
After Hooks.rollbackAllCustomFieldsSettings() 369ms
After Hooks.rollbackSettings() 104ms
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" 092ms
And If user is login then logout 271ms
Given Set token of apiUsername "super-admin-piast" 241ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 132ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 233ms
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 750ms
Then Go to "INVITATIONS_TAB" 495ms
And Go to "EXPIRED_TAB" invitation status tab 254ms
Then Invitation is displayed on list "automaty31415@test.pl" 411ms
After Hooks.deleteInvitationAfterTest() 158ms
After Hooks.rollbackSettings() 122ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 222ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 127ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 304ms
And Prepare setting for automatic time window delete with "super-admin-skz" 214ms
When Login as "swisskrono-admin" 7s 736ms
And Go to "WAREHOUSE_TAB" 935ms
Then Check if dedicated window is deleted from schedule 1m 167ms
After Hooks.rollbackSettings() 191ms
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 780ms
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" 133ms
And Set proper delay time to move order to archive after task timeout 151ms
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" 998ms
And Change warehouse in schedule to: "Katowice" 1s 759ms
And Wait "60" seconds 1m
And Verify that transport window is grey 073ms
And Verify that transport is in archive 7s 388ms
Then Restore transport from archive 2s 905ms
And Verify that transport has been successfully restored 1s 765ms
After Hooks.deleteTransportAfterTest() 751ms
After Hooks.rollbackSettings() 134ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 208ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 128ms
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 029ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 144ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 182ms
When Go to "TRANSPORT_TABLE" 395ms
And Click button advice in transport table "OWN_COLLECTION" 1s 314ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 48s 207ms
And Go to "TRANSPORT_TABLE" 477ms
And Find transport in table with status "planned-magazyn-tychy" 3s 722ms
And Confirm statuses until reach "process-ended" 16s 684ms
And Wait until transport disappear from transport table 40s 363ms
Then Go to "ARCHIVE_TAB" 540ms
And Show "OWN_COLLECTION" 187ms
And Verify that created transport is "true" in transport table 15s 126ms
After Hooks.deleteTransportAfterTest() 711ms
After Hooks.rollbackAllCustomFieldsSettings() 525ms
After Hooks.rollbackSettings() 125ms