---
title: "Comment by Arnold Holm on \"How Much Testing Is Enough? -Day 2 \" | Hashnode"
description: "Your last principle becomes concrete in an automated trading test: an entry condition can be correct while the requirement never says whether a restart may subm"
url: "https://hashnode.com/posts/how-much-testing-is-enough-day-2/6ac3b41840d8ddc1e18b0f06/comment/6ac3e4b9d320781effc617ea"
---

[Discussion](https://hashnode.com/posts/how-much-testing-is-enough-day-2/6ac3b41840d8ddc1e18b0f06)

Comment [How Much Testing Is Enough? -Day 2](https://hashnode.com/posts/how-much-testing-is-enough-day-2/6ac3b41840d8ddc1e18b0f06)

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 5](https://hashnode.com/posts/how-much-testing-is-enough-day-2/6ac3b41840d8ddc1e18b0f06/comment/6ac3e4b9d320781effc617ea)

Your last principle becomes concrete in an automated trading test: an entry condition can be correct while the requirement never says whether a restart may submit it again. I would put a positive case, a no-entry case and a restart-on-the-same-bar case beside that requirement before coding. That tests the intended behaviour rather than treating a green indicator calculation as proof that the whole bot is correct.

[Laiba Razi Khan](https://hashnode.com/@Laiba)

[Oct 6](https://hashnode.com/posts/how-much-testing-is-enough-day-2/6ac3b41840d8ddc1e18b0f06/comment/6ac3e4b9d320781effc617ea#reply-6ac50f3647d70f0794796272)

That's a really smart way to start, Arnold. Those three conditions are exactly what my rules were missing.

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 6](https://hashnode.com/posts/how-much-testing-is-enough-day-2/6ac3b41840d8ddc1e18b0f06/comment/6ac3e4b9d320781effc617ea#reply-6ac55435d3c31f529932d682)

For the restart case, write down what survives a process exit. If the signal was already acted on, a fresh process needs a saved marker or a broker check before it can send again. Test that after a completed send and after a timeout, because the timeout leaves the order state unknown.
