Any way it can be found here
http://neilmartinagile.wordpress.com/2009/04/14/a-variation-on-nbehave-story/
regards
Neil Martin
&
Ronnie Barker

1) Where can I found NBehave documentation?
2) What are the requirements (HD, OS, .NET version, VS version etc.) in order to instal NBehave?

Let me know if poss!
david (at) electrichornet (dot) com

I agree about the semantics.

However (not that I am trying to convince you ) it’s the feeling that I like about making a distinction between a spec. and an observation.

And I would rather put it:

These specifications are concerning this type
vs.
These observations are concerning this type

because they are both part of the (sometimes) same concern, only differ by their intent… with the first we specify how SUT should behave, with the second we observe what that (or other) behavior should do (or result to) – which is equaly important in some scenarios.

Anyway… I am very happy Gallio will support it. It trully will be a great engine to work with (now if only TDD.NET would comply as well )

–
Vladan

I think it is a matter of semantics.

Write it out in a sentence format:

These specifications are observing this type

vs

These specifications are concerning this type

the ladder is more appropriate to me as it conveys importance and something of iterest more so then simply observing.

Although this could simply be an English thing.

I have asked the Gallio crew if we can substitute alias in for attributes. Jeff mentioned this shouldn’t be a problem. So we could both be right in the end.

I just started a discussion thread on the AltDotNet yahoo group about this very subject.

Sounds great! Thnx!
It’s a struggle worth fighting, I am glad your not giving up on it (even for Resharper working better as JP mentioned ).

What do you think about [Observation]?

–
Vladan

>What do you think of an alternative approach to Concerns – nested classes with [Concern] attribute:

I had a feeling you were going to ask this question. The ONLY reason why I have elected not to format it this was is because some of the runners have an issue with nest TestFixtures. As we move towards Gallio this is something I will really be pursuing. If not for anything else then to make it more akin to rSpec. Example:

require ‘user’

describe User do

before(:each) do
@user = User.new
end

context “(adding assigned role)” do
before(:each) do
@user.assign_role(“Manager”)
end

specify “should be in any roles assigned to it” do
@user.should be_in_role(“Manager”)
end

specify “should not be in any role not assigned to it” do
@user.should_not be_in_role(“unassigned role”)
end
end

context “(adding assigned group)” do

end
end

It is all well and good to learn and borrow from other frameworks, other languages, other platforms, etc. but one still needs to keep in mind the rules, guidelines, and conventions of the target framework/language/platform/etc.