Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.59	29 cze 2021, 06:33

	Steps	Scenarios	Features
@rollbackSettings	83	2	0	0	0	85	7	2	9	7m 2s 571ms	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" 252ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 906ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 790ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 761ms

After Hooks.rollbackSettings() 000ms

View Feature API Transport

@deleteAllTransportsAfterTest @rollbackSettings @NIE_DZIAŁA_PRZEZ_A-7854

Scenario Outline Check if response code contains expected status after editing transport by Api with non unique erpIdentifier [A-7521]

Steps

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

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

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

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

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

When Edit transport by API-validation JSON file "EDIT_DELIVERY_WITH_FILLED_ERP_IDENTIFIER" as "super-admin-piast" with "nonUniqueERPId" for api version "v1" 349ms

Then Check if response status code equals "422" 001ms

Error message

org.junit.ComparisonFailure: Odpowiedź zawiera kod 404 zamiast 422 expected:<4[22]> but was:<4[04]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Api.ApiTransportTest.checkIfResponseStatusCodeEquals(ApiTransportTest.java:131)
	at ✽.Check if response status code equals "422"(file:Features/Api/Transport.feature:123)

Hooks

After Hooks.rollbackSettings() 002ms

After Hooks.deleteAllTransports() 1m 3s 459ms

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

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

And Mark custom fields as not obligatory 006ms

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

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

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

And Go to "TRANSPORT_TABLE" 495ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 652ms

After Hooks.rollbackAllCustomFieldsSettings() 337ms

After Hooks.rollbackSettings() 128ms

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

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

And If user is login then logout 263ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 488ms

And Go to "EXPIRED_TAB" invitation status tab 286ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 155ms

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

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

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

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

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

And Go to "WAREHOUSE_TAB" 913ms

Then Check if dedicated window is deleted from schedule 54s 197ms

Hooks

After Hooks.rollbackSettings() 221ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 015ms

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

And Wait "60" seconds 1m

And Verify that transport window is grey 084ms

And Verify that transport is in archive 10s 720ms

Then Restore transport from archive 2s 655ms

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

Hooks

After Hooks.deleteTransportAfterTest() 963ms

After Hooks.rollbackSettings() 119ms

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

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

And Mark custom fields as not obligatory 004ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 369ms

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

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 46s 591ms

And Go to "TRANSPORT_TABLE" 444ms

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

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

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 576ms

And Show "OWN_COLLECTION" 178ms

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

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

After Hooks.rollbackAllCustomFieldsSettings() 418ms

After Hooks.rollbackSettings() 141ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackSettings	83	2	0	0	0	85	7	2	9	7m 2s 571ms	Failed

Tag Report