Project Number Date
ApolloFullRunnerReport apollo-test-2.113 11 sie 2021, 05:52

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 6m 53s 986ms 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" 241ms
And Set token of apiUsername "super-admin-piast" 236ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 073ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 242ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 660ms
Then Login as "super-admin-piast" 4s 228ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 431ms
After Hooks.deleteTransportAfterApiTest() 652ms
After Hooks.rollbackSettings() 234ms
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" 273ms
And Set token of apiUsername "super-admin-piast" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 179ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 173ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 640ms
Then Login as "super-admin-piast" 2s 526ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 398ms
After Hooks.deleteTransportAfterApiTest() 669ms
After Hooks.rollbackSettings() 134ms
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" 253ms
And Set token of apiUsername "super-admin-piast" 239ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 118ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 602ms
Then Login as "super-admin-piast" 2s 435ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 399ms
After Hooks.deleteTransportAfterApiTest() 666ms
After Hooks.rollbackSettings() 112ms
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" 140ms
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" 253ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 586ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 985ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 662ms
After Hooks.rollbackSettings() 134ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 150ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 162ms
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 615ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 827ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 668ms
After Hooks.rollbackSettings() 134ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 182ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 237ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 561ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 339ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 673ms
After Hooks.rollbackSettings() 126ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 249ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
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" 246ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 563ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 032ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 637ms
After Hooks.rollbackSettings() 146ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
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" 263ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 622ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 282ms
After Hooks.deleteTransportAfterApiTest() 644ms
After Hooks.rollbackSettings() 129ms
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" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 158ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 877ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 602ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 532ms
And Show all transport types 1s 196ms
And Click button advice in transport table "DELIVERY" 246ms
And Set advice window in schedule 4s 024ms
And Fill advice form 13s 338ms
And Click advice save button and wait for advice form to disappear 33s 990ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 570ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 504ms
And Go to transport details "DELIVERY" 2s 927ms
And Expand advice panel 611ms
Then Check are transport values equals 2s 468ms
After Hooks.deleteTransportAfterApiTest() 911ms
After Hooks.rollbackSettings() 133ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 244ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 100ms
And Mark custom fields as not obligatory 005ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 135ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 120ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 203ms
Then Login as "neuca-admin" 2s 380ms
And Go to "TRANSPORT_TABLE" 489ms
And Confirm statuses until reach "process-ended" 21s 451ms
Then Check if sorting by 'Finished' status is working correctly 292ms
After Hooks.deleteTransportsAfterTest() 4s 660ms
After Hooks.rollbackAllCustomFieldsSettings() 335ms
After Hooks.rollbackSettings() 107ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 258ms
And Delete invitations with email "automaty31415@test.pl" 105ms
And If user is login then logout 250ms
Given Set token of apiUsername "super-admin-piast" 340ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 151ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 209ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 449ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 840ms
Then Go to "INVITATIONS_TAB" 518ms
And Go to "EXPIRED_TAB" invitation status tab 312ms
Then Invitation is displayed on list "automaty31415@test.pl" 451ms
After Hooks.deleteInvitationAfterTest() 150ms
After Hooks.rollbackSettings() 126ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 232ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 131ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 316ms
And Prepare setting for automatic time window delete with "super-admin-skz" 206ms
When Login as "swisskrono-admin" 7s 820ms
And Go to "WAREHOUSE_TAB" 949ms
Then Check if dedicated window is deleted from schedule 30s 299ms
After Hooks.rollbackSettings() 183ms
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 509ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 021ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 184ms
And Set proper delay time to move order to archive after task timeout 175ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 2s 035ms
And Go to "WAREHOUSE_TAB" 1s 094ms
And Change warehouse in schedule to: "Katowice" 4s 736ms
And Wait "60" seconds 1m
And Verify that transport window is grey 086ms
And Verify that transport is in archive 7s 440ms
Then Restore transport from archive 2s 817ms
And Verify that transport has been successfully restored 1s 798ms
After Hooks.deleteTransportAfterTest() 774ms
After Hooks.rollbackSettings() 127ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 221ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 123ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 287ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 068ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 137ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 187ms
When Go to "TRANSPORT_TABLE" 405ms
And Click button advice in transport table "OWN_COLLECTION" 1s 294ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 48s 368ms
And Go to "TRANSPORT_TABLE" 457ms
And Find transport in table with status "planned-magazyn-tychy" 3s 698ms
And Confirm statuses until reach "process-ended" 16s 703ms
And Wait until transport disappear from transport table 40s 322ms
Then Go to "ARCHIVE_TAB" 566ms
And Show "OWN_COLLECTION" 183ms
And Verify that created transport is "true" in transport table 15s 167ms
After Hooks.deleteTransportAfterTest() 705ms
After Hooks.rollbackAllCustomFieldsSettings() 523ms
After Hooks.rollbackSettings() 142ms