Project Number Date
ApolloFullRunnerReport apollo-test-2.130 24 sie 2021, 05:52

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 48s 021ms 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" 239ms
And Set token of apiUsername "super-admin-piast" 233ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 147ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 226ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 748ms
Then Login as "super-admin-piast" 5s 493ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 389ms
After Hooks.deleteTransportAfterApiTest() 688ms
After Hooks.rollbackSettings() 195ms
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" 253ms
And Set token of apiUsername "super-admin-piast" 259ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 150ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 172ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 779ms
Then Login as "super-admin-piast" 2s 536ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 414ms
After Hooks.deleteTransportAfterApiTest() 666ms
After Hooks.rollbackSettings() 146ms
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" 257ms
And Set token of apiUsername "super-admin-piast" 251ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 159ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 126ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 703ms
Then Login as "super-admin-piast" 2s 576ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 391ms
After Hooks.deleteTransportAfterApiTest() 667ms
After Hooks.rollbackSettings() 111ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 255ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 161ms
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 663ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 878ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 666ms
After Hooks.rollbackSettings() 129ms
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" 156ms
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" 245ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 767ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 851ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 645ms
After Hooks.rollbackSettings() 131ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 262ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 164ms
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 698ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 331ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 634ms
After Hooks.rollbackSettings() 124ms
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" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 166ms
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 663ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 036ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 684ms
After Hooks.rollbackSettings() 125ms
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 955ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 151ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 129ms
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 674ms
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 631ms
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" 336ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 256ms
After Hooks.rollbackSettings() 101ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
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" 247ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 697ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 264ms
After Hooks.deleteTransportAfterApiTest() 619ms
After Hooks.rollbackSettings() 139ms
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" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 167ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 630ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 682ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 019ms
And Show all transport types 1s 164ms
And Click button advice in transport table "DELIVERY" 267ms
And Set advice window in schedule 3s 781ms
And Fill advice form 13s 278ms
And Click advice save button and wait for advice form to disappear 33s 907ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 689ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 489ms
And Go to transport details "DELIVERY" 3s 103ms
And Expand advice panel 603ms
Then Check are transport values equals 2s 369ms
After Hooks.deleteTransportAfterApiTest() 812ms
After Hooks.rollbackSettings() 135ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 239ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 108ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 116ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 134ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 229ms
Then Login as "neuca-admin" 2s 385ms
And Go to "TRANSPORT_TABLE" 509ms
And Confirm statuses until reach "process-ended" 21s 320ms
Then Check if sorting by 'Finished' status is working correctly 228ms
After Hooks.deleteTransportsAfterTest() 4s 473ms
After Hooks.rollbackAllCustomFieldsSettings() 341ms
After Hooks.rollbackSettings() 113ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 210ms
And Delete invitations with email "automaty31415@test.pl" 079ms
And If user is login then logout 224ms
Given Set token of apiUsername "super-admin-piast" 263ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 124ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 207ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 375ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 677ms
Then Go to "INVITATIONS_TAB" 531ms
And Go to "EXPIRED_TAB" invitation status tab 311ms
Then Invitation is displayed on list "automaty31415@test.pl" 460ms
After Hooks.deleteInvitationAfterTest() 157ms
After Hooks.rollbackSettings() 123ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 235ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 144ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 315ms
And Prepare setting for automatic time window delete with "super-admin-skz" 242ms
When Login as "swisskrono-admin" 7s 672ms
And Go to "WAREHOUSE_TAB" 926ms
Then Check if dedicated window is deleted from schedule 1m 24s 459ms
After Hooks.rollbackSettings() 195ms
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 728ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 016ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 131ms
And Set proper delay time to move order to archive after task timeout 137ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 891ms
And Go to "WAREHOUSE_TAB" 893ms
And Change warehouse in schedule to: "Katowice" 2s 003ms
And Wait "60" seconds 1m
And Verify that transport window is grey 080ms
And Verify that transport is in archive 7s 135ms
Then Restore transport from archive 2s 909ms
And Verify that transport has been successfully restored 1s 814ms
After Hooks.deleteTransportAfterTest() 756ms
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" 235ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 121ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 315ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 047ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 136ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 201ms
When Go to "TRANSPORT_TABLE" 363ms
And Click button advice in transport table "OWN_COLLECTION" 1s 358ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 641ms
And Go to "TRANSPORT_TABLE" 365ms
And Find transport in table with status "planned-magazyn-tychy" 3s 718ms
And Confirm statuses until reach "process-ended" 16s 720ms
And Wait until transport disappear from transport table 22s 611ms
Then Go to "ARCHIVE_TAB" 588ms
And Show "OWN_COLLECTION" 188ms
And Verify that created transport is "true" in transport table 15s 156ms
After Hooks.deleteTransportAfterTest() 693ms
After Hooks.rollbackAllCustomFieldsSettings() 539ms
After Hooks.rollbackSettings() 144ms