Project Number Date
ApolloFullRunnerReport apollo-test-2.119 15 sie 2021, 05:58

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@rollbackSettings 125 1 3 0 0 129 13 1 14 7m 23s 957ms 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" 243ms
And Set token of apiUsername "super-admin-piast" 247ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 217ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 629ms
Then Login as "super-admin-piast" 8s 173ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 402ms
After Hooks.deleteTransportAfterApiTest() 609ms
After Hooks.rollbackSettings() 219ms
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" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 172ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 159ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 704ms
Then Login as "super-admin-piast" 2s 470ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 395ms
After Hooks.deleteTransportAfterApiTest() 675ms
After Hooks.rollbackSettings() 142ms
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" 231ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 110ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 631ms
Then Login as "super-admin-piast" 2s 512ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 364ms
After Hooks.deleteTransportAfterApiTest() 668ms
After Hooks.rollbackSettings() 104ms
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" 170ms
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 592ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 808ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 676ms
After Hooks.rollbackSettings() 141ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 258ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 155ms
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" 232ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 592ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 831ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 635ms
After Hooks.rollbackSettings() 132ms
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" 138ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 165ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 228ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 593ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 345ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 652ms
After Hooks.rollbackSettings() 128ms
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" 149ms
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" 237ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 617ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 029ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 634ms
After Hooks.rollbackSettings() 129ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 222ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 148ms
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" 250ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 573ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 237ms
After Hooks.deleteTransportAfterApiTest() 636ms
After Hooks.rollbackSettings() 166ms
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" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 154ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 492ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 593ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 583ms
And Show all transport types 1s 185ms
And Click button advice in transport table "DELIVERY" 220ms
And Set advice window in schedule 3s 806ms
And Fill advice form 13s 344ms
And Click advice save button and wait for advice form to disappear 33s 908ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 546ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 502ms
And Go to transport details "DELIVERY" 2s 963ms
And Expand advice panel 497ms
Then Check are transport values equals 2s 399ms
After Hooks.deleteTransportAfterApiTest() 887ms
After Hooks.rollbackSettings() 123ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 250ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 104ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 133ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 139ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 148ms
Then Login as "neuca-admin" 2s 309ms
And Go to "TRANSPORT_TABLE" 536ms
And Confirm statuses until reach "process-ended" 22s 530ms
Then Check if sorting by 'Finished' status is working correctly 261ms
After Hooks.deleteTransportsAfterTest() 4s 548ms
After Hooks.rollbackAllCustomFieldsSettings() 360ms
After Hooks.rollbackSettings() 108ms
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" 103ms
And If user is login then logout 265ms
Given Set token of apiUsername "super-admin-piast" 253ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 143ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 226ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 417ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 807ms
Then Go to "INVITATIONS_TAB" 537ms
And Go to "EXPIRED_TAB" invitation status tab 300ms
Then Invitation is displayed on list "automaty31415@test.pl" 462ms
After Hooks.deleteInvitationAfterTest() 142ms
After Hooks.rollbackSettings() 130ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-skz" 265ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 148ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 317ms
And Prepare setting for automatic time window delete with "super-admin-skz" 385ms
When Login as "swisskrono-admin" 7s 913ms
And Go to "WAREHOUSE_TAB" 913ms
Then Check if dedicated window is deleted from schedule 1m 12s 054ms
After Hooks.rollbackSettings() 196ms
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 904ms
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" 157ms
And Set proper delay time to move order to archive after task timeout 140ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 990ms
And Go to "WAREHOUSE_TAB" 1s 042ms
And Change warehouse in schedule to: "Katowice" 1s 747ms
And Wait "60" seconds 1m
And Verify that transport window is grey 093ms
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() 746ms
After Hooks.rollbackSettings() 242ms
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 190ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 070ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 141ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 210ms
When Go to "TRANSPORT_TABLE" 345ms
And Click button advice in transport table "OWN_COLLECTION" 1s 315ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 48s 251ms
And Go to "TRANSPORT_TABLE" 496ms
And Find transport in table with status "planned-magazyn-tychy" 3s 687ms
And Confirm statuses until reach "process-ended" 16s 787ms
And Wait until transport disappear from transport table 40s 486ms
Then Go to "ARCHIVE_TAB" 519ms
And Show "OWN_COLLECTION" 199ms
And Verify that created transport is "true" in transport table 15s 179ms
After Hooks.deleteTransportAfterTest() 694ms
After Hooks.rollbackAllCustomFieldsSettings() 612ms
After Hooks.rollbackSettings() 157ms