Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.57	27 cze 2021, 06:33

	Steps	Scenarios	Features
@rollbackSettings	77	1	0	0	0	78	7	1	8	6m 58s 261ms	Failed

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 267ms

And Set token of apiUsername "super-admin-piast" 240ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 262ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 038ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 406ms

Then Login as "super-admin-piast" 3s 177ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 407ms

Hooks

After Hooks.deleteTransportAfterApiTest() 817ms

After Hooks.rollbackSettings() 002ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 250ms

And Set token of apiUsername "super-admin-piast" 240ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 171ms

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 345ms

Then Login as "super-admin-piast" 2s 386ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 423ms

Hooks

After Hooks.deleteTransportAfterApiTest() 788ms

After Hooks.rollbackSettings() 000ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 251ms

And Set token of apiUsername "super-admin-piast" 234ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 151ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 030ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 357ms

Then Login as "super-admin-piast" 2s 214ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 344ms

Hooks

After Hooks.deleteTransportAfterApiTest() 749ms

After Hooks.rollbackSettings() 000ms

View Feature Filters

@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

Scenario Outline Check if sorting by "Finished" status is working correctly [A-7517]

Steps

Given Set token of apiUsername "super-admin-neuca" 217ms

And Get custom field settings for "DELIVERY" transport type and "neuca" company 175ms

And Mark custom fields as not obligatory 006ms

And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 138ms

And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 031ms

When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 21s 152ms

Then Login as "neuca-admin" 2s 230ms

And Go to "TRANSPORT_TABLE" 482ms

And Confirm statuses until reach "process-ended" 17s 171ms

Then Check if sorting by 'Finished' status is working correctly 295ms

Hooks

After Hooks.deleteTransportsAfterTest() 2s 762ms

After Hooks.rollbackAllCustomFieldsSettings() 390ms

After Hooks.rollbackSettings() 122ms

View Feature Invitation

@rollbackSettings @deleteInvitationAfterTest

Scenario Outline Check if expired invitation is visible in expired tab

Steps

Given Set token of apiUsername "super-admin-piast" 231ms

And Delete invitations with email "automaty31415@test.pl" 023ms

And If user is login then logout 267ms

Given Set token of apiUsername "super-admin-piast" 248ms

And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 145ms

Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 141ms

And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 338ms

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 512ms

Then Go to "INVITATIONS_TAB" 526ms

And Go to "EXPIRED_TAB" invitation status tab 300ms

Then Invitation is displayed on list "automaty31415@test.pl" 470ms

Hooks

After Hooks.deleteInvitationAfterTest() 250ms

After Hooks.rollbackSettings() 124ms

View Feature DedicatedWindow

@rollbackSettings

Scenario Outline Check if dedicated window is automatically deleted from schedule

Steps

Given Set token of apiUsername "super-admin-skz" 247ms

And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 129ms

And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 314ms

And Prepare setting for automatic time window delete with "super-admin-skz" 198ms

When Login as "swisskrono-admin" 7s 920ms

And Go to "WAREHOUSE_TAB" 860ms

Then Check if dedicated window is deleted from schedule 1m 6s 290ms

Hooks

After Hooks.rollbackSettings() 298ms

View Feature Move transport to archive

@rollbackSettings @deleteTransportAfterTest

Scenario Outline Check if delayed transport is moved to archived and can be restored

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 248ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 015ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 134ms

And Set proper delay time to move order to archive after task timeout 126ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 937ms

And Go to "WAREHOUSE_TAB" 1s 232ms

And Change warehouse in schedule to: "Katowice" 1s 527ms

And Wait "60" seconds 1m

And Verify that transport window is grey 083ms

And Verify that transport is in archive 9s 393ms

Then Restore transport from archive 2s 542ms

And Verify that transport has been successfully restored 15s 626ms

Hooks

After Hooks.deleteTransportAfterTest() 959ms

After Hooks.rollbackSettings() 126ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

Scenario Outline Check if confirming transport status removed it to the archive

Steps

Given Set token of apiUsername "super-admin-dayco" 219ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 109ms

And Mark custom fields as not obligatory 005ms

And Login as "dayco-admin" 1s 960ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 093ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 127ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 033ms

When Go to "TRANSPORT_TABLE" 402ms

And Click button advice in transport table "OWN_COLLECTION" 1s 397ms

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 990ms

And Go to "TRANSPORT_TABLE" 456ms

And Find transport in table with status "planned-magazyn-tychy" 3s 688ms

And Confirm statuses until reach "process-ended" 13s 631ms

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 528ms

And Show "OWN_COLLECTION" 173ms

And Verify that created transport is "true" in transport table 1m 32s 270ms

Error message

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:116)
	at ✽.Verify that created transport is "true" in transport table(file:Features/Atom/Transport/Archive.feature:54)

Hooks

After Hooks.deleteTransportAfterTest() 997ms

After Hooks.rollbackAllCustomFieldsSettings() 468ms

After Hooks.rollbackSettings() 143ms

	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 58s 261ms	Failed

Tag Report