This project is read-only.

How I use TripleA

  1. Create a new class library project for your tests
  2. Install the TripleA.StoryQ NuGet package (this will download TripleA Core, StoryQ plus other dependent packages).
  3. Install the NUnit NuGet package
  4. Install Visual Studio Extension "Slow Cheetah" - this allows you to create an app.config file per platform configuration (environment). This is a great solution for managing the "variables" between environment (eg: server names)
  5. Write NUnit tests using the technique described here with StoryQ
  6. Create a script that takes the test assembly output files (bin\debug) and bundle these with the nunit gui.exe (& supporting files). This then becomes a transportable "package" that can be executed in the location that best suits your environment.

Building a Test package around NUnit GUI

A great way to expose your verification tests is making them part of your CI (System/Smoke) Test process or as a standalone package that anyone can execute, and the best way to do this is to get your build to bundle the test assemblies with the NUnit (or your runner) executables, even throw in a batch file or Powershell script to launch the tests. An effective way of running these tests is with the NUnit GUI - you get immediate, visual feedback on the state.

TODO: How you set up NUnit GUI to run your tests....

Ninjas apply here...

I have another project called Wolfpack that is a .Net based monitoring system. One of the plug-ins for this system is to automatically deploy and run your tests - all you need to do is package your test assemblies into a NuGet package, add NUnit.Runner as a dependent package and publish it to a NuGet gallery feed (private preferably!) - Wolfpack will take care of executing the tests and alerting you to any failures.

More info here...

Last edited Nov 5, 2012 at 9:03 AM by jimbobdog, version 10


No comments yet.