Actions
Test #6430
closedTest "task groups"
Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Version:
Platform Release:
Tags:
Sprint:
Quarter:
Description
Ticket moved to GitHub: "pulp/pulpcore/1878":https://github.com/pulp/pulpcore/issues/1878
Task group functionality was added without tests, because it is difficult to test via the standard means. Task groups are a plugin-api-only feature so the only way to test this would be:
- manually set them up in the database
- in the "using plugin" section of the functional tests, run tests against a plugin that uses task groups
- bmbouter suggests:
One idea I had for the automated tests is that we should have some way for them to load additional viewsets and tasks in the RQ registry if there is a PULP_TEST env var set or something. Something that keeps them unloaded on production systems and the tests automatically skip if they aren't loaded. Just an idea I had.
Related issues
Updated by dalley over 4 years ago
- Related to Story #6414: As a user, I can keep track of a group of tasks added
Updated by pulpbot over 2 years ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
Actions