FuelLabs/sway

Organize test suites in `swayfmt`

Open

#2494 opened on Aug 9, 2022

View on GitHub
 (7 comments) (0 reactions) (1 assignee)Rust (61,702 stars) (5,421 forks)batch import
ODHack13forcformattergood first issuemay be rewardedtesting

Description

  • parens
  • block
  • array #2593 @eureka-cpu
  • asm
  • return
  • conditionals
    • if/else #2597 & #2564 @eureka-cpu
    • match #2539 & #2530 @eureka-cpu
  • while
  • index
  • tuple field projection
  • ref & deref
  • bitwise operators
  • comparison operators
  • logical operators
  • reassignment
  • #2497

Edit: Extending this to re-organizing all tests in swayfmt

Contributor guide

Tech stack
rust
Domain
testingdeveloper experience
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.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rustswayfmt codebasetesting conventions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the current test structure in swayfmt (likely in tests/ directory). Identify which test suites are not yet organized and move them into appropriate subdirectories as indicated by the checklist. Check completed PRs (#2593, #2597, etc.) for patterns. Consult maintainers if any tests are already covered.