feat: external opcode metadata for archive sources#180
Merged
Conversation
Add opcodes and opcodes_file fields to the archive source config, allowing opcode count data to be provided via an external JSON file when not using EEST fixtures. The opcode data is included in the suite summary.json and displayed in the UI opcode heatmap. Also adds the archive source section to docs/configuration.md and config.example.yaml which were previously missing.
Strip .txt suffix as fallback when matching opcode JSON keys to discovered test names. Also apply the test filter when counting unmatched opcode entries to avoid misleading warnings.
When a suite directory already exists, CreateSuiteOutput re-reads the old summary.json and preserves its test entries. This discarded any newly loaded opcode data. Now we merge opcode counts from the prepared source into the existing test entries before writing.
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.
Summary
opcodesandopcodes_filefields to the archive source config, allowing opcode count data to be provided via an external JSON file when not using EEST fixturesopcode_countat the top level of each test insummary.json, and the UI opcode heatmap/test detail views now read from this unified field (with fallback toeest.info.opcode_countfor backward compatibility)docs/configuration.mdandconfig.example.yamlwhich were previously missingConfig example
Test plan
go build ./pkg/executor/... ./pkg/config/...compilesgo test ./pkg/executor/... ./pkg/config/...passesgolangci-lint runpasses on changed packagesnpx tsc --noEmitsummary.jsoncontainsopcode_countper test