Project

Profile

Help

Issue #6451

Our functional tests use settings from django.conf which may not be accurate

Added by daviddavis about 2 months ago. Updated about 2 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Severity:
2. Medium
Version:
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 70

Description

Imagine you have two environments: one running your pulp functional tests and one running your pulp server. This is the case in our CI. If you call settings.WHATEVER in the tests, you're going to get the value from the test runner environment instead of the actual pulp server.


Related issues

Related to Pulp - Issue #6450: Checking storage in tests uses incorrect value CLOSED - CURRENTRELEASE Actions

Associated revisions

Revision 72795671 View on GitHub
Added by mdellweg about 2 months ago

Fix pulp config in tests

Regenerate travis config.

fixes #6451 https://pulp.plan.io/issues/6451

Revision a8d8ea1d View on GitHub
Added by mdellweg about 2 months ago

Make pulp config acessible to functional tests on travis

Improve formattig a little.

fixes #6451 https://pulp.plan.io/issues/6451

History

#1 Updated by daviddavis about 2 months ago

  • Related to Issue #6450: Checking storage in tests uses incorrect value added

#2 Updated by fao89 about 2 months ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 70

#3 Updated by mdellweg about 2 months ago

  • Assignee set to mdellweg

#4 Updated by pulpbot about 2 months ago

  • Status changed from NEW to POST

#5 Updated by mdellweg about 2 months ago

  • Status changed from POST to MODIFIED

#7 Updated by ttereshc about 2 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
  • Sprint/Milestone set to 3.3.0

Please register to edit this issue

Also available in: Atom PDF