Test #6431
Updated by pulpbot almost 3 years ago
**Ticket moved to GitHub**: "pulp/pulpcore/1879":https://github.com/pulp/pulpcore/issues/1879 ---- Task parentage functionality was added without tests, because it is difficult to test via the standard means. Task parent/child relationships can only be set up through the plugin API, 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. We need to test that task parent/child relationships show up appropriately in the serializer. Since task parentage is only exposed through the
.