Project

Profile

Help

Story #6203

Can't run tests in development without first running a few steps

Added by daviddavis about 1 month ago. Updated about 1 month ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

With merging [0] and [1], you can no longer just run tests in development. You have to first perform a couple steps like generating and installing the bindings. We either need docs and/or an alias that will take care of generating/installing the bindings, setting up the fixture container, etc.

[0] https://pulp.plan.io/issues/6032 [1] https://github.com/pulp/ansible-pulp/pull/223

History

#1 Updated by fabricio.aguiar about 1 month ago

if the plugin is specified on pulp_install_plugins, bindings will be automatically generated https://github.com/pulp/ansible-pulp/blob/master/roles/pulp-devel/tasks/bashrc.yml#L36-L43

#2 Updated by bmbouter about 1 month ago

I was thinking we could have the tests generate the bindings themselves as a pre-test step. Then when running any number of tests, it builds the bindings as the first step and then uses them for the duration of the test run.

This would allow us to receive this feature in the develpoment environment, on travis and github CI's, and downstream packagers too. When packaging Pulp for say Debian, you want to apply a limited number of upstream patches and you need to run the tests when you do.

#3 Updated by daviddavis about 1 month ago

  • Tracker changed from Issue to Story
  • % Done set to 0

Please register to edit this issue

Also available in: Atom PDF