Clarify test plan #4225
Open
Clarify test plan #4225
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
Contributor
There was a problem hiding this comment.
Pull request overview
This PR enhances the test plan documentation by adding clarifying details that help testers trigger expected behavior when testing the CodeQL extension.
- Clarifies that the
test-model-packdirectory should be created in the CodeQL Workspace with specific guidance for users with agithub/codeqlcheckout - Adds explicit steps for selecting the database and adding its source to the workspace before opening the Model Editor
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
cklin
force-pushed
the
cklin/update-testing-plan
branch
from
0fa3173 to
ce57329
Compare
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 clarifies the test plan by adding details that are important for triggering the expected behavior.
Remember to update the changelog if there have been user-facing changes!