RowTest Extension 1.2.0

7 Comments

1. Gaurav
   Posted February 6, 2008 at 3:38 pm | Permalink

   Hi,
   Rowtests are itself not getting detected with version 1.2.0.I am using Nunit 2.4.
   GAURAV
   HARSHA

2. Gaurav
   Posted February 7, 2008 at 4:38 am | Permalink

   Hi Andreas,
   The above problem is solved.We were using Test Driven add-in with Nunit.When we chose the setup type to “Typical” for Test Driven 2.11 and installed it, it started detecting Rowtests.I guess the earlier user had installed some other setup type on this system.

   GAURAV
   HARSHA

3. Andy Morris
   Posted February 7, 2008 at 1:31 pm | Permalink

   When using NUnit 2.4.6 and RowTest 1.2.0 the following code fails. At first I was using the TestDriven.net runner, but I also got the error after uninstalling all things NUnit, installing Nunit 2.4.5 and RowTest 1.2.0, refreshing my references and running the tests from the Nunit gui.

   This all worked fine under NUNit2.4.5 and RowTest 1.1.0

   This would be a good time to mention how much I appreciate the work you have done in RowTest

   //Code starts

   using NUnit.Framework;
   using NUnitExtension.RowTest;

   namespace MultiRowTests
   {
   [TestFixture]
   public class TestClass
   {
   private bool setupHasRun = false;

   [SetUp]
   public void Setup()
   {
   setupHasRun = true;
   }

   [Test]
   public void singleSetupTest()
   {
   Assert.That(setupHasRun);
   }

   [RowTest]
   [Row()]
   public void rowSetupTest()
   {
   Assert.That(setupHasRun);
   }
   }
   }

4. Richard
   Posted February 12, 2008 at 6:28 pm | Permalink

   I think there still is a problem with the [TestFixtureSetup]. It is run, but if I set a class-variable (e.g. a private MockRepository _mockRepository) from within the [TestFixtureSetup]-method, then this variable is back to null when the [SetUp] is run. This does not happen with “normal” [Test]s in the same fixture.

5. Richard
   Posted February 13, 2008 at 2:02 pm | Permalink

   Sorry, when re-reading the comment by Andy Morris I realized that his problem is (probably) essentially my problem. So I made a duplicate comment.

6. Andy Morris
   Posted February 13, 2008 at 6:38 pm | Permalink

   I’ve tried this with NUnit 2.4.5.0, test runner 2.11.2177 and rowtest v2.0.50727

   using NUnit.Framework; // Requires reference nunit.framework
   using NUnit.Framework.SyntaxHelpers;
   using NUnitExtension.RowTest;

   namespace TestFirstLearning
   {
   [TestFixture]
   public class RowTestBugExample
   {
   private bool setupDone;
   private bool fixtureSetupDone;

   [TestFixtureSetUp ]
   public void FixtureSetup()
   {
   fixtureSetupDone = true;
   }
   [SetUp]
   public void Setup()
   {
   setupDone = true;
   }

   [Test]
   public void Test()
   {
   Assert.That(setupDone,”Check setupDone”);
   Assert.That(fixtureSetupDone, “Check fixtureSetupDone”);
   }

   [RowTest]
   [Row("Dummy")]
   public void RowTest(string rowData)
   {
   Assert.That(rowData, Is.EqualTo(”Dummy”));
   Assert.That(setupDone, “Check setupDone”);
   Assert.That(fixtureSetupDone, “Check fixtureSetupDone”);
   }
   }

   }

   and get

   TestCase ‘TestFirstLearning.RowTestBugExample.RowTest(Dummy)’
   failed:
   Check fixtureSetupDone
   Expected: True
   But was: False

   I dont have tiome to try with the most recent version, I think I might get a failure on “Check setupDone” as well. Can anyone else try it out and see?

7. Andreas Schlapsi
   Posted February 17, 2008 at 9:27 pm | Permalink

   I released a new version which should fix this issue.