Project Number Date
ApolloFullRunnerReport apollo-test-2.68 05 lip 2021, 06:38

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@rollbackSettings 77 1 0 0 0 78 7 1 8 7m 24s 641ms Failed
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 252ms
And Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 273ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 028ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 520ms
Then Login as "super-admin-piast" 7s 712ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 410ms
After Hooks.deleteTransportAfterApiTest() 783ms
After Hooks.rollbackSettings() 002ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 249ms
And Set token of apiUsername "super-admin-piast" 248ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 163ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 028ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 428ms
Then Login as "super-admin-piast" 2s 282ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 402ms
After Hooks.deleteTransportAfterApiTest() 811ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 242ms
And Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 026ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 471ms
Then Login as "super-admin-piast" 2s 317ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 398ms
After Hooks.deleteTransportAfterApiTest() 755ms
After Hooks.rollbackSettings() 000ms
View Feature Filters
Given Set token of apiUsername "super-admin-neuca" 223ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 177ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 148ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 030ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 21s 165ms
Then Login as "neuca-admin" 2s 254ms
And Go to "TRANSPORT_TABLE" 493ms
And Confirm statuses until reach "process-ended" 22s 290ms
Then Check if sorting by 'Finished' status is working correctly 239ms
After Hooks.deleteTransportsAfterTest() 2s 747ms
After Hooks.rollbackAllCustomFieldsSettings() 350ms
After Hooks.rollbackSettings() 126ms
View Feature Invitation
Given Set token of apiUsername "super-admin-piast" 230ms
And Delete invitations with email "automaty31415@test.pl" 018ms
And If user is login then logout 257ms
Given Set token of apiUsername "super-admin-piast" 260ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 149ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 143ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 340ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 611ms
Then Go to "INVITATIONS_TAB" 486ms
And Go to "EXPIRED_TAB" invitation status tab 289ms
Then Invitation is displayed on list "automaty31415@test.pl" 449ms
After Hooks.deleteInvitationAfterTest() 151ms
After Hooks.rollbackSettings() 123ms
View Feature DedicatedWindow
Given Set token of apiUsername "super-admin-skz" 230ms
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" 309ms
And Prepare setting for automatic time window delete with "super-admin-skz" 217ms
When Login as "swisskrono-admin" 7s 774ms
And Go to "WAREHOUSE_TAB" 819ms
Then Check if dedicated window is deleted from schedule 1m 18s 436ms
After Hooks.rollbackSettings() 296ms
View Feature Move transport to archive
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 034ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 017ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 144ms
And Set proper delay time to move order to archive after task timeout 127ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 958ms
And Go to "WAREHOUSE_TAB" 1s 048ms
And Change warehouse in schedule to: "Katowice" 1s 560ms
And Wait "60" seconds 1m
And Verify that transport window is grey 084ms
And Verify that transport is in archive 10s 799ms
Then Restore transport from archive 2s 607ms
And Verify that transport has been successfully restored 15s 685ms
After Hooks.deleteTransportAfterTest() 1s
After Hooks.rollbackSettings() 120ms
View Feature Move transport to archive
Scenario Outline Check if confirming transport status removed it to the archive
Steps
Given Set token of apiUsername "super-admin-dayco" 243ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 117ms
And Mark custom fields as not obligatory 007ms
And Login as "dayco-admin" 2s 101ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 112ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 141ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 030ms
When Go to "TRANSPORT_TABLE" 392ms
And Click button advice in transport table "OWN_COLLECTION" 1s 420ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 835ms
And Go to "TRANSPORT_TABLE" 462ms
And Find transport in table with status "planned-magazyn-tychy" 3s 727ms
And Confirm statuses until reach "process-ended" 16s 649ms
And Wait "12" seconds 12s
Then Go to "ARCHIVE_TAB" 525ms
And Show "OWN_COLLECTION" 163ms
And Verify that created transport is "true" in transport table 1m 32s 358ms
java.lang.AssertionError: expected: but was:
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at org.junit.Assert.assertEquals(Assert.java:144)
	at CucumberTests._PerformanceTests.TransportTableTest.verifyThatCreatedTransportIsInTransportTable(TransportTableTest.java:120)
	at ✽.Verify that created transport is "true" in transport table(file:Features/Atom/Transport/Archive.feature:54)
After Hooks.deleteTransportAfterTest() 992ms
After Hooks.rollbackAllCustomFieldsSettings() 464ms
After Hooks.rollbackSettings() 140ms