Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.50	30 cze 2021, 09:31

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 797ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 792ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 780ms

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

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

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

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

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

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

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:133)
	at ✽.Check if response status code equals "422"(file:Features/Api/Transport.feature:136)

Hooks

After Hooks.rollbackSettings() 002ms

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

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

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

And Mark custom fields as not obligatory 006ms

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

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

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

And Go to "TRANSPORT_TABLE" 471ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 702ms

After Hooks.rollbackAllCustomFieldsSettings() 343ms

After Hooks.rollbackSettings() 147ms

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

And If user is login then logout 273ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 491ms

And Go to "EXPIRED_TAB" invitation status tab 303ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 154ms

After Hooks.rollbackSettings() 123ms

View Feature DedicatedWindow

@rollbackSettings

Scenario Outline Check if dedicated window is automatically deleted from schedule

Steps

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

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

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

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

And Go to "WAREHOUSE_TAB" 903ms

Then Check if dedicated window is deleted from schedule 1m 18s 459ms

Hooks

After Hooks.rollbackSettings() 213ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 046ms

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

And Wait "60" seconds 1m

And Verify that transport window is grey 091ms

And Verify that transport is in archive 10s 822ms

Then Restore transport from archive 2s 622ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 023ms

After Hooks.rollbackSettings() 117ms

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

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

And Mark custom fields as not obligatory 006ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 331ms

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

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

And Go to "TRANSPORT_TABLE" 458ms

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

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

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 502ms

And Show "OWN_COLLECTION" 170ms

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

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

After Hooks.rollbackAllCustomFieldsSettings() 468ms

After Hooks.rollbackSettings() 144ms

	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 25s 349ms	Failed

Tag Report