NBehave Source Control Rss Feed

Source code checked in, #96133

Project Collection Service Accounts — Mon, 01 Oct 2012 21:40:31 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #96132

Project Collection Service Accounts — Mon, 01 Oct 2012 21:33:03 GMT

Checked in by server upgrade

Patch Declined: #372

Lazydev — Fri, 08 Jul 2011 19:35:59 GMT

Lazydev has declined patch #372.

Comment:
Too bad codeplex dont notify you when patches are uploaded :-(

Patch Declined: #4308

Lazydev — Fri, 08 Jul 2011 19:34:21 GMT

Lazydev has declined patch #4308.

Comment:
TestDriven.net integration was already in nbehave when this patch was submitted (I think)

Patch Declined: #4238

Lazydev — Fri, 08 Jul 2011 19:29:20 GMT

Lazydev has declined patch #4238.

Comment:
I _think_ similar funktionality exists.

Patch Declined: #3329

Lazydev — Fri, 08 Jul 2011 19:20:54 GMT

Lazydev has declined patch #3329.

Comment:
.

Patch Applied: #699

Lazydev — Fri, 08 Jul 2011 19:14:18 GMT

Lazydev has applied patch #699.

Comment:
applied eons ago.

Patch Declined: #1120

Lazydev — Fri, 08 Jul 2011 19:13:17 GMT

Lazydev has declined patch #1120.

Comment:
Is this reply late or what :(
The automocking container is out and removing [TestFixture] from the base class will break alot of tests (at least mine).

Patch Declined: #3359

Lazydev — Fri, 08 Jul 2011 19:07:08 GMT

Lazydev has declined patch #3359.

Comment:
x

Patch Applied: #3687

Lazydev — Fri, 08 Jul 2011 19:05:44 GMT

Lazydev has applied patch #3687.

Comment:
fix applied long ago.

Patch Applied: #697

Lazydev — Fri, 08 Jul 2011 19:05:08 GMT

Lazydev has applied patch #697.

Comment:
applied, long ago.

Patch Applied: #9751

Lazydev — Fri, 08 Jul 2011 19:01:16 GMT

Lazydev has applied patch #9751.

Comment:
applied. although I wish there where some tests.

Patch Uploaded: #9751

palazkov — Mon, 20 Jun 2011 19:57:32 GMT

palazkov has uploaded a patch.

Description:
Here is a small extension for NBehave which allows to integrate text scenarios into any possible C# xunit frameworks.

For example:

[TestFixture]
public class WhenClassWithTextScenarioHasExternallyProvidedActionSteps
{
[Test]
public void ShouldRecognizeExternalActionSteps()
{
@"Given something
When happens something
Then profit".Execute(
In.Context<GivenActionStep>().And<WhenActionStep>().And<ThenActionStep>());
}
}

[ActionSteps]
public class GivenActionStep
{
[Given("something")]
public void StepImplementation()
{
}
}

[ActionSteps]
public class WhenActionStep
{
[When("happens something")]
public void StepImplementation()
{
}
}

[ActionSteps]
public class ThenActionStep
{
[Then("profit")]
public void StepImplementation()
{
}
}

Source code checked in, #63489

_TFSSERVICE — Tue, 27 Jul 2010 20:28:19 GMT

Checked in by server upgrade

Patch Uploaded: #4308

giancarloorru — Tue, 03 Nov 2009 15:59:24 GMT

giancarloorru has uploaded a patch.

Description:
Hi.
This is my second attempt to allow plain text scenario execution integration in VS.
Things seems to work within TestDriven.

Thanks
giancarlo

Patch Uploaded: #4238

giancarloorru — Tue, 27 Oct 2009 09:57:20 GMT

giancarloorru has uploaded a patch.

Description:
Hi.
This is my first attempt to allow plain text scenario execution integration in VS.
I implemented 2 kind of test: one using a real assembly and the second trying to mock Assembly class. As I seen that it isn't possible a made a refactoring substituting Assembly with _assembly (that is an interface).
Things seems to work within TestDriven.

Thanks
giancarlo
giancarlo.orruATgmail.com

Patch Uploaded: #3687

campbell — Tue, 25 Aug 2009 20:48:17 GMT

campbell has uploaded a patch.

Description:
The following patch addresses a performance issue with the action step implementation of the NBehave framework.

The problem is due to excessive backtracking with the current regular expression being generated to match the action steps. The problem is exasperated further when the action steps themselves are worded similarly. In some cases, we experienced matching times exceeding 45 seconds per action step.

The uploaded file contains a patch for the “ActionStepConverterExtensions” class and a test fixture that demonstrates the problem.

For good measure, we also added the ability to match punctuation characters within the action step parameters as we are currently using the framework to match addresses.

For example we need to match values like the following:

34 Wood Grove Ave. SW, Calgary

Don & Anne

Patch Uploaded: #3359

krugs525 — Sun, 19 Jul 2009 02:36:42 GMT

krugs525 has uploaded a patch.

Description:
Upgraded to NUnit 2.5.1.

In doing this, I changed all tests that were using the [ExpectedException] attribute to use Assert.Throws() because the [ExpectedException] attribute doesn't work with ReSharper 4.5 anymore (known issue).

If you apply this patch, you will also have to get NUnit 2.5.1 and put nunit.framework.dll into the lib directory, and put all of the nunit dlls into tools\nunit.

Patch Uploaded: #3329

krugs525 — Wed, 15 Jul 2009 15:01:51 GMT

krugs525 has uploaded a patch.

Description:
Made CreateStub() and CreateDependency() virtual on SpecBase.

Patch Uploaded: #3295

krugs525 — Fri, 10 Jul 2009 00:41:11 GMT

krugs525 has uploaded a patch.

Description:
Here some NUnit assertions that I've added to my own project and have been using quite extensively...

public static void ShouldContain<T>(this IEnumerable<T> list, params Func<T, bool>[] whereClauses)
public static void ShouldNotContain<T>(this IEnumerable<T> list, params Func<T, bool>[] whereClauses)
public static void ShouldContainOnly<T>(this IEnumerable<T> list, params T[] items)
public static void ShouldContainOnly<T>(this IEnumerable<T> list, params Func<T, bool>[] whereClauses)
public static void ShouldContainOnlyInSameOrder<T>(this IEnumerable<T> list, params T[] items)