Repository navigation
test: add xdr benchmarks, fuzzing engine, connection telemetry, event monitor - #923
Merged
Merged
Conversation
|
@Ogstevyn is attempting to deploy a commit to the vidatg's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@Ogstevyn Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
ide/src/test/benchmarks/xdr.bench.ts) covering XDR decode throughput,transformLedgerEntry,filterByKeyType,searchEntries, and state-diff operations across 100-and 1000-entry payloads (closes [Testing] Benchmarks for XDR Parsing Logic #842)ide/src/lib/test/FuzzingEngine.ts— aSorobanValueGeneratorthat produces randomised values (with targeted edge cases) for every Soroban primitive and compound type, plus aFuzzingEngineorchestrator that runs N iterations against a pluggable simulate function and reports panics and errors (closes [Testing] Fuzzing Engine for Contract Invocations #845)frontend/src/components/sharing/ConnectionTelemetry.tsx, a self-contained React component that manages a WebSocket connection, measures round-trip latency via ping/pong, tracks peer count, and renders a micro-animated telemetry bar with a degraded/disconnected warning overlay (closes [Frontend] Live Sharing Connection Telemetry Status #888)extension/src/services/EventMonitor.ts, a VS Code service that polls the Soroban RPCgetEventsendpoint on a configurable interval, writes formatted event logs (type, ledger, contract ID, topic, value preview) to a dedicated "Stellar Kit — Contract Events" output channel, and supports live filter updates by contract ID or event type (closes [Extension] VS Code View for Contract Events #874)Test plan
cd ide && npx vitest bench --runand confirm all benchmark groups pass with numeric outputFuzzingEnginewith a mock simulate function and callrun(), verify the returnedFuzzReportcontainspanicsanderrorsarrays<ConnectionTelemetry />in the frontend dev server — confirm the telemetry bar mounts, the pulsing indicator is visible, and the warning overlay appears whenwsUrlis omittednew EventMonitor(rpcUrl).start()and confirm the "Stellar Kit — Contract Events" output channel opens and begins logging