Project Number Date
ApolloFullRunnerReport apollo-test-2.162 18 wrz 2021, 06:45

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@rollbackSettings 164 0 0 0 0 164 19 0 19 8m 1s 965ms Passed
View Feature Public Api - Statuses confirmation
@deleteTransportAfterTest @rollbackSettings @TmsLink=A-8210
Before Hooks.showScenarioName(Scenario) 037ms
Given Set token of apiUsername "super-admin-piast" 1s 123ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 861ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 419ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 17s 377ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 5s 589ms
And Confirm status "ADVICE" by Public API "v1" and expect "422" 615ms
Then Check if response message contains "Nie można potwierdzić statusu ADVICE. Status ten został już potwierdzony wcześniej." in "errors" on status confirmation 007ms
After Hooks.deleteTransportAfterTest() 1s 206ms
After Hooks.rollbackSettings() 204ms
View Feature Public Api - Statuses confirmation
@deleteTransportAfterTest @rollbackSettings @TmsLink=A-8210
Before Hooks.showScenarioName(Scenario) 008ms
Given Set token of apiUsername "super-admin-piast" 346ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 161ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 182ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 16s 020ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 4s 001ms
And Confirm status "ORDER_CREATION" by Public API "v1" and expect "422" 263ms
Then Check if response message contains "Nie można potwierdzić statusu ORDER_CREATION. Status ten został już potwierdzony wcześniej." in "errors" on status confirmation 008ms
After Hooks.deleteTransportAfterTest() 1s 023ms
After Hooks.rollbackSettings() 135ms
View Feature Public Api - Statuses confirmation
@deleteTransportAfterTest @rollbackSettings @TmsLink=A-8210
Before Hooks.showScenarioName(Scenario) 008ms
Given Set token of apiUsername "super-admin-piast" 301ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 173ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 163ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 15s 960ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 4s 020ms
And Confirm status "BAD_STATUS_NAME" by Public API "v1" and expect "422" 259ms
Then Check if response message contains "Nie można potwierdzić statusu. Nie znaleziono wybranego statusu." in "errors" on status confirmation 007ms
After Hooks.deleteTransportAfterTest() 988ms
After Hooks.rollbackSettings() 139ms
View Feature Public Api - Statuses confirmation
@deleteTransportAfterTest @rollbackSettings @TmsLink=A-8210
Before Hooks.showScenarioName(Scenario) 006ms
Given Set token of apiUsername "super-admin-piast" 313ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 167ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP" with "super-admin-piast" 168ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 15s 937ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 4s 008ms
And Confirm status "ARRIVAL" by Public API "v1" and expect "404" 108ms
Then Check if response message contains "Nie znaleziono transportu o podanym identyfikatorze" in "text" on status confirmation 009ms
After Hooks.deleteTransportAfterTest() 1s 251ms
After Hooks.rollbackSettings() 147ms
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" 285ms
And Set token of apiUsername "super-admin-piast" 294ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 159ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 716ms
Then Login as "super-admin-piast" 6s 699ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 411ms
After Hooks.deleteTransportAfterApiTest() 643ms
After Hooks.rollbackSettings() 135ms
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" 283ms
And Set token of apiUsername "super-admin-piast" 286ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 147ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 778ms
Then Login as "super-admin-piast" 2s 445ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 410ms
After Hooks.deleteTransportAfterApiTest() 652ms
After Hooks.rollbackSettings() 136ms
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" 295ms
And Set token of apiUsername "super-admin-piast" 296ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 128ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 729ms
Then Login as "super-admin-piast" 2s 520ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 376ms
After Hooks.deleteTransportAfterApiTest() 671ms
After Hooks.rollbackSettings() 104ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 310ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
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" 305ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 923ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 755ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 662ms
After Hooks.rollbackSettings() 133ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 295ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 149ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 145ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 296ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 764ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 911ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 635ms
After Hooks.rollbackSettings() 127ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 290ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 143ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 152ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 294ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 724ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 383ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 637ms
After Hooks.rollbackSettings() 136ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 297ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 135ms
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" 281ms
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" as "super-admin-piast" with "invalidToken" for api version "v1" 033ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 640ms
After Hooks.rollbackSettings() 137ms
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 869ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 136ms
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 700ms
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 814ms
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" 390ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 353ms
After Hooks.rollbackSettings() 098ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 286ms
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" 303ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 776ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 227ms
After Hooks.deleteTransportAfterApiTest() 615ms
After Hooks.rollbackSettings() 134ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 277ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 152ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 338ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 745ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 009ms
And Show all transport types 1s 173ms
And Click button advice in transport table "DELIVERY" 203ms
And Set advice window in schedule 3s 613ms
And Fill advice form 13s 588ms
And Click advice save button and wait for advice form to disappear 33s 912ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 826ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 466ms
And Go to transport details "DELIVERY" 2s 931ms
And Expand advice panel 561ms
Then Check are transport values equals 2s 379ms
After Hooks.deleteTransportAfterApiTest() 875ms
After Hooks.rollbackSettings() 139ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 266ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 101ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 133ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 109ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 264ms
Then Login as "neuca-admin" 2s 388ms
And Go to "TRANSPORT_TABLE" 508ms
And Confirm statuses until reach "process-ended" 22s 439ms
Then Check if sorting by 'Finished' status is working correctly 295ms
After Hooks.deleteTransportsAfterTest() 4s 544ms
After Hooks.rollbackAllCustomFieldsSettings() 341ms
After Hooks.rollbackSettings() 106ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 272ms
And Delete invitations with email "automaty31415@test.pl" 092ms
And If user is login then logout 521ms
Given Set token of apiUsername "super-admin-piast" 294ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 129ms
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 499ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 870ms
Then Go to "INVITATIONS_TAB" 445ms
And Go to "EXPIRED_TAB" invitation status tab 228ms
Then Invitation is displayed on list "automaty31415@test.pl" 408ms
After Hooks.deleteInvitationAfterTest() 165ms
After Hooks.rollbackSettings() 129ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 269ms
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" 358ms
And Prepare setting for automatic time window delete with "super-admin-skz" 245ms
When Login as "swisskrono-admin" 7s 710ms
And Go to "WAREHOUSE_TAB" 856ms
Then Check if dedicated window is deleted from schedule 51s 188ms
After Hooks.rollbackSettings() 194ms
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" 7s 185ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 020ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 153ms
And Set proper delay time to move order to archive after task timeout 145ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 994ms
And Go to "WAREHOUSE_TAB" 931ms
And Change warehouse in schedule to: "Katowice" 1s 178ms
And Wait "60" seconds 1m
And Verify that transport window is grey 071ms
And Verify that transport is in archive 7s 632ms
Then Restore transport from archive 2s 681ms
And Verify that transport has been successfully restored 1s 763ms
After Hooks.deleteTransportAfterTest() 812ms
After Hooks.rollbackSettings() 112ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 276ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 113ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 274ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 145ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 137ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 180ms
When Go to "TRANSPORT_TABLE" 408ms
And Click button advice in transport table "OWN_COLLECTION" 1s 212ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 735ms
And Go to "TRANSPORT_TABLE" 375ms
And Find transport in table with status "planned-magazyn-tychy" 3s 682ms
And Confirm statuses until reach "process-ended" 16s 755ms
And Wait until transport disappear from transport table 40s 403ms
Then Go to "ARCHIVE_TAB" 556ms
And Show "OWN_COLLECTION" 185ms
And Verify that created transport is "true" in transport table 15s 162ms
After Hooks.deleteTransportAfterTest() 730ms
After Hooks.rollbackAllCustomFieldsSettings() 562ms
After Hooks.rollbackSettings() 143ms