chore(tests): Build in source sync temp folder #6166
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…o build_in_source_sync_temp_folder
mildaniel
approved these changes
Nov 7, 2023
| @@ -1,4 +1,4 @@ | |||
| import * as faker from '@faker-js/faker'; | |||
| const faker = require("@faker-js/faker"); | |||
There was a problem hiding this comment.
Curious why we needed to change the import syntax here?
There was a problem hiding this comment.
The build in source test that reuses this project is complaining about using the module import keywords. Changed it back here and ran the entire suite of integration tests on my local machine to make sure that nothing broke. We can test again using the dedicated canaries too.
hawflau
approved these changes
Nov 7, 2023
github-merge-queue bot
pushed a commit
that referenced
this pull request
Dec 5, 2023
* feat: Added event tracking for feature (#5872) * Added event tracking for feature * Correctly pass event value and fix typing * feat: Resolve symlinks at root level and mount to container (#5870) * Resolve symlinks at root level and mount to container * Continue early instead of nesting in if statement * make format * Added integration test * make format * Use node project to test local deps and building in source * Removed old test data * Update test class name to reference testing symlinks * Use correct skip decorator from unittest * Changed mount mode to read only * Removed the removed mount parameter in tests * Remove kwarg in method call * feat: Build in source click option (#5951) * Added skeleton for build in source click option * Fix tests and renamed option * Added description and updated click option to include build * Disable build tests again until esbuild resolution fix * Revert template change * Make hook name option mutually exclusive with build in source * Fix integration test message assert * chore(tests): Enable build in souce build command tests (#6099) * chore(tests): Node build in source test (#6132) * Added nodejs tests * make format * Enable retries * Run build test inside of a scratch directory * make format * Updated Makefile test to properly use scratch directory and moved source copy to setup * Changed copytree call to in house version * Removed redundant parent method calling * make format * chore: Bump Nodejs version in AppVeyor job configuration (#6210) * Bump npm version to 10.2.3 for linux testing * Upgrade node to 18.18.2 * chore(tests): Build in source sync temp folder (#6166) * Enable and use new test data folder paths * Added nodejs tests * feat: Resolve root level symlinked folders in Layers (#6236) * Resolve Layer symlinks before mounting container * Use .get instead of if else * Added integration tests * Unprivate static method and make format * Create paths using pathlib * Remove debug flag * Revert "Resolve Layer symlinks before mounting container" This reverts commit e557067. * Resolve links when creating tarfile for Docker build call * make format * Removed debug line * Updated arugment with optional typing * feat: Add additional default excludes and exclude option for sync (#6299) * Add additional default excludes and exclude option * Updated test and option definition * Updated option and added tests * Update resource match to consider nested stacks * Handle parameters saved in samconfig * fix: Fix sync tests not cleaning up correctly and Linux watch behaviour (#6372) * Use develop version of Lambda Builders * Run nodejs local dep command in scratch directory and clean up aws-sam folder * Exclude the folder of the modified file from trigger sync flows on Linux * Revert "Use develop version of Lambda Builders" This reverts commit fde143e. * Add test validing ignoring Linux modified folder events * Fix test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which issue(s) does this change fix?
None
Why is this change necessary?
Fixes the sync test so that they can be run again with the recent changes that were made to the sync tests.
How does it address the issue?
Fixes the variable references to the test data folder to the newer one and adds the file update logic to test code sync. Additionally, adds Node.js tests to test building regular Node.js projects in source.
What side effects does this change have?
None.
Mandatory Checklist
PRs will only be reviewed after checklist is complete
make prpassesmake update-reproducible-reqsif dependencies were changedBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.