You’ve probably been writing unit tests for years, and they usually pass, right? But what if I told you that many of those tests might actually be hurting your code instead of helping?
So, what does it really mean for a test to be effective? That’s a great question — and one most of us have avoided thinking about for a long time. If the answer was simple, I’d have shared it and retired by now!
Join Abhijit Sonawane for an interactive session at the upcoming Sahaj Software DevDay in Pune, where we’ll take a hard look at your test cases and ask:
Why the standard way of writing unit tests is basically a masterclass in pain and regret
How applying clean code rules to tests can turn them into unreadable messes (ironic, right?)
Why having one assertion per test is not overkill, unless you enjoy debugging 12 things at once
How test fixtures can be your best friend… until they go rogue and take your suite down with them
How naming your test method like testPositiveCase() is not helping anyone
What You’ll Take Away
You’ll walk away with a fresh way of looking at your test suite — knowing what’s worth keeping, what needs fixing, and what should probably just be deleted.
You’ll start to see the difference between tests that help you move fast and those that just sit there looking green and lying to you.
You’ll get better at spotting tests that feel off — even if they pass — and learn what to do about them.
You’ll learn why naming, structure, and clarity matter more than clever test setups or strict rules.
And most importantly, you’ll feel more confident making decisions about tests: when to trust them, when to rewrite them, and when to just start fresh.
Who Should Attend
Anyone who’s ever written a test and wants to find out what they might have been doing wrong — and how to fix it.
Schedule
10:00 am – 10:30 am: Registrations and Breakfast
10:30 am – 12:00 pm: Talk
12:00 pm – 12:30 pm: Q&A and Networking
12:30 pm onwards: Lunch
