HN user

alexgandy

47 karma

alexgandy.com

Posts4
Comments32
View on HN

As far as the "what to do with flaky tests", I error on the side of just outright killing the tests. Unless it's an absolutely crucial business case, I'd rather have no test than a test that slowly degrades trust.

For what it's worth, I've been working on a side-project to try to help with almost this exact situation and would be really interested if it could help you; https://gaffer.sh

Thanks for the detailed response.

I think a lot of companies have some portion of their code that's been avoided for a variety of reasons. I think adding unit tests, simple automated tests and quick CI processes can really alleviate that fear...so eventually that section can be refactored (or moved to a service, etc).

I appreciate what you're saying about needed to be more deeply connected with the code for truly valid tests. What I'm wondering is if there's a happy middle ground where code shops just want basic coverage around their code.

True Crime - Last Podcast on the Left - Criminal - Crimetown

Random Info - Radiolab - 99% Invisible

Interviews - WTF w/ Marc Maron - Joe Rogan (depending on the guest) - The Nerdist (depending on the guest)

I've used theGlutenless.com, a gluten-free business directory, as a testing ground for new technologies for the past few years. I built a custom bot for discovering gluten free businesses so it basically auto-populates. At the moment, I don't really have the time or motivation to do anything with it...