tc39/test262

Missing coverage: BigInt.prototype.toString (partial)

Open

#1,275 opened on Oct 13, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (2,073 stars) (469 forks)batch import
coveragehelp wanted

Description

Missing coverage:

  1. this value capturing objects with an [[BigIntData]] internal. (e.g.: BigInt.prototype.toString.call(Object(1n))).
  2. ToInteger coercions and abrupt completions from radix.
  3. Observable variants for the same this value using different radix, as long as the implementation defined spec permits.

Contributor guide

Tech stack
javascript
Domain
testing
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic BigInt understandingtest262 test conventions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The issue requests adding test coverage for BigInt.prototype.toString. The three missing cases are listed. Contributors should look at existing test262 tests for BigInt, particularly those in test/built ins/BigInt/prototype/toString/ directory, and follow the test format. The linked issue #1275 has no additional comments, so no maintainer clarification is needed. The tests should cover the cases exactly as described.