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:29:08AM -0700, Brian Grayless wrote:
> I think you can also address the specific fields by class or ID names as well, in case the label changes. It wouldn't hurt to talk about this a bit just so we are all on the same page of how this works and what our options are.

Or the name, fill_in('user[email]') works too. But my thought is if we want it to be like the user perspective, we should use the label. Again though this makes some pain when the label is translated, but it does test that the label actually applies to the correct field.

If the test breaks when the label changes... in my mind, that's a good thing. The test is doing its job. If we remember to run the test after each tweak (which Travis will do on a PR anyway) then it'll be obvious that one of these little things changed and we can change the test or fix the view after a minute finding the root cause.