State of Play

I'm afraid our source control database is still out of action.  The whole point of aiming for V1.0 was to mark a stable branch in the database.  It would be crazy to take a snapshot from my development machine and call that V1.0.  Because of this I have decided to go with the last automated build until the database is back up and running.  This is set to time out on the 30th of November.  The golden version should be available well before then.

The positive side to all this is a bit of extra time to get feedback on the installer.  The latest version comes wrapped in a bootstrapper EXE that is capable of uninstalling any previous versions.  I have also hardened the installation and uninstallation code.  If you find any issues at all, please let me know.

You can find the latest build here.

4 Comments

  • Hello,



    We are looking forward to the v1.0 release of TestDriven.NET (especially MbUnit). To use TestDriven.NET are required to have some form of validation of the tool. I'am sure that every TestDriven.NET build generates a test report and maybe a coverage report. It is possible to have those reports available for each build?



    Thank you for your time and specially for providing the software community with such a great test framework.



    Best regards,

    Patricio.

  • Where is the bug tracker?



    I updated to RC7 and now my tests are failing.. no change in code or anything...



    TestCase 'Assembly.TestMethod' failed: File or assembly name Assembly, or one of its dependencies, was not found.

    at Assembly.TestFixutre.TearDown()

  • Sorry just found the Wiki section.. my bad

  • To use TestDriven.NET are required to have some form of validation of the tool. I'am sure that every TestDriven.NET build generates a test report and maybe a coverage report. It is possible to have those reports available for each build?

Comments have been disabled for this content.