Actions
Issue #6451
closed
Our functional tests use settings from django.conf which may not be accurate
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 70
Quarter:
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
Updated by daviddavis over 4 years ago
- Related to Issue #6450: Checking storage in tests uses incorrect value added
Updated by fao89 over 4 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 70
Updated by pulpbot over 4 years ago
- Status changed from NEW to POST
Added by mdellweg over 4 years ago
Added by mdellweg over 4 years ago
Revision a8d8ea1d | View on GitHub
Make pulp config acessible to functional tests on travis
Improve formattig a little.
Updated by mdellweg over 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset plugin_template|a8d8ea1d8dc37dcb499306f5c4f11ddcc7627fc8.
Updated by mdellweg over 4 years ago
Applied in changeset pulpcore|72795671b822424dcc69e3d1a662b08786bb6ce0.
Updated by ttereshc over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
- Sprint/Milestone set to 3.3.0
Actions
.
Fix pulp config in tests
Regenerate travis config.
fixes #6451 https://pulp.plan.io/issues/6451