test(amazonq): generateZipTestGen is unreliable #6290
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Flaky test
generateZipTestGen
sometimes fails withIssue: #6160
Solution
Based on the error, the test is trying to readdir on a mock dirpath even though the entire
zipProject
method should be stubbed. This can be confirmed by commenting out the following line:aws-toolkit-vscode/packages/amazonq/test/unit/codewhisperer/util/zipUtil.test.ts
Line 135 in aa332da
which will give the same error
So instead of stubbing which seems to be unreliable, we can let the test actually create the zip file.
feature/x
branches will not be squash-merged at release time.