Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Enable testing name registrations

See original GitHub issue

When we are working on / updating functionality / ui work for the onboarding, we tend to make a new account each time we have to go through the flow. This ends up being not a small number of new(fake) accounts.

I suggest we have a flag env that we pass when we’re testing, eg process.env.STAGE or something to that effect which would switch out the registrar url for another name, eg *.test-blockstack.id. @kantai we have a test registrar set up already, correct? if so what is that url?

cc @yknl

Issue Analytics

State:
Created 5 years ago
Comments:8 (2 by maintainers)

Top GitHub Comments

1reaction

hstovecommented, Mar 7, 2019

Matt has implemented a flag you can set to use the test registrar. It requires you to use the JavaScript console, but since this is really just for internal use, that seems fine to me

On Thu, Mar 7 2019 at 8:05 AM, < notifications@github.com > wrote:

@yknl ( https://github.com/yknl ) were you able to address this after all?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub ( https://github.com/blockstack/blockstack-browser/issues/1679#issuecomment-470585961 ) , or mute the thread ( https://github.com/notifications/unsubscribe-auth/ABDsQm9ncvY6Slngbe8kvLokNbU-tvFbks5vUTjcgaJpZM4W0XbO ).

0reactions

hstovecommented, Mar 8, 2019

Yes, I think so.