Project Number Date
ApolloFullRunnerReport apollo-test-2.114 12 sie 2021, 06:02

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 2s 759ms 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" 251ms
And Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 243ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 255ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 737ms
Then Login as "super-admin-piast" 8s 531ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 407ms
After Hooks.deleteTransportAfterApiTest() 581ms
After Hooks.rollbackSettings() 209ms
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" 266ms
And Set token of apiUsername "super-admin-piast" 281ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 171ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 627ms
Then Login as "super-admin-piast" 2s 432ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 418ms
After Hooks.deleteTransportAfterApiTest() 674ms
After Hooks.rollbackSettings() 153ms
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" 254ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 156ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 134ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 668ms
Then Login as "super-admin-piast" 2s 514ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 394ms
After Hooks.deleteTransportAfterApiTest() 660ms
After Hooks.rollbackSettings() 101ms
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" 142ms
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" 253ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 596ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 782ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 676ms
After Hooks.rollbackSettings() 147ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 249ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
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" 254ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 592ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 860ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 647ms
After Hooks.rollbackSettings() 126ms
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" 147ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 159ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 243ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 603ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 370ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 660ms
After Hooks.rollbackSettings() 138ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 160ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 242ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 615ms
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() 645ms
After Hooks.rollbackSettings() 122ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 251ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 134ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 185ms
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 612ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 274ms
After Hooks.deleteTransportAfterApiTest() 628ms
After Hooks.rollbackSettings() 137ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 236ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
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" 6s 333ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 565ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 657ms
And Show all transport types 1s 170ms
And Click button advice in transport table "DELIVERY" 260ms
And Set advice window in schedule 3s 806ms
And Fill advice form 13s 307ms
And Click advice save button and wait for advice form to disappear 33s 923ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 567ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 472ms
And Go to transport details "DELIVERY" 3s 003ms
And Expand advice panel 506ms
Then Check are transport values equals 2s 436ms
After Hooks.deleteTransportAfterApiTest() 924ms
After Hooks.rollbackSettings() 128ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 238ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 115ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 135ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 141ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 213ms
Then Login as "neuca-admin" 2s 367ms
And Go to "TRANSPORT_TABLE" 524ms
And Confirm statuses until reach "process-ended" 21s 509ms
Then Check if sorting by 'Finished' status is working correctly 270ms
After Hooks.deleteTransportsAfterTest() 4s 415ms
After Hooks.rollbackAllCustomFieldsSettings() 333ms
After Hooks.rollbackSettings() 107ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 239ms
And Delete invitations with email "automaty31415@test.pl" 094ms
And If user is login then logout 232ms
Given Set token of apiUsername "super-admin-piast" 258ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 152ms
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 450ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 741ms
Then Go to "INVITATIONS_TAB" 448ms
And Go to "EXPIRED_TAB" invitation status tab 277ms
Then Invitation is displayed on list "automaty31415@test.pl" 457ms
After Hooks.deleteInvitationAfterTest() 161ms
After Hooks.rollbackSettings() 122ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 215ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 135ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 297ms
And Prepare setting for automatic time window delete with "super-admin-skz" 217ms
When Login as "swisskrono-admin" 7s 952ms
And Go to "WAREHOUSE_TAB" 939ms
Then Check if dedicated window is deleted from schedule 35s 902ms
After Hooks.rollbackSettings() 180ms
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 503ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 022ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 145ms
And Set proper delay time to move order to archive after task timeout 150ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 908ms
And Go to "WAREHOUSE_TAB" 1s 145ms
And Change warehouse in schedule to: "Katowice" 4s 624ms
And Wait "60" seconds 1m
And Verify that transport window is grey 091ms
And Verify that transport is in archive 7s 334ms
Then Restore transport from archive 2s 875ms
And Verify that transport has been successfully restored 1s 812ms
After Hooks.deleteTransportAfterTest() 784ms
After Hooks.rollbackSettings() 121ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 228ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 121ms
And Mark custom fields as not obligatory 004ms
And Login as "dayco-admin" 2s 227ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 080ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 138ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 224ms
When Go to "TRANSPORT_TABLE" 354ms
And Click button advice in transport table "OWN_COLLECTION" 1s 271ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 48s 134ms
And Go to "TRANSPORT_TABLE" 469ms
And Find transport in table with status "planned-magazyn-tychy" 3s 824ms
And Confirm statuses until reach "process-ended" 16s 735ms
And Wait until transport disappear from transport table 40s 516ms
Then Go to "ARCHIVE_TAB" 521ms
And Show "OWN_COLLECTION" 174ms
And Verify that created transport is "true" in transport table 15s 141ms
After Hooks.deleteTransportAfterTest() 832ms
After Hooks.rollbackAllCustomFieldsSettings() 588ms
After Hooks.rollbackSettings() 141ms