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

Tests to run in Postman (UA-514) #72

Merged
merged 5 commits into from
May 8, 2017
Merged

Tests to run in Postman (UA-514) #72

merged 5 commits into from
May 8, 2017

Conversation

kotodharma
Copy link
Contributor

I created project top-level dir "tests"... hope that was ok... Go still compiles the project, so I guess so :=)

@jonpage
Copy link
Contributor

jonpage commented May 5, 2017

I'm cool with the top-level dir. What are the instructions for running the test? These should probably go in the README.

@kotodharma
Copy link
Contributor Author

kotodharma commented May 6, 2017

Added testing instructions to the README, but now that I've done that, I realize that the URL of our production API is hardcoded in the test files. I guess this is not what we really want for others who might fork and adapt the code. I have a suspicion that Postman's CLI sidekick, newman, might make it easy to parameterize the URL, though I haven't looked into newman yet.

Btw, the "standalone" Postman app (i.e. not Chrome or other browser plugin) seems to be better on several points than the plugin version, so if you don't have that, I'd recommend it.

@kotodharma kotodharma requested a review from jonpage May 6, 2017 05:06
@kotodharma
Copy link
Contributor Author

test. please ignore

@kotodharma kotodharma merged commit 7f5ea91 into master May 8, 2017
@kotodharma kotodharma deleted the feature/UA-514 branch May 8, 2017 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants