I was wondering… There are so many different ways to setup and
teardown in the Test Cases thing!!!
So I thought maybe could be a very good idea to open a new topic about
that and people contribute with their ideas about how to implement the
setup and teardown in a typical test case.
On Fri, Nov 09, 2007 at 07:54:20PM +0900, Mario R. wrote:
I was wondering… There are so many different ways to setup and
teardown in the Test Cases thing!!! So I thought maybe could be a very
Are there? I’m only aware of setup() and teardown(), which seem to
create a lot of overhead when running testcases that just contain
assertions without modifying anything.
Are there? I’m only aware of setup() and teardown(), which seem to
create a lot of overhead when running testcases that just contain
assertions without modifying anything.
I was wondering… There are so many different ways to setup and
teardown in the Test Cases thing!!!
by so many do you mean two? 1 - setup. 2 - teardown. ?
So I thought maybe could be a very good idea to open a new topic about
that and people contribute with their ideas about how to implement the
setup and teardown in a typical test case.
“dotnetguy”, “csharp”, ‘clever’ quips like “Setup and teardown methods
attract entropy faster than an outsource programmer with his first
patterns book”…
Lots of words, but… How is ANY of this applicable?
As far as I can tell, we’ve got setup, and teardown… and that’s it.
No magic, just plain old ruby code.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.