Project Number Date
ApolloFullRunnerReport apollo-test-2.124 19 sie 2021, 06:07

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 8s 997ms 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" 228ms
And Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 236ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 230ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 563ms
Then Login as "super-admin-piast" 7s 311ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 467ms
After Hooks.deleteTransportAfterApiTest() 653ms
After Hooks.rollbackSettings() 187ms
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" 233ms
And Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 143ms
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 592ms
Then Login as "super-admin-piast" 2s 482ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 383ms
After Hooks.deleteTransportAfterApiTest() 650ms
After Hooks.rollbackSettings() 139ms
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" 228ms
And Set token of apiUsername "super-admin-piast" 249ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 125ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 129ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 584ms
Then Login as "super-admin-piast" 2s 450ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 379ms
After Hooks.deleteTransportAfterApiTest() 659ms
After Hooks.rollbackSettings() 109ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
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" 245ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 603ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 791ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 668ms
After Hooks.rollbackSettings() 140ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 267ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 146ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 238ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 588ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 832ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 637ms
After Hooks.rollbackSettings() 133ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 262ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 152ms
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" 236ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 587ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 337ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 645ms
After Hooks.rollbackSettings() 132ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 251ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 170ms
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 578ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 028ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 638ms
After Hooks.rollbackSettings() 143ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 228ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 156ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 144ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 238ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 569ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 264ms
After Hooks.deleteTransportAfterApiTest() 630ms
After Hooks.rollbackSettings() 137ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 248ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 134ms
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" 6s 040ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 581ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 746ms
And Show all transport types 1s 163ms
And Click button advice in transport table "DELIVERY" 237ms
And Set advice window in schedule 3s 776ms
And Fill advice form 13s 370ms
And Click advice save button and wait for advice form to disappear 33s 891ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 518ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 456ms
And Go to transport details "DELIVERY" 2s 900ms
And Expand advice panel 591ms
Then Check are transport values equals 2s 402ms
After Hooks.deleteTransportAfterApiTest() 916ms
After Hooks.rollbackSettings() 145ms
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 110ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 140ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 110ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 032ms
Then Login as "neuca-admin" 2s 378ms
And Go to "TRANSPORT_TABLE" 510ms
And Confirm statuses until reach "process-ended" 21s 550ms
Then Check if sorting by 'Finished' status is working correctly 339ms
After Hooks.deleteTransportsAfterTest() 4s 490ms
After Hooks.rollbackAllCustomFieldsSettings() 353ms
After Hooks.rollbackSettings() 108ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 226ms
And Delete invitations with email "automaty31415@test.pl" 091ms
And If user is login then logout 272ms
Given Set token of apiUsername "super-admin-piast" 270ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 153ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 217ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 422ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 725ms
Then Go to "INVITATIONS_TAB" 501ms
And Go to "EXPIRED_TAB" invitation status tab 231ms
Then Invitation is displayed on list "automaty31415@test.pl" 410ms
After Hooks.deleteInvitationAfterTest() 138ms
After Hooks.rollbackSettings() 122ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 225ms
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" 339ms
And Prepare setting for automatic time window delete with "super-admin-skz" 217ms
When Login as "swisskrono-admin" 7s 795ms
And Go to "WAREHOUSE_TAB" 927ms
Then Check if dedicated window is deleted from schedule 51s 314ms
After Hooks.rollbackSettings() 198ms
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 792ms
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" 144ms
And Set proper delay time to move order to archive after task timeout 151ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 983ms
And Go to "WAREHOUSE_TAB" 957ms
And Change warehouse in schedule to: "Katowice" 1s 623ms
And Wait "60" seconds 1m
And Verify that transport window is grey 077ms
And Verify that transport is in archive 6s 627ms
Then Restore transport from archive 2s 862ms
And Verify that transport has been successfully restored 1s 822ms
After Hooks.deleteTransportAfterTest() 743ms
After Hooks.rollbackSettings() 126ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 236ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 118ms
And Mark custom fields as not obligatory 006ms
And Login as "dayco-admin" 2s 143ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 109ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 129ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 213ms
When Go to "TRANSPORT_TABLE" 347ms
And Click button advice in transport table "OWN_COLLECTION" 1s 299ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 48s 248ms
And Go to "TRANSPORT_TABLE" 470ms
And Find transport in table with status "planned-magazyn-tychy" 3s 674ms
And Confirm statuses until reach "process-ended" 16s 711ms
And Wait until transport disappear from transport table 37s 445ms
Then Go to "ARCHIVE_TAB" 532ms
And Show "OWN_COLLECTION" 177ms
And Verify that created transport is "true" in transport table 15s 176ms
After Hooks.deleteTransportAfterTest() 710ms
After Hooks.rollbackAllCustomFieldsSettings() 515ms
After Hooks.rollbackSettings() 133ms