Relocate test codes to match the structure of codes

Registered by Akihiro Motoki

At now, OpenStack dashboard test codes are placed randomly in most cases.
It would be really nice if a location of a corresponding test code is placed at a predictable location from a code to be tested.

This blueprint proposed that a unit test file for {TOP_MODULE}/{MODULE}/{FILENAME}.py will be located at {TOP_MODULE}/test/units/{MODULE}/test_{FILENAME}.py.

We sometimes would like to have a unit test which test a module as a whole. In this case, this blueprint proposes that such test is located at {TOP_MODULE}/test/units/{MODULE}/test_{MODULE}.py.

This clarifies locations of test files.

Blueprint information

Status:
Complete
Approver:
Ying Zuo
Priority:
Low
Drafter:
Akihiro Motoki
Direction:
Approved
Assignee:
Akihiro Motoki
Definition:
Approved
Series goal:
Accepted for 13.0.0-queens
Implementation:
Implemented
Milestone target:
milestone icon queens-3
Started by
Ying Zuo
Completed by
Akihiro Motoki

Related branches

Sprints

Whiteboard

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

Addressed by: https://review.openstack.org/522592
    horizon: Move test files to match corresponding module structure

Addressed by: https://review.openstack.org/522593
    openstack_auth: Move test files to match module structure

Addressed by: https://review.openstack.org/522594
    openstack_dashboard: Move test files to match module structure

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.