Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.58	28 cze 2021, 06:08

	Steps	Scenarios	Features
@rollbackSettings	77	1	0	0	0	78	7	1	8	7m 24s 869ms	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" 231ms

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

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

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

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

Then Login as "super-admin-piast" 7s 207ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 745ms

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" 247ms

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

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

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" 14s 063ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 712ms

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" 242ms

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

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

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_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 265ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 633ms

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" 221ms

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

And Mark custom fields as not obligatory 008ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 487ms

And Confirm statuses until reach "process-ended" 22s 114ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 834ms

After Hooks.rollbackAllCustomFieldsSettings() 312ms

After Hooks.rollbackSettings() 109ms

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" 225ms

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

And If user is login then logout 231ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 547ms

And Go to "EXPIRED_TAB" invitation status tab 280ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 241ms

After Hooks.rollbackSettings() 125ms

View Feature DedicatedWindow

@rollbackSettings

Scenario Outline Check if dedicated window is automatically deleted from schedule

Steps

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

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" 306ms

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

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

And Go to "WAREHOUSE_TAB" 893ms

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

Hooks

After Hooks.rollbackSettings() 300ms

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

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 022ms

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

And Wait "60" seconds 1m

And Verify that transport window is grey 078ms

And Verify that transport is in archive 11s 846ms

Then Restore transport from archive 2s 564ms

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

Hooks

After Hooks.deleteTransportAfterTest() 962ms

After Hooks.rollbackSettings() 123ms

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" 227ms

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

And Mark custom fields as not obligatory 007ms

And Login as "dayco-admin" 2s 164ms

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

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

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

When Go to "TRANSPORT_TABLE" 403ms

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

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

And Go to "TRANSPORT_TABLE" 463ms

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

And Confirm statuses until reach "process-ended" 16s 680ms

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 507ms

And Show "OWN_COLLECTION" 171ms

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

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() 1s 070ms

After Hooks.rollbackAllCustomFieldsSettings() 478ms

After Hooks.rollbackSettings() 141ms

	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 869ms	Failed

Tag Report