373 provdiding CRUD tests for Breadcrumb v2 component, adding needed …

[Danon9111]

…test pages, configurations and page objects

[Danon9111]

CRUD test for Breadcrumb component v2

Issue tracking: wttech/bobcat#373

[kaczymuczy]

I think you overkilled this component - you're testing multiple combinations and behaviors for this component, but what we're really supposed to test is if we can handle the configuration dialog forms with Bobcat. So instead of testing, if the component reacts properly when you increase a value, and then decrease the value, test if you can work with the dialog field for that value and if the component reflects that change.
translating into something different

• modifyAllProperties() - this test covers too much at the same time

• decreaseNavigationStartLevel(), increaseNavigationStartLevel() - only one of these is needed to check if we can handle the responsible dialog field

• hideCurrentPage(), showHiddenNavigationItems() - these both edit simple checkboxes, they can be merged into one test

• after applying the points above maybe it's possible to reduce the number of test pages?

Please remember - we're not covering the core components with tests. We're testing Bobcat to see if it's able to handle the configuration of core components.

[kaczymuczy]

Forgot to request changes :P

[kaczymuczy]

You assert that the current page is not displayed in the breadcrumb component, but you don't check if the hidden page is displayed in it, right? If so, then an assertion is missing