tc39 / tc39/test262

Potentially import more JSON tests

Open
#783 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2.8k
Forks
564
Avg merge
3d 7h
Merged PRs (30d)
10

Description

@nst has written a a nice JSON testsuite; this targets RFC 7159's definition of JSON rather than ECMA-404's, and obviously many tests don't apply given the source for JSON.parse is a string primitive rather than a bunch of bytes. We should, nevertheless, check that we have coverage for all of their tests that apply.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked JSONTestSuite and comparing its applicable cases with the existing JSON.parse coverage in test262. Determine which byte-oriented cases do not apply to string primitives; done when every applicable JSONTestSuite case is covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.