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

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 53s 335ms Failed
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 270ms
And Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 260ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" 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 495ms
Then Login as "super-admin-piast" 9s 229ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 392ms
After Hooks.deleteTransportAfterApiTest() 713ms
After Hooks.rollbackSettings() 001ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 262ms
And Set token of apiUsername "super-admin-piast" 236ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 169ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_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 455ms
Then Login as "super-admin-piast" 2s 350ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 416ms
After Hooks.deleteTransportAfterApiTest() 701ms
After Hooks.rollbackSettings() 000ms
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" 227ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 157ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 029ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 445ms
Then Login as "super-admin-piast" 2s 309ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 357ms
After Hooks.deleteTransportAfterApiTest() 672ms
After Hooks.rollbackSettings() 000ms
View Feature Filters
Given Set token of apiUsername "super-admin-neuca" 239ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 180ms
And Mark custom fields as not obligatory 007ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 147ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 029ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 20s 872ms
Then Login as "neuca-admin" 2s 054ms
And Go to "TRANSPORT_TABLE" 473ms
And Confirm statuses until reach "process-ended" 22s 185ms
Then Check if sorting by 'Finished' status is working correctly 298ms
After Hooks.deleteTransportsAfterTest() 2s 431ms
After Hooks.rollbackAllCustomFieldsSettings() 350ms
After Hooks.rollbackSettings() 125ms
View Feature Invitation
Given Set token of apiUsername "super-admin-piast" 232ms
And Delete invitations with email "automaty31415@test.pl" 014ms
And If user is login then logout 265ms
Given Set token of apiUsername "super-admin-piast" 255ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 127ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 134ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 201ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 506ms
Then Go to "INVITATIONS_TAB" 460ms
And Go to "EXPIRED_TAB" invitation status tab 239ms
Then Invitation is displayed on list "automaty31415@test.pl" 451ms
After Hooks.deleteInvitationAfterTest() 154ms
After Hooks.rollbackSettings() 119ms
View Feature DedicatedWindow
Given Set token of apiUsername "super-admin-skz" 300ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 122ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 307ms
And Prepare setting for automatic time window delete with "super-admin-skz" 226ms
When Login as "swisskrono-admin" 7s 771ms
And Go to "WAREHOUSE_TAB" 842ms
Then Check if dedicated window is deleted from schedule 51s 046ms
After Hooks.rollbackSettings() 199ms
View Feature Move transport to archive
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 670ms
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" 154ms
And Set proper delay time to move order to archive after task timeout 123ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 871ms
And Go to "WAREHOUSE_TAB" 1s 008ms
And Change warehouse in schedule to: "Katowice" 1s 592ms
And Wait "60" seconds 1m
And Verify that transport window is grey 063ms
And Verify that transport is in archive 6s 301ms
Then Restore transport from archive 2s 606ms
And Verify that transport has been successfully restored 15s 595ms
After Hooks.deleteTransportAfterTest() 751ms
After Hooks.rollbackSettings() 101ms
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" 228ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 100ms
And Mark custom fields as not obligatory 004ms
And Login as "dayco-admin" 2s 049ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 988ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 147ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 032ms
When Go to "TRANSPORT_TABLE" 355ms
And Click button advice in transport table "OWN_COLLECTION" 1s 512ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 670ms
And Go to "TRANSPORT_TABLE" 485ms
And Find transport in table with status "planned-magazyn-tychy" 3s 659ms
And Confirm statuses until reach "process-ended" 16s 532ms
And Wait "12" seconds 12s
Then Go to "ARCHIVE_TAB" 489ms
And Show "OWN_COLLECTION" 154ms
And Verify that created transport is "true" in transport table 1m 32s 315ms
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() 918ms
After Hooks.rollbackAllCustomFieldsSettings() 457ms
After Hooks.rollbackSettings() 137ms