Deprecated features need to be tested even when not enabled

Registered by Matt Borland

A requirement of the Angular work to be made live is that the deprecated work continue to be tested while it is still in deprecation. To best support this, tests of the deprecated work must still operate within reason. However, due to things like Django routes, we can't, for example, perform selenium tests of both Angular and deprecated work simultaneously within the same configuration. Thus it is suggested that we break out tests of deprecated work into its own set of tests.

Blueprint information

Status:
Complete
Approver:
Travis Tripp
Priority:
High
Drafter:
Matt Borland
Direction:
Approved
Assignee:
Matt Borland
Definition:
Review
Series goal:
Accepted for 10.0.0-newton
Implementation:
Implemented
Milestone target:
milestone icon newton-3
Started by
Travis Tripp
Completed by
Rob Cresswell

Related branches

Sprints

Whiteboard

Summary
=======
Tests jobs that test deprecated code need to be set up.

Motivation
========
Client-side (Angular) content will replace legacy code (and routes, etc.) but there's an interest in testing the old deprecated code while it still lingers. The best way to do that is to separate out the tests for the old deprecated code.

Description
=========
The plan is this:
1) Unit tests just need to continue being tested 'as-is' by ensuring that the test settings.py uses the 'legacy' panels when appropriate. Remember that the Angular unit tests are run in npm.

2) Create pre-test hooks that modify the HORIZON_CONFIG to enable the appropriate deprecated panels. Modify the integration test's horizon.conf to use the 'legacy' settings.

3) Create a separate integration test that tests Horizon with the deprecated panels.
  a) This needs to appropriately pass a flag to the pre-test hooks so it executes #2 above.

UX
===
n/a

Wireframes, Mocks, Videos and UI Markup
---------------------------------------------------------
n/a

Testing
======
This is self-testing.

Outside Dependencies
==================
none

Requirements Update Required
========================
none

Doc Impact
=========
I'm unaware of any doc impact. These are just more jobs. Perhaps we should document how one deprecates old code.

Gerrit topic: https://review.openstack.org/#q,topic:bp/test-deprecated-features,n,z

Addressed by: https://review.openstack.org/349020
    Pre-test hook for integration tests/deprecated

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.