Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.81	15 lip 2021, 06:54

	Steps	Scenarios	Features
@rollbackSettings	77	1	0	0	0	78	7	1	8	6m 57s 248ms	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" 262ms

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

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

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

Then Login as "super-admin-piast" 9s 822ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 685ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 604ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 694ms

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

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

And Mark custom fields as not obligatory 005ms

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

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" 20s 952ms

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

And Go to "TRANSPORT_TABLE" 510ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 381ms

After Hooks.rollbackAllCustomFieldsSettings() 395ms

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

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

And If user is login then logout 245ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 469ms

And Go to "EXPIRED_TAB" invitation status tab 289ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 142ms

After Hooks.rollbackSettings() 121ms

View Feature DedicatedWindow

@rollbackSettings

Scenario Outline Check if dedicated window is automatically deleted from schedule

Steps

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

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

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

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

When Login as "swisskrono-admin" 8s 043ms

And Go to "WAREHOUSE_TAB" 899ms

Then Check if dedicated window is deleted from schedule 51s 281ms

Hooks

After Hooks.rollbackSettings() 304ms

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

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 093ms

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

And Wait "60" seconds 1m

And Verify that transport window is grey 071ms

And Verify that transport is in archive 7s 014ms

Then Restore transport from archive 2s 708ms

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

Hooks

After Hooks.deleteTransportAfterTest() 771ms

After Hooks.rollbackSettings() 107ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings @FLAKY

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

Steps

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 337ms

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

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

And Go to "TRANSPORT_TABLE" 422ms

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

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

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 532ms

And Show "OWN_COLLECTION" 166ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 763ms

After Hooks.rollbackAllCustomFieldsSettings() 466ms

After Hooks.rollbackSettings() 129ms

	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 57s 248ms	Failed

Tag Report