oxidecomputer / oxidecomputer/typify

speed up tests by building fixtures; don't use `trybuild`

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

Nobody has claimed this yet.

Dominant language
Rust
Stars
898
Forks
114
Avg merge
4h 18m
Merged PRs (30d)
14

Description

We generate fixtures based on a bunch of input schemas and then we run those through trybuild... which takes a while. There really isn't much value in running each one separately. We could either do a single trybuild invocation for a file that includes all of them or we could have a distinct crate that sources all the generated rust fixtures.

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.

Research direction

Start by locating the generated fixture workflow and the trybuild invocations described in the issue. Compare consolidating the fixtures into one trybuild input with using a separate crate, then verify that all generated schemas remain covered and the test suite completes faster.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
performance, testing
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.