Project

General

Profile

Actions

Feature #6517

closed

Dynflow tests dont execute sub plans

Added by Partha Aji almost 10 years ago. Updated almost 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Dynflow Action tests in general don't let us execute sub plans. Take the example of product delete, whose destroy plan does something like

1) Delete each repo of the product, using the repo delete orchestration
2) Delete candlepin artifacts.
3) Destroy the AR/elastic presence of the product

Now suppose I wanted to test the following scenario. "I want product delete to fail if one of the repo deletions fail due to some validation error". There is no way for me to test that. Because the action unit tests will not execute the repo delete orchestration.

Actions #1

Updated by Ivan Necas almost 10 years ago

I don't think this needs to be tested, as that's the properly of the Dynflow.

Actions #2

Updated by Ivan Necas almost 10 years ago

  • Status changed from New to Rejected

I would suggest for the unit tests to keep the behavior as it is. If we want some more complex tests, it should happen outside of the unit testing framework for the end-to-end tasks tests

Actions #3

Updated by Eric Helms over 9 years ago

  • translation missing: en.field_release set to 13
Actions #4

Updated by Eric Helms about 9 years ago

  • translation missing: en.field_release deleted (13)
Actions #5

Updated by Eric Helms almost 8 years ago

  • translation missing: en.field_release set to 166
Actions

Also available in: Atom PDF