Project Number Date
ApolloFullRunnerReport apollo-test-2.136 28 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 26s 454ms 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" 242ms
And Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 177ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 289ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 782ms
Then Login as "super-admin-piast" 5s 326ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 428ms
After Hooks.deleteTransportAfterApiTest() 672ms
After Hooks.rollbackSettings() 171ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 236ms
And Set token of apiUsername "super-admin-piast" 268ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 123ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 173ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 699ms
Then Login as "super-admin-piast" 2s 503ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 378ms
After Hooks.deleteTransportAfterApiTest() 674ms
After Hooks.rollbackSettings() 137ms
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" 229ms
And Set token of apiUsername "super-admin-piast" 236ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 122ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 700ms
Then Login as "super-admin-piast" 2s 526ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 403ms
After Hooks.deleteTransportAfterApiTest() 727ms
After Hooks.rollbackSettings() 106ms
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" 154ms
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 623ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 897ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 663ms
After Hooks.rollbackSettings() 151ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 231ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
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" 235ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 694ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 877ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 626ms
After Hooks.rollbackSettings() 144ms
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" 165ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 168ms
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 715ms
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() 641ms
After Hooks.rollbackSettings() 132ms
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" 131ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 155ms
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 678ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 030ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 644ms
After Hooks.rollbackSettings() 133ms
View Feature API Transport
@deleteApiTransportsAfterTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 865ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 152ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 134ms
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 680ms
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 619ms
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" 345ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 291ms
After Hooks.rollbackSettings() 091ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 132ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 173ms
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 627ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 273ms
After Hooks.deleteTransportAfterApiTest() 641ms
After Hooks.rollbackSettings() 127ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 233ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 163ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 3s 033ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 638ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 009ms
And Show all transport types 1s 179ms
And Click button advice in transport table "DELIVERY" 246ms
And Set advice window in schedule 4s 194ms
And Fill advice form 13s 305ms
And Click advice save button and wait for advice form to disappear 33s 944ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 780ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 477ms
And Go to transport details "DELIVERY" 2s 933ms
And Expand advice panel 603ms
Then Check are transport values equals 2s 436ms
After Hooks.deleteTransportAfterApiTest() 904ms
After Hooks.rollbackSettings() 163ms
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 111ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 127ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 135ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 102ms
Then Login as "neuca-admin" 2s 230ms
And Go to "TRANSPORT_TABLE" 506ms
And Confirm statuses until reach "process-ended" 21s 551ms
Then Check if sorting by 'Finished' status is working correctly 310ms
After Hooks.deleteTransportsAfterTest() 4s 515ms
After Hooks.rollbackAllCustomFieldsSettings() 338ms
After Hooks.rollbackSettings() 106ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 223ms
And Delete invitations with email "automaty31415@test.pl" 091ms
And If user is login then logout 274ms
Given Set token of apiUsername "super-admin-piast" 244ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 135ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 204ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 393ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 586ms
Then Go to "INVITATIONS_TAB" 509ms
And Go to "EXPIRED_TAB" invitation status tab 291ms
Then Invitation is displayed on list "automaty31415@test.pl" 463ms
After Hooks.deleteInvitationAfterTest() 154ms
After Hooks.rollbackSettings() 125ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 236ms
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" 335ms
And Prepare setting for automatic time window delete with "super-admin-skz" 225ms
When Login as "swisskrono-admin" 7s 923ms
And Go to "WAREHOUSE_TAB" 909ms
Then Check if dedicated window is deleted from schedule 51s 236ms
After Hooks.rollbackSettings() 190ms
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 810ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 021ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 174ms
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" 2s 035ms
And Go to "WAREHOUSE_TAB" 964ms
And Change warehouse in schedule to: "Katowice" 1s 605ms
And Wait "60" seconds 1m
And Verify that transport window is grey 095ms
And Verify that transport is in archive 7s 755ms
Then Restore transport from archive 2s 658ms
And Verify that transport has been successfully restored 1s 784ms
After Hooks.deleteTransportAfterTest() 874ms
After Hooks.rollbackSettings() 125ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 214ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 129ms
And Mark custom fields as not obligatory 006ms
And Login as "dayco-admin" 2s 172ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 196ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 125ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 211ms
When Go to "TRANSPORT_TABLE" 406ms
And Click button advice in transport table "OWN_COLLECTION" 1s 153ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 667ms
And Go to "TRANSPORT_TABLE" 356ms
And Find transport in table with status "planned-magazyn-tychy" 3s 748ms
And Confirm statuses until reach "process-ended" 16s 743ms
And Wait until transport disappear from transport table 37s 602ms
Then Go to "ARCHIVE_TAB" 565ms
And Show "OWN_COLLECTION" 178ms
And Verify that created transport is "true" in transport table 15s 171ms
After Hooks.deleteTransportAfterTest() 719ms
After Hooks.rollbackAllCustomFieldsSettings() 590ms
After Hooks.rollbackSettings() 143ms