Writing and debugging such tests is always an interesting challenge... Fortunately this exercise didn't unveil any problem in the newly written code, only some insidious problems in the test fixture itself. Which again highlights the necessity, that each *command instance* needs to be an independent clone from the original *command prototype*, since argument binding messages and trigger messages can appear in arbitrary order. |
||
|---|---|---|
| .. | ||
| asset | ||
| control | ||
| engine | ||
| mobject | ||
| play | ||