Need for better test coverage #118
Description
I've been working with cluster-turndown and noticed there's not much test coverage in the codebase. I started addressing this with a simple PR for the async package (#117), but it's just scratching the surface.
Most of the core functionality - providers, scheduler, strategies - lacks tests, which makes it harder to refactor or extend the code without breaking things. Even small changes could have unexpected impacts that are hard to catch without tests.
Would it make sense to focus on improving test coverage across the board? I'm thinking about working on more unit tests for the core packages and some integration tests to make sure everything works together properly. This would make the codebase more maintainable and extensible as new cloud providers or features get added.
Any thoughts on priority areas or suggestions for testing approach? I am willing to work on them and contribute them back.