Project Number Date
ApolloFullRunnerReport apollo-test-2.134 26 sie 2021, 07:47

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 20s 217ms 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" 234ms
And Set token of apiUsername "super-admin-piast" 246ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 061ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 216ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 681ms
Then Login as "super-admin-piast" 8s 574ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 383ms
After Hooks.deleteTransportAfterApiTest() 545ms
After Hooks.rollbackSettings() 183ms
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" 255ms
And Set token of apiUsername "super-admin-piast" 257ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 171ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 164ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 705ms
Then Login as "super-admin-piast" 2s 578ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 415ms
After Hooks.deleteTransportAfterApiTest() 664ms
After Hooks.rollbackSettings() 138ms
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" 231ms
And Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 130ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 123ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 676ms
Then Login as "super-admin-piast" 2s 491ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 388ms
After Hooks.deleteTransportAfterApiTest() 642ms
After Hooks.rollbackSettings() 096ms
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" 142ms
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" 239ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 681ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 889ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 662ms
After Hooks.rollbackSettings() 145ms
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" 135ms
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" 250ms
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_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 875ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 643ms
After Hooks.rollbackSettings() 126ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 238ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
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" 244ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 688ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 366ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 620ms
After Hooks.rollbackSettings() 146ms
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" 155ms
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" 244ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 646ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 031ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 644ms
After Hooks.rollbackSettings() 138ms
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 825ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 131ms
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 659ms
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 677ms
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" 344ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 283ms
After Hooks.rollbackSettings() 098ms
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" 140ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 159ms
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 666ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 260ms
After Hooks.deleteTransportAfterApiTest() 670ms
After Hooks.rollbackSettings() 141ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 148ms
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 369ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 602ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 008ms
And Show all transport types 1s 175ms
And Click button advice in transport table "DELIVERY" 227ms
And Set advice window in schedule 3s 707ms
And Fill advice form 13s 403ms
And Click advice save button and wait for advice form to disappear 33s 920ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 609ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 477ms
And Go to transport details "DELIVERY" 2s 858ms
And Expand advice panel 471ms
Then Check are transport values equals 2s 392ms
After Hooks.deleteTransportAfterApiTest() 880ms
After Hooks.rollbackSettings() 134ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 234ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 113ms
And Mark custom fields as not obligatory 007ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 142ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 105ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 179ms
Then Login as "neuca-admin" 2s 290ms
And Go to "TRANSPORT_TABLE" 530ms
And Confirm statuses until reach "process-ended" 22s 335ms
Then Check if sorting by 'Finished' status is working correctly 300ms
After Hooks.deleteTransportsAfterTest() 4s 424ms
After Hooks.rollbackAllCustomFieldsSettings() 358ms
After Hooks.rollbackSettings() 107ms
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" 092ms
And If user is login then logout 281ms
Given Set token of apiUsername "super-admin-piast" 264ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 140ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 189ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 361ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 700ms
Then Go to "INVITATIONS_TAB" 535ms
And Go to "EXPIRED_TAB" invitation status tab 305ms
Then Invitation is displayed on list "automaty31415@test.pl" 463ms
After Hooks.deleteInvitationAfterTest() 143ms
After Hooks.rollbackSettings() 121ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 245ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 129ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 315ms
And Prepare setting for automatic time window delete with "super-admin-skz" 219ms
When Login as "swisskrono-admin" 7s 931ms
And Go to "WAREHOUSE_TAB" 960ms
Then Check if dedicated window is deleted from schedule 54s 349ms
After Hooks.rollbackSettings() 190ms
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 738ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 019ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 153ms
And Set proper delay time to move order to archive after task timeout 158ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 937ms
And Go to "WAREHOUSE_TAB" 928ms
And Change warehouse in schedule to: "Katowice" 1s 691ms
And Wait "60" seconds 1m
And Verify that transport window is grey 085ms
And Verify that transport is in archive 6s 804ms
Then Restore transport from archive 2s 814ms
And Verify that transport has been successfully restored 1s 851ms
After Hooks.deleteTransportAfterTest() 840ms
After Hooks.rollbackSettings() 124ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 218ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 112ms
And Mark custom fields as not obligatory 004ms
And Login as "dayco-admin" 2s 276ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 055ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 112ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 218ms
When Go to "TRANSPORT_TABLE" 364ms
And Click button advice in transport table "OWN_COLLECTION" 1s 316ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 524ms
And Go to "TRANSPORT_TABLE" 367ms
And Find transport in table with status "planned-magazyn-tychy" 3s 716ms
And Confirm statuses until reach "process-ended" 16s 728ms
And Wait until transport disappear from transport table 22s 544ms
Then Go to "ARCHIVE_TAB" 569ms
And Show "OWN_COLLECTION" 188ms
And Verify that created transport is "true" in transport table 15s 151ms
After Hooks.deleteTransportAfterTest() 740ms
After Hooks.rollbackAllCustomFieldsSettings() 575ms
After Hooks.rollbackSettings() 150ms