tests: Categorize Tests into CI and Scheduled Groups #3391
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
…ng and deleting items, searching flows, and searching components on the main page to ensure proper functionality and user experience.
…atch the correct directory structure for scheduled-end-to-end tests.
dosubot
bot
added
the
size:S
Pull Request Validation ReportThis comment is automatically generated by Conventional PR Whitelist Report
Result Pull request does not satisfy any enabled whitelist criteria. Pull request will be validated. Validation Report
Result Pull request satisfies all enabled pull request rules. Last Modified at 16 Aug 24 17:42 UTC |
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Cristhianzl
changed the title
…ry to run end-to-end tests in the frontend folder 📝 (typescript_test.yml): improve comments for better readability and understanding of the workflow logic
dosubot
bot
added
size:M
…n a specific folder 📝 (ci.yml): Update job dependencies to improve readability and maintainability of the workflow configuration
ogabrielluiz
approved these changes
Aug 16, 2024
…hardTotal to reduce redundancy and improve readability
…ng and deleting items, searching flows, and searching components on the main page to ensure proper functionality and user experience.
…atch the correct directory structure for scheduled-end-to-end tests.
…ry to run end-to-end tests in the frontend folder 📝 (typescript_test.yml): improve comments for better readability and understanding of the workflow logic
…n a specific folder 📝 (ci.yml): Update job dependencies to improve readability and maintainability of the workflow configuration
…hardTotal to reduce redundancy and improve readability
ogabrielluiz
force-pushed
the
cz/test-category
branch
from
0940d14 to
8696ff7
Compare
…rectly locate the test file in the assets folder
…t to match new file location in the project structure
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.
This PR introduces a categorization of tests to optimize our Continuous Integration (CI) pipeline and nightly testing processes. By dividing the tests into two distinct groups—CI and Scheduled—we aim to improve testing efficiency and ensure critical functionalities are validated in a timely manner.
Categorization of Tests:
Includes basic example tests, tests ensuring critical functionalities, and any essential functionality tests that need immediate feedback.
Includes large flow tests and any additional tests that cover a broad range of functionalities and edge cases, which are less time-sensitive but important for comprehensive coverage.