Project Number Date
ApolloFullRunnerReport apollo-test-2.153 10 wrz 2021, 06:23

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 31s 425ms 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" 259ms
And Set token of apiUsername "super-admin-piast" 239ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 176ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 233ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 687ms
Then Login as "super-admin-piast" 7s 444ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 407ms
After Hooks.deleteTransportAfterApiTest() 559ms
After Hooks.rollbackSettings() 167ms
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" 239ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 154ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 171ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 853ms
Then Login as "super-admin-piast" 2s 437ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 372ms
After Hooks.deleteTransportAfterApiTest() 669ms
After Hooks.rollbackSettings() 140ms
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" 233ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 120ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 710ms
Then Login as "super-admin-piast" 2s 597ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 352ms
After Hooks.deleteTransportAfterApiTest() 694ms
After Hooks.rollbackSettings() 107ms
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" 145ms
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" 234ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 698ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 872ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 691ms
After Hooks.rollbackSettings() 120ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 251ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
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" 257ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 741ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 884ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 649ms
After Hooks.rollbackSettings() 134ms
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" 140ms
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" 235ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 731ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 344ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 638ms
After Hooks.rollbackSettings() 154ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 247ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 162ms
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" 255ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 715ms
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() 666ms
After Hooks.rollbackSettings() 134ms
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 910ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 155ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 130ms
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 673ms
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 645ms
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" 337ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 217ms
After Hooks.rollbackSettings() 109ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 249ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 141ms
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 650ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 265ms
After Hooks.deleteTransportAfterApiTest() 621ms
After Hooks.rollbackSettings() 138ms
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" 131ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 159ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 097ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 665ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 010ms
And Show all transport types 1s 188ms
And Click button advice in transport table "DELIVERY" 262ms
And Set advice window in schedule 3s 793ms
And Fill advice form 13s 215ms
And Click advice save button and wait for advice form to disappear 33s 856ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 637ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 507ms
And Go to transport details "DELIVERY" 3s 005ms
And Expand advice panel 596ms
Then Check are transport values equals 2s 389ms
After Hooks.deleteTransportAfterApiTest() 824ms
After Hooks.rollbackSettings() 133ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 260ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 109ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 128ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 121ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 047ms
Then Login as "neuca-admin" 2s 284ms
And Go to "TRANSPORT_TABLE" 489ms
And Confirm statuses until reach "process-ended" 21s 471ms
Then Check if sorting by 'Finished' status is working correctly 380ms
After Hooks.deleteTransportsAfterTest() 4s 400ms
After Hooks.rollbackAllCustomFieldsSettings() 329ms
After Hooks.rollbackSettings() 101ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 240ms
And Delete invitations with email "automaty31415@test.pl" 090ms
And If user is login then logout 269ms
Given Set token of apiUsername "super-admin-piast" 264ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 139ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 182ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 388ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 829ms
Then Go to "INVITATIONS_TAB" 524ms
And Go to "EXPIRED_TAB" invitation status tab 264ms
Then Invitation is displayed on list "automaty31415@test.pl" 417ms
After Hooks.deleteInvitationAfterTest() 146ms
After Hooks.rollbackSettings() 114ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-skz" 221ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 121ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 312ms
And Prepare setting for automatic time window delete with "super-admin-skz" 211ms
When Login as "swisskrono-admin" 7s 560ms
And Go to "WAREHOUSE_TAB" 896ms
Then Check if dedicated window is deleted from schedule 54s 302ms
After Hooks.rollbackSettings() 192ms
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 221ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 016ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 136ms
And Set proper delay time to move order to archive after task timeout 141ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 912ms
And Go to "WAREHOUSE_TAB" 989ms
And Change warehouse in schedule to: "Katowice" 1s 245ms
And Wait "60" seconds 1m
And Verify that transport window is grey 086ms
And Verify that transport is in archive 7s 048ms
Then Restore transport from archive 2s 849ms
And Verify that transport has been successfully restored 1s 808ms
After Hooks.deleteTransportAfterTest() 757ms
After Hooks.rollbackSettings() 114ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 227ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 118ms
And Mark custom fields as not obligatory 004ms
And Login as "dayco-admin" 2s 330ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 088ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 130ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 194ms
When Go to "TRANSPORT_TABLE" 410ms
And Click button advice in transport table "OWN_COLLECTION" 1s 282ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 507ms
And Go to "TRANSPORT_TABLE" 357ms
And Find transport in table with status "planned-magazyn-tychy" 3s 701ms
And Confirm statuses until reach "process-ended" 16s 761ms
And Wait until transport disappear from transport table 37s 566ms
Then Go to "ARCHIVE_TAB" 558ms
And Show "OWN_COLLECTION" 187ms
And Verify that created transport is "true" in transport table 15s 161ms
After Hooks.deleteTransportAfterTest() 727ms
After Hooks.rollbackAllCustomFieldsSettings() 524ms
After Hooks.rollbackSettings() 142ms