When testing this repo, do I need to create a new repo every time?

[joncodo]

Overview

I am looking for a way to iterate on programming ideas faster.

Steps I take now to code changes in this repo

Here is what I do now:

• I make a change in the cloned repo locally, create-frigg-app on my own branch.
• I run a command like:

➜  prevent-duplicate-users-test1 git:(master) ✗ ../create-frigg-app/packages/create-frigg-app/index.js prevent-duplicate-users-test2 --template file:../create-frigg-app/packages/cfa-template/

• This makes a new folder with a new create-frigg-app that I think is required to ensure that the changes are translated over to the consuming programmers.
• Then I check the files to see if things are the way I expect

How I test those changes

Since the test suite fails now, I just test things manually.

This means:

• npm start should compile
• I can log into the front end
• I can see the integrations page with salesforce listed

For now, this is where we are at with testing. Referenced here: #55

Question

@seanspeaks how are you doing this flow locally? How can we improve this flow?