trunk-rs/trunk

Regression tests

Open

#57 opened on Sep 23, 2020

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)Rust (315 forks)auto 404
Staleci/cdgood first issuetests

Repository metrics

Stars
 (4,347 stars)
PR merge metrics
 (PR metrics pending)

Description

items to test

  • pin down issues related to proc-macro-nested causing issues for wasm32 builds on Windows platform.
  • fix the current snapshot & integration tests in CI. May need to scrap them for something which will not break related to hashing of content.
  • CI cache is giving very strange errors as well, let's fix that up. Currently, cache code is commented.
  • ensure index.html file is served as a fallback.
  • test the proxy system with an echo server to ensure requests are proxied and echoed back.
  • test the trunk config show command output with some snapshot tests to ensure Trunk.toml and env vars are processed properly.
  • snapshot test --help output to ensure we don't hit a regression in CLI help output.

Contributor guide

Research direction
Focus on the failing snapshot and integration tests in CI. Start by inspecting the CI configuration and the test output logs to understand the failures. Then, fix the snapshot tests by updating expected values or adjusting hash handling. For proxy tests, set up an echo server and verify proxying.
Tech stack
rustwasm
Domain
cli
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustGitWASM
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60