Update Regtest setup / define Regtest #268

New issue

Open

opened 2019-03-19 16:06:45 +01:00 by binaryflesh · 2 comments

binaryflesh commented

2019-03-19 16:06:45 +01:00

(Migrated from github.com)

As a new user coming from the infosec side of things, 'Regtest' is usually thought as dynamic brute force analysis not the actual definition of regression testing. While writing an API binding for lbrycrd I was under impression using testnet was what I needed to use for unit tests to see if my code would work, not break. There is currently no highlight to point newbie devs to lbrycrd's useful feature and it would help others like myself

Tom edit:
This should also include an update of https://lbry.tech/resources/regtest-setup to include latest install instructions / orchestrate.

As a new user coming from the infosec side of things, 'Regtest' is usually thought as [dynamic brute force analysis](https://en.wikipedia.org/wiki/Fuzzing) not the actual definition of [regression testing](https://en.wikipedia.org/wiki/Regression_testing). While writing an API binding for lbrycrd I was under impression using testnet was what I needed to use for unit tests to see if my code would work, not break. There is currently no highlight to point newbie devs to lbrycrd's useful feature and it would help others like myself Tom edit: This should also include an update of https://lbry.tech/resources/regtest-setup to include latest install instructions / orchestrate.

tzarebczan commented

2019-03-19 18:03:27 +01:00

(Migrated from github.com)

hey @binaryflesh, thanks for opening the issue. I'll edit this to also include updating regtest instructions(may be out of date per my comment on the other issue).

rhysmeister commented

2021-09-06 19:46:10 +02:00

(Migrated from github.com)

regtest setup instructions need an update...

https://lbry.tech/resources/regtest-setup

Several broken links to deleted repositories meaning getting a working env isn't possible.

regtest setup instructions need an update... https://lbry.tech/resources/regtest-setup Several broken links to deleted repositories meaning getting a working env isn't possible.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry.tech#268

No description provided.