This information is from the code coverage report (see http://coverage.cwgordon.com/coverage).
We need to test:
1) Multiple actions firing at once,
2) Firing actions in a loop (make sure it aborts).
3) Orphaning of actions (base module deleted).
This information is from the code coverage report (see http://coverage.cwgordon.com/coverage).
We need to test:
1) Multiple actions firing at once,
2) Firing actions in a loop (make sure it aborts).
3) Orphaning of actions (base module deleted).
Comments
Comment #1
cwgordon7 commentedBumping to critical on behalf of chx.
Comment #2
catchI'm restricting this to the first item on the list.
#296322: Tests for abort of actions firing in a loop + trigger module API is completely broken + fix
#296318: TestingParty08: Orphaning of actions
Comment #3
damien tournoud commentedComment #4
kscheirerI'm a little new to the actions system, could you describe how to cause such an event to occur that we can test for? I'm assuming this would collide somewhere in actions_do()?
Comment #5
cwgordon7 commentedSorry, I didn't mean literally firing at once, just when there are two or more actions assigned to a single trigger - do both actions fire properly? (Note: they fire in no specific order, that is expected).
Comment #6
catchMoving this out of the critical bugs queue - see #607038: Meta issue: fix gaps in code coverage.