feat(Example): add checkmark script for tests#4087
Draft
sgaczol wants to merge 1 commit into
Draft
Conversation
This file contains hidden or 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
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.
Description
This PR adds a new utility script that automatically collects information about test scenarios and generates readable Markdown tables based on their metadata.
The script processes the collected data and outputs it into two separate sections: Smoke Tests and Non-Smoke Tests. Currently, the generated tables include the following columns:
Mark(rendered as an empty checkbox [ ]),Test Name,E2E CoverageandKey. The entries in both tables are sorted first by E2E coverage priority, and then alphabetically by their file path. This ensures that tests related to the same features or areas are grouped logically together in the list.If you want to add a new property or column to the table in the future, you simply need to add a new object to the
TABLE_COLUMNSarray inside the script.By default, the script searches the standard test directory, but you can override this behavior by passing a custom path using the
--test-path <path>flag.Changes
Before & after - visual documentation
Test plan
Checklist