Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.46	19 cze 2021, 05:43

	Steps	Scenarios	Features
@rollbackSettings	72	1	0	0	0	73	7	1	8	7m 26s 293ms	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" 600ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 968ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 687ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 692ms

After Hooks.rollbackSettings() 000ms

View Feature Filters

@deleteTransportsAfterTest @rollbackSettings

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 setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 132ms

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" 21s 022ms

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

And Go to "TRANSPORT_TABLE" 472ms

And Confirm statuses until reach "process-ended" 18s 327ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 389ms

After Hooks.rollbackSettings() 119ms

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

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

And If user is login then logout 15s 119ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 695ms

And Go to "EXPIRED_TAB" invitation status tab 300ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 150ms

After Hooks.rollbackSettings() 126ms

View Feature DedicatedWindow

@rollbackSettings

Scenario Outline Check if dedicated window is automatically deleted from schedule

Steps

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

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

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

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

When Login as "swisskrono-admin" 2s 546ms

And Go to "WAREHOUSE_TAB" 1s 015ms

Then Check if dedicated window is deleted from schedule 1m 21s 424ms

Hooks

After Hooks.rollbackSettings() 284ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 998ms

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

And Wait "60" seconds 1m

And Verify that transport window is grey 085ms

And Verify that transport is in archive 6s 245ms

Then Restore transport from archive 2s 496ms

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

Hooks

After Hooks.deleteTransportAfterTest() 887ms

After Hooks.rollbackSettings() 123ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings

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

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 2s 418ms

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

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

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

When Go to "TRANSPORT_TABLE" 414ms

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

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

And Go to "TRANSPORT_TABLE" 557ms

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

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

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 498ms

And Show "OWN_COLLECTION" 172ms

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

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:51)

Hooks

After Hooks.deleteTransportAfterTest() 794ms

After Hooks.rollbackSettings() 133ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackSettings	72	1	0	0	0	73	7	1	8	7m 26s 293ms	Failed

Tag Report