Project Number Date
ApolloFullRunnerReport apollo-test-2.155 12 wrz 2021, 06:40

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 29s 999ms 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" 240ms
And Set token of apiUsername "super-admin-piast" 236ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 330ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 249ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 731ms
Then Login as "super-admin-piast" 7s 030ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 513ms
After Hooks.deleteTransportAfterApiTest() 674ms
After Hooks.rollbackSettings() 189ms
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" 243ms
And Set token of apiUsername "super-admin-piast" 230ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 161ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 174ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 774ms
Then Login as "super-admin-piast" 2s 553ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 371ms
After Hooks.deleteTransportAfterApiTest() 685ms
After Hooks.rollbackSettings() 147ms
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" 245ms
And Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
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 693ms
Then Login as "super-admin-piast" 2s 466ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 350ms
After Hooks.deleteTransportAfterApiTest() 660ms
After Hooks.rollbackSettings() 104ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 139ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 168ms
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 678ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 933ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 654ms
After Hooks.rollbackSettings() 132ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 168ms
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 654ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 896ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 627ms
After Hooks.rollbackSettings() 134ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 234ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 175ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 250ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 694ms
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() 632ms
After Hooks.rollbackSettings() 131ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 194ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 272ms
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 "invalidToken" for api version "v1" 030ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 664ms
After Hooks.rollbackSettings() 121ms
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 899ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 154ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 127ms
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 636ms
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
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" 332ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 284ms
After Hooks.rollbackSettings() 105ms
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" 134ms
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" 247ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 649ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 297ms
After Hooks.deleteTransportAfterApiTest() 724ms
After Hooks.rollbackSettings() 133ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 244ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 139ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 160ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 343ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 769ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 008ms
And Show all transport types 1s 185ms
And Click button advice in transport table "DELIVERY" 262ms
And Set advice window in schedule 3s 919ms
And Fill advice form 13s 299ms
And Click advice save button and wait for advice form to disappear 34s 011ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 757ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 459ms
And Go to transport details "DELIVERY" 2s 932ms
And Expand advice panel 542ms
Then Check are transport values equals 2s 416ms
After Hooks.deleteTransportAfterApiTest() 855ms
After Hooks.rollbackSettings() 135ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 228ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 110ms
And Mark custom fields as not obligatory 008ms
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" 128ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 129ms
Then Login as "neuca-admin" 2s 327ms
And Go to "TRANSPORT_TABLE" 497ms
And Confirm statuses until reach "process-ended" 22s 458ms
Then Check if sorting by 'Finished' status is working correctly 308ms
After Hooks.deleteTransportsAfterTest() 4s 419ms
After Hooks.rollbackAllCustomFieldsSettings() 331ms
After Hooks.rollbackSettings() 107ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 229ms
And Delete invitations with email "automaty31415@test.pl" 091ms
And If user is login then logout 260ms
Given Set token of apiUsername "super-admin-piast" 253ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 137ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 214ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 391ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 776ms
Then Go to "INVITATIONS_TAB" 524ms
And Go to "EXPIRED_TAB" invitation status tab 300ms
Then Invitation is displayed on list "automaty31415@test.pl" 456ms
After Hooks.deleteInvitationAfterTest() 125ms
After Hooks.rollbackSettings() 125ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 248ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 136ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 357ms
And Prepare setting for automatic time window delete with "super-admin-skz" 241ms
When Login as "swisskrono-admin" 7s 622ms
And Go to "WAREHOUSE_TAB" 823ms
Then Check if dedicated window is deleted from schedule 51s 137ms
After Hooks.rollbackSettings() 185ms
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 715ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 028ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 203ms
And Set proper delay time to move order to archive after task timeout 181ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 2s 116ms
And Go to "WAREHOUSE_TAB" 1s 015ms
And Change warehouse in schedule to: "Katowice" 1s 286ms
And Wait "60" seconds 1m
And Verify that transport window is grey 069ms
And Verify that transport is in archive 7s 925ms
Then Restore transport from archive 2s 623ms
And Verify that transport has been successfully restored 1s 932ms
After Hooks.deleteTransportAfterTest() 706ms
After Hooks.rollbackSettings() 116ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 229ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 114ms
And Mark custom fields as not obligatory 004ms
And Login as "dayco-admin" 2s 195ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 061ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 139ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 204ms
When Go to "TRANSPORT_TABLE" 372ms
And Click button advice in transport table "OWN_COLLECTION" 1s 284ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 324ms
And Go to "TRANSPORT_TABLE" 331ms
And Find transport in table with status "planned-magazyn-tychy" 3s 747ms
And Confirm statuses until reach "process-ended" 17s 070ms
And Wait until transport disappear from transport table 37s 215ms
Then Go to "ARCHIVE_TAB" 521ms
And Show "OWN_COLLECTION" 169ms
And Verify that created transport is "true" in transport table 15s 146ms
After Hooks.deleteTransportAfterTest() 710ms
After Hooks.rollbackAllCustomFieldsSettings() 604ms
After Hooks.rollbackSettings() 162ms