Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Regtest setup / define Regtest #268

Open
binaryflesh opened this issue Mar 19, 2019 · 2 comments
Open

Update Regtest setup / define Regtest #268

binaryflesh opened this issue Mar 19, 2019 · 2 comments

Comments

@binaryflesh
Copy link
Contributor

binaryflesh commented Mar 19, 2019

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.

@tzarebczan
Copy link
Contributor

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).

@tzarebczan tzarebczan changed the title Add definition of Regtest to glossary and Regtest setup Add definition of Regtest to glossary and update Regtest setup Mar 19, 2019
@tzarebczan tzarebczan changed the title Add definition of Regtest to glossary and update Regtest setup U pdate Regtest setup / define Regtest Mar 19, 2019
@tzarebczan tzarebczan changed the title U pdate Regtest setup / define Regtest Update Regtest setup / define Regtest Mar 19, 2019
@rhysmeister
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants