Skip to content

✨ Quality: Browser integration tests do not cover ajv2020 and ajvJTD UMD bundles#2600

Open
Hikkywannafly wants to merge 1 commit into
ajv-validator:masterfrom
Hikkywannafly:contribai/improve/quality/browser-integration-tests-do-not-cover-a
Open

✨ Quality: Browser integration tests do not cover ajv2020 and ajvJTD UMD bundles#2600
Hikkywannafly wants to merge 1 commit into
ajv-validator:masterfrom
Hikkywannafly:contribai/improve/quality/browser-integration-tests-do-not-cover-a

Conversation

@Hikkywannafly
Copy link
Copy Markdown

✨ Code Quality

Problem

The browser test runner only loads bundle/ajv7.min.js and bundle/ajv2019.min.js, while the build config also produces ajv2020 and ajvJTD bundles. This leaves two published browser artifacts unverified in CI, so bundling/runtime regressions in those entrypoints can ship undetected.

Severity: high
File: karma.conf.js

Solution

Extend Karma inputs and add browser specs for each missing bundle. For example: 1) In karma.conf.js add:

  • "bundle/ajv2020.min.js"
  • "bundle/ajvJTD.min.js"
  1. Add .browser/ajv2020.spec.js:
    • instantiate new ajv2020.default() (or exposed global)
    • compile a draft-2020-12 schema and assert valid/invalid cases
  2. Add .browser/jtd.spec.js:
    • instantiate JTD bundle
    • compile parser/serializer for a small schema and assert round-trip behavior.

Changes

  • karma.conf.js (modified)

What issue does this pull request resolve?

What changes did you make?

Is there anything that requires more attention while reviewing?


🤖 About this PR

This pull request was generated by ContribAI, an AI agent
that helps improve open source projects. The change was:

  1. Discovered by automated code analysis
  2. Generated by AI with context-aware code generation
  3. Self-reviewed by AI quality checks

If you have questions or feedback about this PR, please comment below.
We appreciate your time reviewing this contribution!

Closes #2599

…d` umd bundles

The browser test runner only loads `bundle/ajv7.min.js` and `bundle/ajv2019.min.js`, while the build config also produces `ajv2020` and `ajvJTD` bundles. This leaves two published browser artifacts unverified in CI, so bundling/runtime regressions in those entrypoints can ship undetected.


Affected files: karma.conf.js

Signed-off-by: - nyankoiscat - <76279331+Hikkywannafly@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

fix: browser integration tests do not cover ajv2020 and ajvjtd umd bundles

1 participant