bi-13 step 02 — Mine TestExpectations

Goal

Turn a 9,418-line file into a candidate list for your first contribution — and into product-risk intelligence.

Tasks

  1. Read the header. Note the results vocabulary and the policy forbidding a bare [ Skip ]. Write down the three reasons a failing test is kept running.
  2. Grep for areas you have studied (parsing, tables, CSS invalidation, layout). Find three currently-failing tests.
  3. For each: read the linked bug, read the relevant spec text, and write one paragraph on whether it looks tractable for a newcomer.
  4. Note the platform tags in use, including OS-version-specific ones. State what version-specific expectations imply about "it works in Chrome".
  5. Keep this list. It is your bi-14 candidate pool.

Done when

  • Three candidates with tractability judgements
  • The no-Skip policy stated in your own words, with its three justifications
  • One product-relevant risk identified, if any applies to your work