Closed geeeeeeeeek closed 8 years ago
There is a connection error in the integration test against the real Badge server. Maybe you should look into that.
Also, the word integration
in your test/app.js
is misspelled. I'll just leave it to yourself. : )
Hi @geeeeeeeeek tests are running fine here; you need credentials that @acabunoc can provide.
The spelling error was corrected in #175.
@josmas I don't get it. Shouldn't credentials be stored in Travis's environment variables?
If you want to run tests locally, you'll need the credentials locally. There's info in the readme for local setup.
I guess you were referring to the automated tests triggered by the pull request (in travis), and yes, that needs to be looked after. I thought you were trying to run tests locally.
@josmas Sorry I didn't express myself. I was talking about the CI build. If the failure was with the CI itself, I think this pr can be merged.
Hey @geeeeeeeeek & @josmas!
Sorry for the delay, busy day :) yes we have the credentials in Travis, but it only works when the branch is in the MozillaScience/paperbadger repo. This is a known issue, I think @audy was looking at this awhile ago. Can't seem to find this in our issue tracker though, so thanks for flagging, @geeeeeeeeek!
Swagger seems like a good idea, especially as we get more mature
Filed the CI issue here: https://github.com/mozillascience/PaperBadger/issues/178
So, we also list all these API endpoints in home.jsx (I know, it's not the best solution)
I'd like to update both pages together, if possible. @geeeeeeeeek can you updates those endpoints there, too?
@acabunoc I'd love to.
@acabunoc Done. I'll look into other issues and see what I can do.
Thanks friend :)
R+
There are some typos in the README.
users
were typed intobadges
. I found them when writing a GSoC proposal for your project.@acabunocActually this kind of api doc is not convenient to maintain, I suggest using Swagger to drive the API documentation. I will further clarify that in my porposal.