Document nextest usage

Open
#161 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Half a day
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation, testing

Research direction

Start by locating the Servo Book section covering tests or development workflows, then review the official nextest documentation linked in the issue. Document the move to nextest, useful options, and the --stress-count infinite example with a test filter; done means contributors can find and follow the guidance.

Written by the indexing model from the issue text.

Description

As pointed out on Zulip, we recently moved to nextest and are lacking documentation for it (e.g. linking to the official nextest docs, outlining some of the most useful options, etc.).

One trick @jdm mentioned on Zulip that might be worth documenting:

Also, I helpful thing I just figured out: use --stress-count infinite with a test filter (like test_show_and_hide_ime) to run a test repeatedly and increase confidence that a particular change makes intermittent timeouts go away.

Dominant language
Python
Stars
42
Forks
71
Avg merge
1d 5h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

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.

More from servo/book

All issues in servo/book

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.