RSpec's contexts are for grouping tests—or defining specifications—for
a Ruby class:
describe Account do
it "should be able to withdraw money and reflect it in its balance"
do
...
end
end
...creates a test basically called "Account should be able to withdraw
money and reflect it in its balance" in a spec for a class called
Account.
It does indeed create a "test container", though—that's what I meant
in the first place. You can do all sorts of stuff with them, but its
title is appended to each of its tests' titles whenever it's displayed
in test results, etc. What I meant is that a test context container be
created. I don't really care as much about the prefixing of test names
itself, but it would make sense and it's what RSpec does.
On Dec 8, 8:31 pm, ".Bill Smith" <[EMAIL PROTECTED]> wrote:
> I agree that the ability to nest tests is important, but I'm not sure
> encoding the nesting information in the test name is necessarily the
> right way to go. Perhaps an intermediate step would be to define a
> "test container" that, when executed, runs all the tests it contains.
> With that foundation, you could define functions that create and
> populate the test container according to various criteria.
>
> What is the purpose of a nested test context in RSpec? Can a test
> belong to more than one nested test context?
>
> Bill
>
> On Dec 7, 4:20 pm, samppi <[EMAIL PROTECTED]> wrote:
>
> > I would wholeheartedly love if tests could be nested. Even if it was
> > as simple as appending a phrase to each nested test:
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To post to this group, send email to clojure@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---
