Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The fact that this can run in-process is a big deal, as it means you don't have to worry about cleanup.

As soon as you have external processes that your tests depend on, your tests need some sort of wrapper or orchestrator to set everything up before starting tests, and ideally tear it down after.

In 90% of cases I see, that orchestration is done in an extremely non-portable way (like leveraging tools built in to your CI system) which can make reproducing test failures a huge pain in the ass.



Your test framework probably provides you with hooks for one-time setup and cleanup. This is where you start and delete your external dependencies.


Again, every time I've seen that folks make non-portable assumptions about the environment.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: