Task #3553: Move tests out of Pulp's application code - Pulp

Actions

Send by e-mail Copy link

Task #3553

closed

Move tests out of Pulp's application code

Added by bmbouter about 6 years ago. Updated over 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

dalley

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Yes

Sprint Candidate:

Tags:

Sprint:

Sprint 35

Quarter:

Description

The tests currently live at: https://github.com/pulp/pulp/tree/3.0-dev/pulpcore/pulpcore/app/tests

This is atypical. Usually tests live outside of the application code itself as a peer of it.

Since we do have two packages living in one repository, the existing tests would move from /pulpcore/pulpcore/app/tests to /pulpcore/tests/. Eventually we would add plugin API tests in /plugin/tests/

Actions

Copy link

Updated by bmbouter about 6 years ago

Description updated (diff)

Actions

Copy link

Updated by daviddavis about 6 years ago

Groomed changed from No to Yes
Sprint set to Sprint 35

Actions

Copy link

Updated by dalley about 6 years ago

Status changed from NEW to ASSIGNED
Assignee set to dalley

Actions

Copy link

Updated by dalley about 6 years ago

Status changed from ASSIGNED to POST

https://pulp.plan.io/issues/3553

Actions

Copy link

Updated by dalley about 6 years ago

This exact scheme doesn't work because the tests/pulpcore package mirrors the pulpcore package and attempts to import the code from tests/pulpcore, which fails.

What we really want is just to move the tests from pulpcore/app/tests to pulpcore/tests. That is the proper structure since both pulpcore and pulpcore-plugin are their own separate python packages.