Project Number Date
ApolloFullRunnerReport apollo-test-2.140 01 wrz 2021, 05:52

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@rollbackSettings 132 1 3 0 0 136 14 1 15 6m 23s 334ms Failed
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" 269ms
And Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 175ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 284ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 807ms
Then Login as "super-admin-piast" 8s 702ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 447ms
After Hooks.deleteTransportAfterApiTest() 677ms
After Hooks.rollbackSettings() 176ms
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" 266ms
And Set token of apiUsername "super-admin-piast" 233ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 180ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 745ms
Then Login as "super-admin-piast" 2s 483ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 344ms
After Hooks.deleteTransportAfterApiTest() 654ms
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" 223ms
And 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: "ERP_IDENTIFIER" with "super-admin-piast" 117ms
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" 2s 504ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 394ms
After Hooks.deleteTransportAfterApiTest() 656ms
After Hooks.rollbackSettings() 109ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 269ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 151ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 152ms
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 697ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 964ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 748ms
After Hooks.rollbackSettings() 137ms
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" 147ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 160ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 251ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 709ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 883ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 599ms
After Hooks.rollbackSettings() 140ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 250ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 161ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 148ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 252ms
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 "invalidTransportId" for api version "v1" 380ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 639ms
After Hooks.rollbackSettings() 126ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 254ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 139ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 152ms
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 654ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 034ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 666ms
After Hooks.rollbackSettings() 131ms
View Feature API Transport
@deleteApiTransportsAfterTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 3s 009ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 161ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 136ms
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 671ms
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 695ms
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" 341ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 287ms
After Hooks.rollbackSettings() 105ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 250ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 131ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 160ms
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 651ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 290ms
After Hooks.deleteTransportAfterApiTest() 659ms
After Hooks.rollbackSettings() 128ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 134ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 147ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 567ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 658ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 007ms
And Show all transport types 1s 189ms
And Click button advice in transport table "DELIVERY" 274ms
And Set advice window in schedule 3s 927ms
And Fill advice form 13s 291ms
And Click advice save button and wait for advice form to disappear 33s 952ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 950ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 483ms
And Go to transport details "DELIVERY" 2s 914ms
And Expand advice panel 580ms
Then Check are transport values equals 2s 383ms
After Hooks.deleteTransportAfterApiTest() 850ms
After Hooks.rollbackSettings() 126ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 238ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 097ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 138ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 125ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 167ms
Then Login as "neuca-admin" 2s 309ms
And Go to "TRANSPORT_TABLE" 519ms
And Confirm statuses until reach "process-ended" 22s 561ms
Then Check if sorting by 'Finished' status is working correctly 288ms
After Hooks.deleteTransportsAfterTest() 4s 496ms
After Hooks.rollbackAllCustomFieldsSettings() 355ms
After Hooks.rollbackSettings() 100ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-piast" 230ms
And Delete invitations with email "automaty31415@test.pl" 088ms
And If user is login then logout 230ms
Given Set token of apiUsername "super-admin-piast" 339ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 133ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 287ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 375ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 733ms
Then Go to "INVITATIONS_TAB" 504ms
And Go to "EXPIRED_TAB" invitation status tab 291ms
Then Invitation is displayed on list "automaty31415@test.pl" 492ms
After Hooks.deleteInvitationAfterTest() 128ms
After Hooks.rollbackSettings() 126ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 253ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 135ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 353ms
And Prepare setting for automatic time window delete with "super-admin-skz" 245ms
When Login as "swisskrono-admin" 7s 819ms
And Go to "WAREHOUSE_TAB" 873ms
Then Check if dedicated window is deleted from schedule 48s 456ms
After Hooks.rollbackSettings() 195ms
View Feature Move transport to archive
@rollbackSettings @deleteTransportAfterTest
Scenario Outline Check if delayed transport is moved to archived and can be restored
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 899ms
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" 148ms
And Set proper delay time to move order to archive after task timeout 131ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 942ms
And Go to "WAREHOUSE_TAB" 895ms
And Change warehouse in schedule to: "Katowice" 1s 830ms
And Wait "60" seconds 1m
And Verify that transport window is grey 075ms
Error message 
java.lang.AssertionError: Okno zlecenia nie zrobiło się szare
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Warehouse.WarehouseTest.verifyThatTransportWindowIsGrey(WarehouseTest.java:118)
	at ✽.Verify that transport window is grey(file:Features/Atom/Transport/Archive.feature:13)
And Verify that transport is in archive 000ms
Then Restore transport from archive 000ms
And Verify that transport has been successfully restored 000ms
After Hooks.deleteTransportAfterTest() 753ms
After Hooks.rollbackSettings() 223ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 225ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 129ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 285ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 059ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 135ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 200ms
When Go to "TRANSPORT_TABLE" 354ms
And Click button advice in transport table "OWN_COLLECTION" 1s 342ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 652ms
And Go to "TRANSPORT_TABLE" 359ms
And Find transport in table with status "planned-magazyn-tychy" 3s 695ms
And Confirm statuses until reach "process-ended" 16s 849ms
And Wait until transport disappear from transport table 40s 490ms
Then Go to "ARCHIVE_TAB" 547ms
And Show "OWN_COLLECTION" 179ms
And Verify that created transport is "true" in transport table 15s 164ms
After Hooks.deleteTransportAfterTest() 729ms
After Hooks.rollbackAllCustomFieldsSettings() 620ms
After Hooks.rollbackSettings() 138ms