Project Number Date
ApolloFullRunnerReport apollo-test-2.64 01 lip 2021, 04:35

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 13s 256ms Failed
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" 254ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 248ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" 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 373ms
Then Login as "super-admin-piast" 10s 256ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 552ms
After Hooks.deleteTransportAfterApiTest() 1s 050ms
After Hooks.rollbackSettings() 002ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 246ms
And Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 204ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_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 412ms
Then Login as "super-admin-piast" 2s 560ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 379ms
After Hooks.deleteTransportAfterApiTest() 713ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 245ms
And Set token of apiUsername "super-admin-piast" 229ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 164ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 023ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 306ms
Then Login as "super-admin-piast" 2s 647ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 350ms
After Hooks.deleteTransportAfterApiTest() 792ms
After Hooks.rollbackSettings() 000ms
View Feature Filters
Given Set token of apiUsername "super-admin-neuca" 237ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 192ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 135ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 025ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 21s 234ms
Then Login as "neuca-admin" 2s 234ms
And Go to "TRANSPORT_TABLE" 481ms
And Confirm statuses until reach "process-ended" 22s 265ms
Then Check if sorting by 'Finished' status is working correctly 297ms
After Hooks.deleteTransportsAfterTest() 2s 787ms
After Hooks.rollbackAllCustomFieldsSettings() 359ms
After Hooks.rollbackSettings() 123ms
View Feature Invitation
Given Set token of apiUsername "super-admin-piast" 233ms
And Delete invitations with email "automaty31415@test.pl" 017ms
And If user is login then logout 287ms
Given Set token of apiUsername "super-admin-piast" 254ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 188ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 147ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 351ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 627ms
Then Go to "INVITATIONS_TAB" 491ms
And Go to "EXPIRED_TAB" invitation status tab 289ms
Then Invitation is displayed on list "automaty31415@test.pl" 441ms
After Hooks.deleteInvitationAfterTest() 164ms
After Hooks.rollbackSettings() 124ms
View Feature DedicatedWindow
Given Set token of apiUsername "super-admin-skz" 228ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 127ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 302ms
And Prepare setting for automatic time window delete with "super-admin-skz" 195ms
When Login as "swisskrono-admin" 7s 819ms
And Go to "WAREHOUSE_TAB" 842ms
Then Check if dedicated window is deleted from schedule 1m 9s 559ms
After Hooks.rollbackSettings() 209ms
View Feature Move transport to archive
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 406ms
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" 119ms
And Set proper delay time to move order to archive after task timeout 129ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 980ms
And Go to "WAREHOUSE_TAB" 1s 033ms
And Change warehouse in schedule to: "Katowice" 1s 523ms
And Wait "60" seconds 1m
And Verify that transport window is grey 087ms
And Verify that transport is in archive 5s 211ms
Then Restore transport from archive 2s 520ms
And Verify that transport has been successfully restored 15s 598ms
After Hooks.deleteTransportAfterTest() 885ms
After Hooks.rollbackSettings() 114ms
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" 230ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 113ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 147ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 109ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 132ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 032ms
When Go to "TRANSPORT_TABLE" 397ms
And Click button advice in transport table "OWN_COLLECTION" 1s 396ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 791ms
And Go to "TRANSPORT_TABLE" 452ms
And Find transport in table with status "planned-magazyn-tychy" 3s 698ms
And Confirm statuses until reach "process-ended" 16s 645ms
And Wait "12" seconds 12s
Then Go to "ARCHIVE_TAB" 503ms
And Show "OWN_COLLECTION" 169ms
And Verify that created transport is "true" in transport table 1m 32s 302ms
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() 1s 015ms
After Hooks.rollbackAllCustomFieldsSettings() 466ms
After Hooks.rollbackSettings() 154ms