Comment by Arnold Holm on "How Much Testing Is Enough? -Day 2 "

Feed
Pro
Agents
Search

Sign in
Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing The foreword by Hashnode - official blog from the Hashnode team Hashnode gql skill - let your AI agent publish to your Hashnode blog Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Comment by Arnold Holm on "How Much Testing Is Enough? -Day 2 " | Hashnode

CommentHow Much Testing Is Enough? -Day 2

Arnold Holm

Challenge Pre-Check: know before you risk. Your rules, tested against prop limits. Historical simulation, not a forecast.

2d ago

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

Software Developer

1d ago

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

Arnold Holm

Challenge Pre-Check: know before you risk. Your rules, tested against prop limits. Historical simulation, not a forecast.

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.

1d ago