Project Number Date
ApolloFullRunnerReport apollo-test-2.120 16 sie 2021, 06:00

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 38s 075ms 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" 233ms
And Set token of apiUsername "super-admin-piast" 228ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 148ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 295ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 579ms
Then Login as "super-admin-piast" 8s 424ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 381ms
After Hooks.deleteTransportAfterApiTest() 583ms
After Hooks.rollbackSettings() 203ms
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" 248ms
And Set token of apiUsername "super-admin-piast" 271ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 173ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 170ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 607ms
Then Login as "super-admin-piast" 2s 530ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 385ms
After Hooks.deleteTransportAfterApiTest() 662ms
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" 228ms
And Set token of apiUsername "super-admin-piast" 244ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 116ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 605ms
Then Login as "super-admin-piast" 2s 586ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 403ms
After Hooks.deleteTransportAfterApiTest() 696ms
After Hooks.rollbackSettings() 110ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 255ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
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" 244ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 675ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 732ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 645ms
After Hooks.rollbackSettings() 145ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 263ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 139ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 164ms
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 595ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 866ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 634ms
After Hooks.rollbackSettings() 122ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 133ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 158ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 259ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 630ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 335ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 636ms
After Hooks.rollbackSettings() 136ms
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" 134ms
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" 235ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 589ms
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() 640ms
After Hooks.rollbackSettings() 136ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 246ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 165ms
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 589ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 297ms
After Hooks.deleteTransportAfterApiTest() 624ms
After Hooks.rollbackSettings() 130ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 250ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 148ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 156ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 759ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 544ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 610ms
And Show all transport types 1s 177ms
And Click button advice in transport table "DELIVERY" 243ms
And Set advice window in schedule 3s 819ms
And Fill advice form 13s 277ms
And Click advice save button and wait for advice form to disappear 33s 933ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 514ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 499ms
And Go to transport details "DELIVERY" 2s 960ms
And Expand advice panel 548ms
Then Check are transport values equals 2s 367ms
After Hooks.deleteTransportAfterApiTest() 884ms
After Hooks.rollbackSettings() 136ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 220ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 112ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 130ms
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 209ms
Then Login as "neuca-admin" 2s 324ms
And Go to "TRANSPORT_TABLE" 535ms
And Confirm statuses until reach "process-ended" 21s 478ms
Then Check if sorting by 'Finished' status is working correctly 270ms
After Hooks.deleteTransportsAfterTest() 4s 545ms
After Hooks.rollbackAllCustomFieldsSettings() 358ms
After Hooks.rollbackSettings() 103ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 224ms
And Delete invitations with email "automaty31415@test.pl" 092ms
And If user is login then logout 234ms
Given Set token of apiUsername "super-admin-piast" 243ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 139ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 201ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 369ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 796ms
Then Go to "INVITATIONS_TAB" 491ms
And Go to "EXPIRED_TAB" invitation status tab 267ms
Then Invitation is displayed on list "automaty31415@test.pl" 478ms
After Hooks.deleteInvitationAfterTest() 152ms
After Hooks.rollbackSettings() 125ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 241ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 125ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 327ms
And Prepare setting for automatic time window delete with "super-admin-skz" 233ms
When Login as "swisskrono-admin" 7s 866ms
And Go to "WAREHOUSE_TAB" 986ms
Then Check if dedicated window is deleted from schedule 1m 15s 577ms
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 635ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 022ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 165ms
And Set proper delay time to move order to archive after task timeout 159ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 905ms
And Go to "WAREHOUSE_TAB" 1s 031ms
And Change warehouse in schedule to: "Katowice" 1s 724ms
And Wait "60" seconds 1m
And Verify that transport window is grey 086ms
And Verify that transport is in archive 7s 209ms
Then Restore transport from archive 2s 907ms
And Verify that transport has been successfully restored 1s 763ms
After Hooks.deleteTransportAfterTest() 833ms
After Hooks.rollbackSettings() 120ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-dayco" 219ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 124ms
And Mark custom fields as not obligatory 007ms
And Login as "dayco-admin" 2s 302ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 076ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 127ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 184ms
When Go to "TRANSPORT_TABLE" 358ms
And Click button advice in transport table "OWN_COLLECTION" 1s 278ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 48s 310ms
And Go to "TRANSPORT_TABLE" 478ms
And Find transport in table with status "planned-magazyn-tychy" 3s 747ms
And Confirm statuses until reach "process-ended" 16s 583ms
And Wait until transport disappear from transport table 40s 354ms
Then Go to "ARCHIVE_TAB" 504ms
And Show "OWN_COLLECTION" 178ms
And Verify that created transport is "true" in transport table 15s 165ms
After Hooks.deleteTransportAfterTest() 738ms
After Hooks.rollbackAllCustomFieldsSettings() 680ms
After Hooks.rollbackSettings() 138ms