Project Number Date
ApolloFullRunnerReport apollo-test-2.72 09 lip 2021, 07:01

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 6m 47s 619ms Failed
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 283ms
And Set token of apiUsername "super-admin-piast" 250ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 299ms
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 623ms
Then Login as "super-admin-piast" 3s 851ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 441ms
After Hooks.deleteTransportAfterApiTest() 653ms
After Hooks.rollbackSettings() 002ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 288ms
And Set token of apiUsername "super-admin-piast" 255ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 155ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 027ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 521ms
Then Login as "super-admin-piast" 2s 406ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 334ms
After Hooks.deleteTransportAfterApiTest() 707ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 340ms
And Set token of apiUsername "super-admin-piast" 258ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 153ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 025ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 448ms
Then Login as "super-admin-piast" 2s 252ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 355ms
After Hooks.deleteTransportAfterApiTest() 628ms
After Hooks.rollbackSettings() 000ms
View Feature Filters
Given Set token of apiUsername "super-admin-neuca" 252ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 230ms
And Mark custom fields as not obligatory 005ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 125ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 024ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 21s 111ms
Then Login as "neuca-admin" 2s 281ms
And Go to "TRANSPORT_TABLE" 508ms
And Confirm statuses until reach "process-ended" 21s 390ms
Then Check if sorting by 'Finished' status is working correctly 232ms
After Hooks.deleteTransportsAfterTest() 2s 344ms
After Hooks.rollbackAllCustomFieldsSettings() 368ms
After Hooks.rollbackSettings() 136ms
View Feature Invitation
Given Set token of apiUsername "super-admin-piast" 254ms
And Delete invitations with email "automaty31415@test.pl" 014ms
And If user is login then logout 240ms
Given Set token of apiUsername "super-admin-piast" 286ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 144ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 144ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 413ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 654ms
Then Go to "INVITATIONS_TAB" 466ms
And Go to "EXPIRED_TAB" invitation status tab 239ms
Then Invitation is displayed on list "automaty31415@test.pl" 408ms
After Hooks.deleteInvitationAfterTest() 164ms
After Hooks.rollbackSettings() 120ms
View Feature DedicatedWindow
Given Set token of apiUsername "super-admin-skz" 236ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 125ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 323ms
And Prepare setting for automatic time window delete with "super-admin-skz" 206ms
When Login as "swisskrono-admin" 7s 860ms
And Go to "WAREHOUSE_TAB" 971ms
Then Check if dedicated window is deleted from schedule 48s 330ms
After Hooks.rollbackSettings() 272ms
View Feature Move transport to archive
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 591ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 018ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 186ms
And Set proper delay time to move order to archive after task timeout 144ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 2s 032ms
And Go to "WAREHOUSE_TAB" 1s 112ms
And Change warehouse in schedule to: "Katowice" 1s 956ms
And Wait "60" seconds 1m
And Verify that transport window is grey 078ms
And Verify that transport is in archive 6s 788ms
Then Restore transport from archive 2s 644ms
And Verify that transport has been successfully restored 15s 635ms
After Hooks.deleteTransportAfterTest() 839ms
After Hooks.rollbackSettings() 156ms
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" 236ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 117ms
And Mark custom fields as not obligatory 006ms
And Login as "dayco-admin" 2s 222ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 997ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 143ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 029ms
When Go to "TRANSPORT_TABLE" 359ms
And Click button advice in transport table "OWN_COLLECTION" 1s 612ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 765ms
And Go to "TRANSPORT_TABLE" 427ms
And Find transport in table with status "planned-magazyn-tychy" 3s 693ms
And Confirm statuses until reach "process-ended" 16s 598ms
And Wait "12" seconds 12s
Then Go to "ARCHIVE_TAB" 602ms
And Show "OWN_COLLECTION" 184ms
And Verify that created transport is "true" in transport table 1m 32s 346ms
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() 700ms
After Hooks.rollbackAllCustomFieldsSettings() 434ms
After Hooks.rollbackSettings() 130ms