-
-
Notifications
You must be signed in to change notification settings - Fork 0
Update tests workflow coverage handling #68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
gocanto
merged 18 commits into
main
from
codex/update-go-version-and-improve-coverage-handling
Aug 1, 2025
Merged
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
f981e5f
Pin Go 1.24.5 and merge coverage
gocanto bcbe80f
test: expand isValidTable edge cases
gocanto 61f346e
use artifact action v4
gocanto 9321c81
fix coverage merging
gocanto 01972f9
Fix coverage merge step
gocanto 36c4437
test: run workflow across go versions and print merged coverage
gocanto 59ecb42
Pin Go versions to 1.24.5 and 1.23.4
gocanto 11bd9d8
Remove coverage artifact upload
gocanto 3a96675
Test on Go 1.24.5 and 1.24.4
gocanto 6ed3971
add version
gocanto c49b7d6
cache
gocanto ef13b0b
go.sum
gocanto 00a0b60
wip
gocanto 848abf7
wip
gocanto 3dd2c93
wip
gocanto 59ac84f
wip
gocanto 459e8ef
wip
gocanto 16ef98c
wip
gocanto File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Test logic misalignment with actual implementation.
The test assumes
isValidTableperforms string validation (checking for special characters, case sensitivity, length limits, etc.), but based on the implementation indatabase/model.go, the function only checks if the input exists in theschemaTablesslice usingslices.Contains.This test will pass if none of these edge case strings are present in
schemaTables, but it's not actually testing string validation logic - it's testing slice membership. The test name and structure suggest it's meant to validate input format rules, which don't exist in the current implementation.Consider either:
isValidTableif that's the intended behaviorLet me verify what's actually in the
schemaTablesslice to understand the expected behavior:🏁 Script executed:
Length of output: 40
🏁 Script executed:
Length of output: 1451
Align test behavior with
isValidTableor extendisValidTablefunctionalityThe test
TestIsValidTableEdgeCasesindatabase/model_internal_test.go(lines 17–34) currently only verifies that arbitrary strings aren’t present inschemaTables, but does not exercise any format or character‐set rules. Meanwhile,isValidTableindatabase/model.go(lines 22–24) simply returnsslices.Contains(schemaTables, seed)without any additional validation. To resolve this misalignment, choose one of the following:TestIsValidTableNonexistentTables).GetSchemaTables()to assert that known valid names return true.isValidTableto enforce format rules:🤖 Prompt for AI Agents