Repository navigation
chore(deps): adopt @forkzero/s3-website-test-kit 0.4.0 - #202
Merged
Merged
Conversation
Kit 0.4.0 drops the in-package Artillery processor (which accumulated per-worker partial metrics, kit #9) in favor of Artillery's own aggregated `-o` reports; s3-website-perf-compare now diffs two of those. - Bump devDependency ^0.2.1 -> ^0.4.0. - artillery-local: capture Artillery's own report (-o artillery-report- <example>.json) and drop the now-dead `env TEST_ENVIRONMENT=local`. - Add opt-in `perf-compare` target: A/B load two framework examples (BASELINE vs CANDIDATE) and diff via `s3-website-perf-compare compare`. Not in all/functional-tests (two load runs ~2 GB S3 egress). - Document perf-compare in docs/performance.md. Conformance config is unchanged in 0.4.0; `make conformance-local` (the CI gate) verified green against the live bucket with the new kit. Co-Authored-By: Claude Opus 4.8 (1M context) <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
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.
Closes #201.
Kit 0.4.0 removes the in-package Artillery processor (it accumulated per-worker partial metrics — kit #9, the reason
artillery-localproduced throwaway partialload-test-results-*.json) and leans on Artillery's native-oreports;s3-website-perf-comparenow diffs two of those.Changes
@forkzero/s3-website-test-kit^0.2.1→^0.4.0.artillery-local: writes Artillery's own report (-o artillery-report-<example>.json) and drops the now-deadenv TEST_ENVIRONMENT=local.perf-comparetarget: load two framework examples (BASELINEvsCANDIDATE) and diff vias3-website-perf-compare compare --baseline … --candidate …. Deliberately not inall/functional-tests— two load runs are ~2 GB of S3 egress.perf-compareindocs/performance.md.Verification
make conformance-local(the CI gate) run green against the live bucket with 0.4.0 — both scenarios (core + s3proxy XML error contract),vusers.failed: 0.make -n artillery-local/make -n perf-compareexpand correctly;s3-website-perf-compare --helpconfirms thecompare --baseline/--candidateCLI.npm run lintclean.🤖 Generated with Claude Code