Make tests faster

[matifali]

Problem

Bun tests run sequentially and take 8-10 minutes. They are also flaky. Maybe, along with #308, we should migrate away from bun tests in as many modules as possible.

Suggested Solution

• Migrate away from bun testing in all modules where no coder_script is used. Epic: Migrate all modules from Bun tests to Terraform tests #308
• Make tests run in parallel (If possible)
• Found another faster testing method.

[DevelopmentCats]

I know a lot of the flakiness is from some of the tests not completing before they time out. Although the obvious resolution would be to extend those timeouts, this obviously would not address the long test times.

In reference to the tests though. I was thinking about whether we really even need these to be run in the workflows or not? They seem very useful for verifying if things function properly, but once the module is released they serve no purpose outside of internal/contributor development.

I feel like I have a few options off the top of my head.

1. We set up the CI so it only runs the tests in the directories for modules that were altered in the PR. ( Example: We have a PR for claude code. The CI only runs the Tests for Claude Code rather than every single test on every PR )

2. We remove the testing step from the CI and reserve it for contributors, and maintainers (Contributors would need to run tests and verify they pass themselves, and Maintainers would need to run the tests before Approving.) This would probably be more time consuming for me, but it would definitely speed the time it takes for the workflows to run

Ill look into some other options as well, but I just wanted to post my first thoughts

[matifali]

Let's go with option 1. There is a GitHub action that gives you file changes to run tests conditionally. We should also do #308 where applicable, as I expect that to be more stable(not faster)