lbryio/lbrycrd

An automated test for checking that a PR can sync

Open

#164 opened on Jun 25, 2018

View on GitHubContributor guide
 (4 comments) (0 reactions) (0 assignees)C++ (173 forks)auto 404
area: devopsgood first issuehacktoberfesthelp wantedtype: new feature

Repository metrics

Stars
 (2,528 stars)
PR merge metrics
 (PR metrics pending)

Description

As part of the automated travis build (or maybe it could be a separate thing from travis) , we should try to run and sync the built lbrycrd on testnet to see if it can a) sync from scratch and b) start up when its already synced and can succesfuly recieve a couple of blocks.

Not sure if this is possible just using travis (might take too long? use too much disk space?). We might have to set up some servers for this.

Contributor guide

Research direction
Investigate the existing Travis CI configuration and test infrastructure. Create a test script that builds lbrycrd and runs it on testnet, verifying it can sync from scratch and restart. Consider using prebuilt docker images or setting up a dedicated test server if Travis resources are insufficient.
Tech stack
cpp
Domain
testing
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.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitC++Travis CI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40