Project Number Date
ApolloFullRunnerReport apollo-test-2.149 08 wrz 2021, 06:16

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 59s 663ms Passed
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" 239ms
And Set token of apiUsername "super-admin-piast" 233ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 148ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 237ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 734ms
Then Login as "super-admin-piast" 6s 652ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 387ms
After Hooks.deleteTransportAfterApiTest() 583ms
After Hooks.rollbackSettings() 209ms
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" 246ms
And Set token of apiUsername "super-admin-piast" 239ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 155ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 162ms
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" 2s 571ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 395ms
After Hooks.deleteTransportAfterApiTest() 649ms
After Hooks.rollbackSettings() 150ms
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" 234ms
And Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 125ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 724ms
Then Login as "super-admin-piast" 2s 506ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 355ms
After Hooks.deleteTransportAfterApiTest() 653ms
After Hooks.rollbackSettings() 098ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 234ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 176ms
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 706ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 873ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 649ms
After Hooks.rollbackSettings() 137ms
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" 132ms
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" 243ms
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" 870ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 657ms
After Hooks.rollbackSettings() 126ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 143ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 167ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 241ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 704ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 348ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 661ms
After Hooks.rollbackSettings() 149ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 270ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 176ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 249ms
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" 029ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 722ms
After Hooks.rollbackSettings() 126ms
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 871ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 160ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 138ms
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 634ms
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 665ms
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" 353ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 252ms
After Hooks.rollbackSettings() 095ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 139ms
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 646ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 267ms
After Hooks.deleteTransportAfterApiTest() 619ms
After Hooks.rollbackSettings() 130ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 242ms
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 as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 325ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 640ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 007ms
And Show all transport types 1s 174ms
And Click button advice in transport table "DELIVERY" 262ms
And Set advice window in schedule 3s 777ms
And Fill advice form 13s 482ms
And Click advice save button and wait for advice form to disappear 33s 857ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 645ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 511ms
And Go to transport details "DELIVERY" 2s 957ms
And Expand advice panel 496ms
Then Check are transport values equals 2s 416ms
After Hooks.deleteTransportAfterApiTest() 895ms
After Hooks.rollbackSettings() 136ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 223ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 127ms
And Mark custom fields as not obligatory 007ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 137ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 116ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 179ms
Then Login as "neuca-admin" 2s 348ms
And Go to "TRANSPORT_TABLE" 513ms
And Confirm statuses until reach "process-ended" 22s 320ms
Then Check if sorting by 'Finished' status is working correctly 317ms
After Hooks.deleteTransportsAfterTest() 4s 406ms
After Hooks.rollbackAllCustomFieldsSettings() 326ms
After Hooks.rollbackSettings() 102ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 273ms
And Delete invitations with email "automaty31415@test.pl" 093ms
And If user is login then logout 277ms
Given Set token of apiUsername "super-admin-piast" 251ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 152ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 219ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 486ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 745ms
Then Go to "INVITATIONS_TAB" 446ms
And Go to "EXPIRED_TAB" invitation status tab 237ms
Then Invitation is displayed on list "automaty31415@test.pl" 402ms
After Hooks.deleteInvitationAfterTest() 144ms
After Hooks.rollbackSettings() 138ms
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" 126ms
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" 238ms
When Login as "swisskrono-admin" 7s 764ms
And Go to "WAREHOUSE_TAB" 886ms
Then Check if dedicated window is deleted from schedule 1m 21s 629ms
After Hooks.rollbackSettings() 176ms
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 314ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 018ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 160ms
And Set proper delay time to move order to archive after task timeout 139ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 2s 036ms
And Go to "WAREHOUSE_TAB" 1s 088ms
And Change warehouse in schedule to: "Katowice" 1s 190ms
And Wait "60" seconds 1m
And Verify that transport window is grey 086ms
And Verify that transport is in archive 7s 105ms
Then Restore transport from archive 2s 869ms
And Verify that transport has been successfully restored 1s 781ms
After Hooks.deleteTransportAfterTest() 791ms
After Hooks.rollbackSettings() 118ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 219ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 151ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 207ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 094ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 136ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 208ms
When Go to "TRANSPORT_TABLE" 337ms
And Click button advice in transport table "OWN_COLLECTION" 1s 289ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 640ms
And Go to "TRANSPORT_TABLE" 361ms
And Find transport in table with status "planned-magazyn-tychy" 3s 759ms
And Confirm statuses until reach "process-ended" 16s 770ms
And Wait until transport disappear from transport table 37s 517ms
Then Go to "ARCHIVE_TAB" 562ms
And Show "OWN_COLLECTION" 174ms
And Verify that created transport is "true" in transport table 15s 131ms
After Hooks.deleteTransportAfterTest() 729ms
After Hooks.rollbackAllCustomFieldsSettings() 598ms
After Hooks.rollbackSettings() 155ms