Creating parallel tests for NUnit with PNUnit

Hands on lab

pablo santos luaces

The history of PNUnit• Back in 2005, December• We needed a way to test our server + our client

• We wanted to automate the CLI

Our testing system

Nunit and GUI were fine…• We were using Nunit• We were using Automated QA Test Complete (Now Smart Bear)

• But we needed something to automate the CLI…

What we needed…

So we need to..• Wait till the server is up and running

• Then start launching commands…

But we wanted more…• The basic sample is client and server on the same machine

• BUT, we wanted more!

Multiple OSServer• Windows (XP, 2000, 2003, 2008, Vista, 7)

• Linux (several flavors)

• Mac OS X• Solaris!

Client• Windows• Linux• Mac OS X• Solaris

And combinations between the two!!

Plus multiple backends…• Server running with• SQL Server• MySQL• Firebird• SQLite• Postgresql…

So…• We needed a «networked» way to sync client and servers (server start up might vary)

• But we wanted more ;)

What about more complex tests?• Stuff like: two clients start and one wait for the other to do something…

• We needed sync mechanims…

Barriers• The very basic sync mechanism is the barrier: you create a barrier, and then each test must «hit it» before going forward!

PNUnit structure

And we also use it for cluster testing!!!

And we use it extensively• Run a basic suite once each task is closed

• Run the entire suite (on several vmachines) each time we create a release

…and here we go

Go for PNUnit!!!