Change Details

As a **developer**, **I want** to rely on my tests, **so that** template changes in production templates are reflected in tests **and** HTML changes do not affect my tests too much. Acceptance Criteria: - `/skins/test/templates` folder is removed - all tests are green - DOM/CSS selectors or JSON checks are used for checking for necessary content - The default skin is tested, but when a skin A/B test is active, the other skin is either also tested or skipped. Background: Using separate templates without HTML in the tests can only check if variables are assigned - logic and desired output in the production templates is not tested. This has lead to some unnoticed errors in production and falsely passing tests during refactoring.

As a **developer**, **I want** to rely on my tests, **so that** template changes in production templates are reflected in tests **and** HTML changes do not affect my tests too much. Acceptance Criteria: - `/skins/test/templates` folder is removed - all tests are green - DOM and JSON checks are used for checking for assigned variables. See `UpdateAddressRouteTest::getDataApplicationVars` for an example, the method may be moved into a helper class or the `WebRouteTestCase` class. Background: We created logic-less test templates without or only minimal markup to make the integration tests independent from template logic. Now that all templating and behavioral logic has moved to the client side (Vue), the test templates are no longer necessary.

As a **developer**, **I want** to rely on my tests, **so that** template changes in production templates are reflected in tests **and** HTML changes do not affect my tests too much. Acceptance Criteria: - `/skins/test/templates` folder is removed - all tests are green - DOM/CSS selectors or and JSON checks are used for checking for necessary content - The default skin is tested,assigned variables. but when a skin A/B test is activeSee `UpdateAddressRouteTest::getDataApplicationVars` for an example, the other skin is either also tested or skippedmethod may be moved into a helper class or the `WebRouteTestCase` class. Background: Using separate templates without HTML in the tests can only check if variables are assigned - logic and desired output in the production templates is not tested. This has lead to some unnoticed errors in production and falsely passing tests during refactoringWe created logic-less test templates without or only minimal markup to make the integration tests independent from template logic. Now that all templating and behavioral logic has moved to the client side (Vue), the test templates are no longer necessary.