why test built-in activerecord things?
3 views
Skip to first unread message
Kevin
Jun 26, 2010, 1:24:35 PM6/26/10
to Remarkable
i've always wondered why anyone would bother writing tests to check
built-in things like validates_presence_of?
Also, is the remarkable::rails stuff working now? The readme refers
to an earlier alpha version not working...
built-in things like validates_presence_of?
Also, is the remarkable::rails stuff working now? The readme refers
to an earlier alpha version not working...
Louis T.
Jun 26, 2010, 2:21:34 PM6/26/10
to Remarkable
When developing an application using TDD or BDD you would write the
tests/specs first. So the matchers that remarkable provides would
allow you to describe the expected behavior of your application and
when all the tests/specs pass your application should work correctly.
However, testing and how in-depth you test is optional, if you work by
yourself or your company does not require test coverage and you find
it cumbersome then don't. But, without test coverage if by chance that
one line disappears your application could begin to act in unexpected
ways and hunting down that problem would be a waste of time. Testing
is insurance against regression that happens from time to time while
an application is being developed and maintained.
Louis T.
@negonicrac
tests/specs first. So the matchers that remarkable provides would
allow you to describe the expected behavior of your application and
when all the tests/specs pass your application should work correctly.
However, testing and how in-depth you test is optional, if you work by
yourself or your company does not require test coverage and you find
it cumbersome then don't. But, without test coverage if by chance that
one line disappears your application could begin to act in unexpected
ways and hunting down that problem would be a waste of time. Testing
is insurance against regression that happens from time to time while
an application is being developed and maintained.
Louis T.
@negonicrac
Louis T.
Jun 26, 2010, 2:27:57 PM6/26/10
to Remarkable
Also, the remarkable::rails is not working. I did not use it in the
pass as it was seemed a bit overkill, but I like the plans that
hosh(Ho-Sheng Hsiao) has laid out in the issue for the future
development of the remarkable::rails stuff.
http://github.com/remarkable/remarkable/issues#issue/4
pass as it was seemed a bit overkill, but I like the plans that
hosh(Ho-Sheng Hsiao) has laid out in the issue for the future
development of the remarkable::rails stuff.
http://github.com/remarkable/remarkable/issues#issue/4
Reply all
Reply to author
Forward
0 new messages