docs: update CLAUDE.md with new test files and architecture notes#43
Merged
docs: update CLAUDE.md with new test files and architecture notes#43
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
Updates the project documentation (
CLAUDE.md) to reflect the current state of the codebase, including recently added test files and improved development workflow guidance.Changes Made
PlaywrightClientConcurrencyTest,PlaywrightClientDataTest,PlaywrightClientExceptionTest,PlaywrightClientHc5MigrationTest,PlaywrightClientInternalMethodTest,PlaywrightClientPropertyTestCrawlerWebProxyTestto test utilities sectionmvn license:formatto development commands and code standards (was missing from both)Testing
Documentation-only change, no functional code modified.
Additional Notes
These updates ensure the documentation accurately reflects the test suite structure and required pre-commit workflow steps.