Re: [ruby-81] Re: Pros + cons of various testing frameworks...
| From: | user 3. |
| Sent on: | Monday, August 24, 2009, 10:16 AM |
Along those same lines I've heard in a presentation once to start testing from the log entries. You could even take the log entries generated by your smoke test which report parameters and results.
Wolf
Chad Woolley wrote:
On Sun, Aug 23, 2009 at 3:06 PM, Steve Midgley<[address removed]> wrote:
> Whatever framework you decide to use, one tip that might be helpful in
> building legacy tests, is to start with your "smoke tests." You could build
> a lot of: "Given this set of parameters, this GET request should return
> 200-Ok, and in the resulting HTML there should be an input tag with this
> value." This sets some a baseline harness around your system to define it's
> behavior in the most fundamental way (these parameters in, this html out).
>
> It's not the ideal way to build TDD from the ground up, but I've found it
> can help to give you some control over your overall environment, so that as
> you change code, you can be confident that your major functionality hasn't
> just failed.
Yes, this is a very good point. If you really must write tests for
your existing code, start with some high-level 'happy path' tests of
the flow of your external user interface. This can avoid the catch-22
of lower-level unit tests forcing you to refactor when you don't have
any tests to catch bugs.
-- Chad
--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
http://ruby.meetup.com/81/
This message was sent by Chad Woolley ([address removed]) from The East Bay Ruby Meetup Group.
To learn more about Chad Woolley, visit his/her member profile: http://ruby.meetup.com/81/members/2726338/
To unsubscribe or to update your mailing list settings, click here: http://www.meetup.com/account/comm/
Meetup Support: [address removed]
632 Broadway, New York, NY 10012 USA
Wolf
-- Sent from my Palm Pr��
Chad Woolley wrote:
On Sun, Aug 23, 2009 at 3:06 PM, Steve Midgley<[address removed]> wrote:
> Whatever framework you decide to use, one tip that might be helpful in
> building legacy tests, is to start with your "smoke tests." You could build
> a lot of: "Given this set of parameters, this GET request should return
> 200-Ok, and in the resulting HTML there should be an input tag with this
> value." This sets some a baseline harness around your system to define it's
> behavior in the most fundamental way (these parameters in, this html out).
>
> It's not the ideal way to build TDD from the ground up, but I've found it
> can help to give you some control over your overall environment, so that as
> you change code, you can be confident that your major functionality hasn't
> just failed.
Yes, this is a very good point. If you really must write tests for
your existing code, start with some high-level 'happy path' tests of
the flow of your external user interface. This can avoid the catch-22
of lower-level unit tests forcing you to refactor when you don't have
any tests to catch bugs.
-- Chad
--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
http://ruby.meetup.com/81/
This message was sent by Chad Woolley ([address removed]) from The East Bay Ruby Meetup Group.
To learn more about Chad Woolley, visit his/her member profile: http://ruby.meetup.com/81/members/2726338/
To unsubscribe or to update your mailing list settings, click here: http://www.meetup.com/account/comm/
Meetup Support: [address removed]
632 Broadway, New York, NY 10012 USA
People in this
group are also in:
-
GoSF
5,667 Gophers
-
SF New Tech
7,964 Tech Lovers
-
The San Francisco Ruby Meetup Group
5,639 Ruby enthusiasts
-
Swift Language User Group (San Francisco) x Cocoaheads SF
5,602 Swift Developers
-
San Francisco Python Meetup Group
13,824 Python Programmers
-
SF Creative Coders
2,382 Members