test: Add unit test for projects/app/src/components/Markdown/utils.ts #5711
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.
Trigger Info
Summary
This pull request introduces a new test suite for the
Markdown/utils
module, specifically targeting theCodeClassNameEnum
andmdTextFormat
functions. The tests are implemented using thevitest
framework and cover a variety of scenarios to ensure the correctness and robustness of the utility functions.Key Changes:
CodeClassNameEnum Tests:
Verifies the presence of expected enum values such as
guide
,questionguide
,mermaid
, etc.Confirms the absence of removed enum values like
table
andindicator
.mdTextFormat Tests:
Ensures correct formatting of LaTeX delimiters, converting
\[\]
to$$
and\(\)
to$
.Checks that code blocks and inline code are not modified.
Validates the conversion of
[quote:id]
and[id]
to[id](CITE)
.Tests the addition of spaces between URLs and citations, as well as after Chinese punctuation following a URL.
Handles multiple replacements within a single string and ensures unrelated text remains unchanged.
Confirms that URLs with non-citation brackets are not altered.
Includes edge cases such as empty strings, consecutive citations, and complex mixed input.
These tests aim to enhance the reliability of the
Markdown/utils
module by covering a wide range of input scenarios and edge cases.Coverage
The change in coverage value, such as:
0% -> 50%
, indicates that the coverage was 0% before writing the tests and 50% after writing them.https://web.dev/articles/ta-code-coverage
Test Statuses
Tip
You can
@gru-agent
and leave your feedback. TestGru will make adjustments based on your inputTip
You can
@gru-agent rebase
to rebase the PR.Tip
You can
@gru-agent redo
to reset or rebase before redoing the PR.Tip
To modify the test code yourself, click here Edit Test Code