Project Number Date
ApolloFullRunnerReport apollo-test-2.161 17 wrz 2021, 07:00

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 25s 192ms Passed
View Feature Public Api - Statuses confirmation
@deleteTransportAfterTest @rollbackSettings @TmsLink=A-8210
Before Hooks.showScenarioName(Scenario) 046ms
Given Set token of apiUsername "super-admin-piast" 1s 133ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 709ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 384ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 17s 281ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 5s 642ms
And Confirm status "ADVICE" by Public API "v1" and expect "422" 731ms
Then Check if response message contains "Nie można potwierdzić statusu ADVICE. Status ten został już potwierdzony wcześniej." in "errors" on status confirmation 008ms
After Hooks.deleteTransportAfterTest() 1s 206ms
After Hooks.rollbackSettings() 176ms
View Feature Public Api - Statuses confirmation
@deleteTransportAfterTest @rollbackSettings @TmsLink=A-8210
Before Hooks.showScenarioName(Scenario) 005ms
Given Set token of apiUsername "super-admin-piast" 300ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 203ms
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 085ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 4s 224ms
And Confirm status "ORDER_CREATION" by Public API "v1" and expect "422" 252ms
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 035ms
After Hooks.rollbackSettings() 155ms
View Feature Public Api - Statuses confirmation
@deleteTransportAfterTest @rollbackSettings @TmsLink=A-8210
Before Hooks.showScenarioName(Scenario) 008ms
Given Set token of apiUsername "super-admin-piast" 326ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 156ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 162ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 16s 002ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 3s 929ms
And Confirm status "BAD_STATUS_NAME" by Public API "v1" and expect "422" 289ms
Then Check if response message contains "Nie można potwierdzić statusu. Nie znaleziono wybranego statusu." in "errors" on status confirmation 006ms
After Hooks.deleteTransportAfterTest() 993ms
After Hooks.rollbackSettings() 131ms
View Feature Public Api - Statuses confirmation
@deleteTransportAfterTest @rollbackSettings @TmsLink=A-8210
Before Hooks.showScenarioName(Scenario) 005ms
Given Set token of apiUsername "super-admin-piast" 288ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 148ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP" with "super-admin-piast" 163ms
And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 15s 981ms
And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 4s 067ms
And Confirm status "ARRIVAL" by Public API "v1" and expect "404" 121ms
Then Check if response message contains "Nie znaleziono transportu o podanym identyfikatorze" in "text" on status confirmation 009ms
After Hooks.deleteTransportAfterTest() 969ms
After Hooks.rollbackSettings() 140ms
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" 294ms
And Set token of apiUsername "super-admin-piast" 289ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 153ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 697ms
Then Login as "super-admin-piast" 6s 624ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 387ms
After Hooks.deleteTransportAfterApiTest() 670ms
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" 288ms
And Set token of apiUsername "super-admin-piast" 288ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 133ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 153ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 754ms
Then Login as "super-admin-piast" 2s 516ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 383ms
After Hooks.deleteTransportAfterApiTest() 627ms
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" 304ms
And Set token of apiUsername "super-admin-piast" 279ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 157ms
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 766ms
Then Login as "super-admin-piast" 2s 684ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 424ms
After Hooks.deleteTransportAfterApiTest() 644ms
After Hooks.rollbackSettings() 108ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 267ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 161ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 156ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 283ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 726ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 694ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 631ms
After Hooks.rollbackSettings() 138ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 292ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms
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" 283ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 753ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 973ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 612ms
After Hooks.rollbackSettings() 135ms
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" 129ms
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" 303ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 750ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 427ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 670ms
After Hooks.rollbackSettings() 129ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 270ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
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" 270ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 824ms
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() 659ms
After Hooks.rollbackSettings() 134ms
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" 3s 014ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 115ms
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 670ms
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 726ms
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" 388ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 249ms
After Hooks.rollbackSettings() 094ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 276ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
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" 284ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 717ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 215ms
After Hooks.deleteTransportAfterApiTest() 612ms
After Hooks.rollbackSettings() 129ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 288ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
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" 6s 567ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 727ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 011ms
And Show all transport types 1s 183ms
And Click button advice in transport table "DELIVERY" 259ms
And Set advice window in schedule 3s 709ms
And Fill advice form 13s 471ms
And Click advice save button and wait for advice form to disappear 33s 403ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 779ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 498ms
And Go to transport details "DELIVERY" 2s 909ms
And Expand advice panel 578ms
Then Check are transport values equals 2s 416ms
After Hooks.deleteTransportAfterApiTest() 868ms
After Hooks.rollbackSettings() 137ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 258ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 113ms
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" 125ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 111ms
Then Login as "neuca-admin" 2s 337ms
And Go to "TRANSPORT_TABLE" 508ms
And Confirm statuses until reach "process-ended" 21s 520ms
Then Check if sorting by 'Finished' status is working correctly 259ms
After Hooks.deleteTransportsAfterTest() 4s 521ms
After Hooks.rollbackAllCustomFieldsSettings() 354ms
After Hooks.rollbackSettings() 118ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 281ms
And Delete invitations with email "automaty31415@test.pl" 102ms
And If user is login then logout 261ms
Given Set token of apiUsername "super-admin-piast" 304ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 140ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 254ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 514ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 841ms
Then Go to "INVITATIONS_TAB" 494ms
And Go to "EXPIRED_TAB" invitation status tab 303ms
Then Invitation is displayed on list "automaty31415@test.pl" 445ms
After Hooks.deleteInvitationAfterTest() 142ms
After Hooks.rollbackSettings() 134ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 276ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 119ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 339ms
And Prepare setting for automatic time window delete with "super-admin-skz" 240ms
When Login as "swisskrono-admin" 7s 511ms
And Go to "WAREHOUSE_TAB" 883ms
Then Check if dedicated window is deleted from schedule 1m 15s 141ms
After Hooks.rollbackSettings() 197ms
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 144ms
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" 169ms
And Set proper delay time to move order to archive after task timeout 148ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 973ms
And Go to "WAREHOUSE_TAB" 893ms
And Change warehouse in schedule to: "Katowice" 1s 145ms
And Wait "60" seconds 1m
And Verify that transport window is grey 073ms
And Verify that transport is in archive 7s 629ms
Then Restore transport from archive 2s 663ms
And Verify that transport has been successfully restored 1s 753ms
After Hooks.deleteTransportAfterTest() 783ms
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" 290ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 113ms
And Mark custom fields as not obligatory 006ms
And Login as "dayco-admin" 2s 260ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 076ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 120ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 171ms
When Go to "TRANSPORT_TABLE" 390ms
And Click button advice in transport table "OWN_COLLECTION" 1s 351ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 722ms
And Go to "TRANSPORT_TABLE" 365ms
And Find transport in table with status "planned-magazyn-tychy" 3s 696ms
And Confirm statuses until reach "process-ended" 16s 662ms
And Wait until transport disappear from transport table 40s 403ms
Then Go to "ARCHIVE_TAB" 550ms
And Show "OWN_COLLECTION" 179ms
And Verify that created transport is "true" in transport table 15s 132ms
After Hooks.deleteTransportAfterTest() 722ms
After Hooks.rollbackAllCustomFieldsSettings() 572ms
After Hooks.rollbackSettings() 148ms