I’m using some HTTP basic authentication in Chirk HR as a simple way of preventing unauthorized access. It’s simple, fast, and easy to change to a more robust authentication later on. Ideal Authentication Test As part of my testing habits, I try to really exercise important methods. Authentication is definitely one of them. Authentication is …
Tag: authentication
Redmine API: Adding Key Authentication for Issues#create
Now that I’ve tested #index and #show for #6447, it’s time to see if #create is working. Updating the Issues#create test The first thing I need to do is to update the tests for #create to see if I can reproduce any authentication bugs. With a few tweaks to my shoulda macros, I added tests …
Redmine API: Changing API Tests for Issues #index and #show
Now that I’ve built up a few shoulda helpers for testing the different authentication APIs in Redmine, I can now start testing the actual bug reported. Creating a standard test macro for all APIs The first thing I did was to create a standard test macro for all of the different API authentication types. Otherwise …
Redmine API: Testing for HTTP Basic auth with an API Token
This should be the final refactoring I need before I can fix the Issues API doesn’t allow full key auth for all actions bug. Here I refactored the test that is authenticating against Redmine using an API token but through HTTP Basic. Basically it’s a cross between the Token Auth and the Username and Password …
Redmine API: Testing for HTTP Basic auth refactoring
After thinking over the test refactoring I did yesterday, I thought it would be useful to do a few more refactorings to the Redmine API test suite. Today I refactored how HTTP Basic authentication is used with a username and password by creating a new shoulda macro. Before 1 2 3 4 5 6 7 …