ChainSafe / ChainSafe/lodestar

Integrate and schedule CI for Assertoor testing

Open
#6,692 2 comments 0 reactions 0 assignees View on GitHub
meta-feature-request scope-testing
Dominant language
TypeScript
Stars
1.4k
Forks
483
Avg merge
1d 16h
Merged PRs (30d)
150

Description

### Problem description

Ensuring our commits don't break important functionality is always a problem. Having something that can do it for us automatically is useful for ensuring stability.

### Solution description

Integrate [Assertoor](https://ethpandaops.io/posts/assertoor-introduction/) into our CI and have it do daily runs to ensure we didn't break anything in `unstable`. With it running every 24 hours we will be able to determine where things would have broke.

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reading the linked Assertoor introduction and inspecting Lodestar's existing CI configuration. Determine how Assertoor should run against unstable on a 24-hour schedule, then verify that the scheduled run executes successfully and detects regressions.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.