Cucumber-JVM Reports - Feature: Assortment Group

Project	Number	Date
ApolloFullRunnerReport	develop.361	28 mar 2021, 06:40

	Steps	Scenarios	Features
Assortment Group	53	1	0	0	0	54	6	1	7	2m 9s 277ms	Failed

@deleteAssortmentGroupAfterTest

Scenario Outline Check if it is possible to create an assortment group

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 137ms

And Go to "SETTINGS_TAB" 382ms

And Go to warehouse "Magazyn Surowców" 1s 162ms

When Add assortment group to "Magazyn Surowców" with all transport type linked 2s 704ms

And Check if created assortment group is visible in warehouse settings 027ms

And If user is login then logout 086ms

And Login as "pka1-carrier" 2s 137ms

And Go to "TRANSPORT_TABLE" 108ms

Then Go to new transport "TANKER_GRANULATE_DELIVERY" 279ms

And Check if new assortment group can be selected in transport form 118ms

Hooks

After Hooks.deleteAssortmentGroupAfterTest() 054ms

@deleteAssortmentGroupAfterTest

Scenario Outline Check if it is possible to edit an assortment group

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 796ms

And Go to "SETTINGS_TAB" 245ms

And Go to warehouse "Magazyn Surowców" 1s 173ms

When Add assortment group to "Magazyn Surowców" with all transport type linked 2s 395ms

And Check if created assortment group is visible in warehouse settings 033ms

And Go to assortment group settings 080ms

And Edit created assortment group - set namePl to "Edycja" 441ms

Then Go to new transport "TANKER_GRANULATE_DELIVERY" 254ms

And Check if edited assortment group "Edycja" can be selected in transport form 129ms

Hooks

After Hooks.deleteAssortmentGroupAfterTest() 042ms

@deleteAssortmentGroupAfterTest

Scenario Outline Check if it is possible to delete created assortment group

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 847ms

And Go to "SETTINGS_TAB" 260ms

And Go to warehouse "Magazyn Surowców" 1s 198ms

When Add assortment group to "Magazyn Surowców" with all transport type linked 2s 390ms

And Check if created assortment group is visible in warehouse settings 025ms

And Go to assortment group settings 067ms

Then Delete created assortment group 2s 358ms

And Go to new transport "TANKER_GRANULATE_DELIVERY" 305ms

And Check if deleted assortment group can't be selected in transport form 15s 111ms

Hooks

After Hooks.deleteAssortmentGroupAfterTest() 031ms

@deleteAssortmentGroupAfterTest

Scenario Outline Check if assortment group can't be selected in transport form after disabling transport type in this assortment group

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 052ms

And Go to "SETTINGS_TAB" 258ms

And Go to warehouse "Magazyn Surowców" 1s 160ms

When Add assortment group to warehouse with selected "TANKER_GRANULATE_DELIVERY" 2s 223ms

And Check if created assortment group is visible in warehouse settings 024ms

And Refresh page 2s 120ms

Then Go to new transport "TANKER_GRANULATE_DELIVERY" 330ms

And Check if assortment group can be selected in transport form 140ms

And Close transport details 15s 111ms

And Go to new transport "UNLOAD" 272ms

And Select warehouse in transport form "Magazyn Surowców" 351ms

And Check if assortment group can't be selected in transport form 15s 139ms

Hooks

After Hooks.deleteAssortmentGroupAfterTest() 055ms

Scenario Outline Check if assortment group select is obligatory in new transport form

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 196ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 347ms

Then Check if new assortment group is obligatory in transport form 1s 079ms

@deleteTransportAfterTest

Scenario Outline Check if assortment group select is disabled when transport is during edition

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 037ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 432ms

When Go to "TRANSPORT_TABLE" 142ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 384ms

Then Check if new assortment group is disabled in transport form 030ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

Scenario Outline Check if only the group hours are displayed in the schedule

Steps

Given Get inputs from database "CREATE_TANKER_GRANULATE_DELIVERY_ASSORTMENT_GROUP_SUPPLIER" "super-admin-keeeper" 002ms

And Login as "dka1-supplier" and set token of apiUsername "super-admin-keeeper" 1s 920ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 278ms

And Fill transport form 23s 213ms

And Click "save-transport" save button and wait for form to disappear 15s 642ms

Then Check if only the assortment group hours are available for advice in the schedule 120ms

Error message

java.lang.AssertionError: Blokada poza czasem na grupę asortymentową ma różną długość od spodziewanej expected:<22> but was:<21>
	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 CucumberTests.Warehouse.AssortmentGroupTest.checkIfOnlyTheGroupHoursAreAvailableForAdviceInTheSchedule(AssortmentGroupTest.java:182)
	at ✽.Check if only the assortment group hours are available for advice in the schedule(file:Features/Atom/Warehouse/AssortmentGroup.feature:94)

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Assortment Group	53	1	0	0	0	54	6	1	7	2m 9s 277ms	Failed

Feature Report