FuelLabs/fuel-core

Beef up execution tests

Open

#1,911 opened on May 29, 2024

View on GitHub
 (3 comments) (0 reactions) (1 assignee)Rust (57,084 stars) (2,861 forks)batch import
good first issue

Description

Each of the tests should:

  1. Each produced block also is valdiated
  2. We produce the same block twice. First from intial block, the second from the first iteratiopn block
  3. All modification are done in InMemoryTransaction and we compare them after production and validation. The idea is that they are exactly the same

In addition, there are probably missing tests. Add any tests that seem to be missing.

Contributor guide

Tech stack
rust
Domain
testingbackend
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-3 hours
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
Rust programmingbasic blockchain concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue asks to improve execution tests by ensuring each produced block is validated, that the same block is produced twice (from initial block and from first iteration), and that all modifications in InMemoryTransaction are identical after production and validation. Likely the tests reside in the `fuel core` repository under a `tests/` directory or within the execution module. The assignee is working on this, so any new contributor should coordinate. Look at existing test files for execution to understand the structure and add similar tests. The comment thread may contain additional guidance.