Project Number Date
ApolloFullRunnerReport apollo-test-2.112 10 sie 2021, 05:53

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 6s 506ms 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" 246ms
And Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 184ms
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 575ms
Then Login as "super-admin-piast" 4s 356ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 424ms
After Hooks.deleteTransportAfterApiTest() 681ms
After Hooks.rollbackSettings() 189ms
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" 388ms
And Set token of apiUsername "super-admin-piast" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 169ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 174ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 553ms
Then Login as "super-admin-piast" 2s 431ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 385ms
After Hooks.deleteTransportAfterApiTest() 677ms
After Hooks.rollbackSettings() 149ms
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" 233ms
And Set token of apiUsername "super-admin-piast" 217ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 132ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 649ms
Then Login as "super-admin-piast" 2s 496ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 358ms
After Hooks.deleteTransportAfterApiTest() 676ms
After Hooks.rollbackSettings() 106ms
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" 133ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 176ms
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 579ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 723ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 668ms
After Hooks.rollbackSettings() 143ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 252ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 155ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 140ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 229ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 513ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 770ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 671ms
After Hooks.rollbackSettings() 135ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
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" 160ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 236ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 538ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 360ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 661ms
After Hooks.rollbackSettings() 129ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 238ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 153ms
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" 234ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 547ms
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() 653ms
After Hooks.rollbackSettings() 144ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 126ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 153ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 239ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 526ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 290ms
After Hooks.deleteTransportAfterApiTest() 659ms
After Hooks.rollbackSettings() 133ms
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" 149ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 257ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 663ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 522ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 802ms
And Show all transport types 1s 162ms
And Click button advice in transport table "DELIVERY" 269ms
And Set advice window in schedule 3s 949ms
And Fill advice form 13s 446ms
And Click advice save button and wait for advice form to disappear 33s 895ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 732ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 488ms
And Go to transport details "DELIVERY" 2s 936ms
And Expand advice panel 675ms
Then Check are transport values equals 2s 389ms
After Hooks.deleteTransportAfterApiTest() 864ms
After Hooks.rollbackSettings() 134ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 225ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 110ms
And Mark custom fields as not obligatory 005ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 112ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 104ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 6s 950ms
Then Login as "neuca-admin" 2s 213ms
And Go to "TRANSPORT_TABLE" 487ms
And Confirm statuses until reach "process-ended" 21s 610ms
Then Check if sorting by 'Finished' status is working correctly 324ms
After Hooks.deleteTransportsAfterTest() 4s 505ms
After Hooks.rollbackAllCustomFieldsSettings() 340ms
After Hooks.rollbackSettings() 110ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 221ms
And Delete invitations with email "automaty31415@test.pl" 092ms
And If user is login then logout 264ms
Given Set token of apiUsername "super-admin-piast" 268ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 172ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 242ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 420ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 700ms
Then Go to "INVITATIONS_TAB" 479ms
And Go to "EXPIRED_TAB" invitation status tab 233ms
Then Invitation is displayed on list "automaty31415@test.pl" 428ms
After Hooks.deleteInvitationAfterTest() 146ms
After Hooks.rollbackSettings() 129ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 231ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 129ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 324ms
And Prepare setting for automatic time window delete with "super-admin-skz" 210ms
When Login as "swisskrono-admin" 7s 843ms
And Go to "WAREHOUSE_TAB" 908ms
Then Check if dedicated window is deleted from schedule 48s 453ms
After Hooks.rollbackSettings() 171ms
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 498ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 018ms
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 168ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 928ms
And Go to "WAREHOUSE_TAB" 1s 169ms
And Change warehouse in schedule to: "Katowice" 4s 508ms
And Wait "60" seconds 1m
And Verify that transport window is grey 076ms
And Verify that transport is in archive 7s 409ms
Then Restore transport from archive 2s 785ms
And Verify that transport has been successfully restored 1s 810ms
After Hooks.deleteTransportAfterTest() 817ms
After Hooks.rollbackSettings() 120ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 218ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 124ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 253ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 100ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 130ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 208ms
When Go to "TRANSPORT_TABLE" 354ms
And Click button advice in transport table "OWN_COLLECTION" 1s 288ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 48s 121ms
And Go to "TRANSPORT_TABLE" 443ms
And Find transport in table with status "planned-magazyn-tychy" 3s 690ms
And Confirm statuses until reach "process-ended" 16s 712ms
And Wait until transport disappear from transport table 40s 529ms
Then Go to "ARCHIVE_TAB" 544ms
And Show "OWN_COLLECTION" 162ms
And Verify that created transport is "true" in transport table 15s 140ms
After Hooks.deleteTransportAfterTest() 698ms
After Hooks.rollbackAllCustomFieldsSettings() 597ms
After Hooks.rollbackSettings() 164ms