-
Notifications
You must be signed in to change notification settings - Fork 61
Issues: aws-amplify/amplify-backend
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
document e2e test process
repo-infrastructure
Engineering label for issues related to repo infrastructure
tech-debt
Refactors, unsavory workarounds or other technical decisions that should be revisited later
testing
Engineering label for issues related to tests or test tooling
#1351
opened Apr 19, 2024 by
sobolk
Invest in parameterization strategy for amplify version in e2e tests
feature-request
New feature or request
repo-infrastructure
Engineering label for issues related to repo infrastructure
testing
Engineering label for issues related to tests or test tooling
#1349
opened Apr 19, 2024 by
edwardfoyle
Implement check for changeset completeness
feature-request
New feature or request
repo-infrastructure
Engineering label for issues related to repo infrastructure
testing
Engineering label for issues related to tests or test tooling
#1335
opened Apr 18, 2024 by
sobolk
Lint rule for Engineering label for issues related to repo infrastructure
tech-debt
Refactors, unsavory workarounds or other technical decisions that should be revisited later
\n
repo-infrastructure
#1294
opened Apr 12, 2024 by
edwardfoyle
Lint rule for AmplifyUserError and AmplifyFault
repo-infrastructure
Engineering label for issues related to repo infrastructure
tech-debt
Refactors, unsavory workarounds or other technical decisions that should be revisited later
#1293
opened Apr 12, 2024 by
edwardfoyle
investigate why windows create_amplify e2e test takes so long
repo-infrastructure
Engineering label for issues related to repo infrastructure
tech-debt
Refactors, unsavory workarounds or other technical decisions that should be revisited later
testing
Engineering label for issues related to tests or test tooling
#1198
opened Mar 22, 2024 by
edwardfoyle
consider test-splitting strategy for expensive e2e tests
repo-infrastructure
Engineering label for issues related to repo infrastructure
tech-debt
Refactors, unsavory workarounds or other technical decisions that should be revisited later
testing
Engineering label for issues related to tests or test tooling
#1190
opened Mar 22, 2024 by
edwardfoyle
[CICD] e2e tests fail with "Error: Unable to deserialize cloned data due to invalid or unsupported version."
flaky
Engineering label for flaky tests
repo-infrastructure
Engineering label for issues related to repo infrastructure
tech-debt
Refactors, unsavory workarounds or other technical decisions that should be revisited later
testing
Engineering label for issues related to tests or test tooling
#1145
opened Mar 13, 2024 by
edwardfoyle
Revisit dependency check - how do we enforce versions of packages in amplify-backend repo
repo-infrastructure
Engineering label for issues related to repo infrastructure
tech-debt
Refactors, unsavory workarounds or other technical decisions that should be revisited later
#897
opened Jan 9, 2024 by
sobolk
API tests further improvements.
repo-infrastructure
Engineering label for issues related to repo infrastructure
tech-debt
Refactors, unsavory workarounds or other technical decisions that should be revisited later
testing
Engineering label for issues related to tests or test tooling
#871
opened Jan 5, 2024 by
sobolk
linter should force to use Engineering label for issues related to repo infrastructure
tech-debt
Refactors, unsavory workarounds or other technical decisions that should be revisited later
fs/promises
to avoid using fs
APIs
repo-infrastructure
#847
opened Dec 27, 2023 by
0618
enable eslint "no-then"
repo-infrastructure
Engineering label for issues related to repo infrastructure
tech-debt
Refactors, unsavory workarounds or other technical decisions that should be revisited later
#452
opened Oct 19, 2023 by
0618
ProTip!
Mix and match filters to narrow down what you’re looking for.