Project

Profile

Help

Issue #6451

closed

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

Added by daviddavis over 2 years ago. Updated about 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
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

Related to Pulp - Issue #6450: Checking storage in tests uses incorrect valueCLOSED - CURRENTRELEASEmdellwegActions
Actions #1

Updated by daviddavis over 2 years ago

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

Updated by fao89 over 2 years ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 70
Actions #3

Updated by mdellweg over 2 years ago

  • Assignee set to mdellweg
Actions #4

Updated by pulpbot over 2 years ago

  • Status changed from NEW to POST

Added by mdellweg over 2 years ago

Revision 72795671

Fix pulp config in tests

Regenerate travis config.

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

Added by mdellweg over 2 years ago

Revision a8d8ea1d

Make pulp config acessible to functional tests on travis

Improve formattig a little.

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

Actions #5

Updated by mdellweg over 2 years ago

  • Status changed from POST to MODIFIED
Actions #7

Updated by ttereshc over 2 years ago

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

Also available in: Atom PDF