first unit test and integration test

A quick test that the homepage works and that the login succeeds in three cases (failure, unconfirmed, and success).
On Thu, Jun 26, 2014 at 07:36:47AM -0700, Brian Grayless wrote:
> Yeah. Just because the login info is wrong doesn't mean the HTTP request failed.

Eh, in general, it might arguably be 403 Forbidden or 401 Unauthorized (though 401 will then ask for http authentication) but those are more API oriented than end-user oriented.

For example, I'm pretty sure the Twitter API uses 403 in this case, but the website itself uses 200.


But it is moot in our case anyway IMO because I don't want to customize Devise to this level; if we were going to change something on this level it kinda defeats the purpose of using the gem in the first place.


That said, I don't like looking for a specific error message either. A css class would be much better... just not sure we can easily add it whereas the error message was trivial to check.