Setup integration testing #483
Conversation
There was a problem hiding this comment.
I will let @aeschright review the TypeScript details but these look sensible on first sight to me and I'm 💯 👍 for improving test coverage in general, so thank you for the work!
The only thing I'm worried about is bundling the 30M provider binary in the extension repo. I assume (hope) that it at least doesn't get included in the package distributed through the Marketplace, but even then my experience is that such technical debt is nearly impossible to address later. i.e. git history is immutable and we'll have to live with that decision practically forever.
Would calling init as part of the test complicate things a lot?
|
@radeksimko great point, that was included mostly by accident, I will amend the setup to calling init as part of the test |
Fix eslint suggestions
Add items to vscodeignore
appilon
force-pushed
the
integration-tests
branch
from
8b44d3c to
c363cd7
Compare
| case 'x64': | ||
| arch = 'amd64' | ||
| break; | ||
| case 'x32': | ||
| case 'ia32': |
There was a problem hiding this comment.
32bit installs were not working
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
ghost
locked as resolved and limited conversation to collaborators
This PR sets up helpers and folder structure for integration testing. The example test, tests document symbols which lands in hashicorp/terraform-ls#265.