I have recently released two commercial versions of TestDriven.NET. The need to create a commercial version kind of crept up on me. I had been working on it as much as I could between consultancy gigs. By the end of last year I realised it had turned into very much a full time job. I was actively turning down work in order to carry on supporting TestDriven.NET. For this to be sustainable I really needed to become an ISV!
My original plan was to release the professional version of TestDriven.NET at the beginning of this year. Unfortunately something happened to derail that plan (more in a later post). You may have noticed that recent TestDriven.NET releases have been as much about updates to Grant Drake's NCoverExplorer than about TestDriven.NET itself. I am grateful to Grant for keeping me focused and generally positive through a difficult few months. TestDriven.NET 2.0 is now back on track, more stable than ever and and has some useful new features.
At the moment the difference between between TestDriven.NET enterprise and professional is purely in the licence. TestDriven.NET enterprise is for organisations that wish to deploy a version of TestDriven.NET onto multiple machines. The licence grants the right to distribute TestDriven.NET enterprise onto as many machines as the organisation has licences. The enterprise licence includes one year of guaranteed support and software updates.
TestDriven.NET professional is intended for developers who are responsible for acquiring and installing their own development tools. This version can be installed on as many machines as the licenced developer. TestDriven.NET professional can't be stored on a network share or deployed from a central location for use by multiple developers.
Just because the commercial versions now exist doesn't mean I'm turning my back on hobbyist/budget-constrained users. There is still a TestDriven.NET personal version available. This version isn't crippled, it doesn't nag you and you don't need to enter a licence code. I could hardly call it "zero friction" if it did. I do however ask that if you use it regularly on commercial projects you purchase a professional licence. If you're using a version of TestDriven.NET that is deployed from a central location then you will need an enterprise licence.
Thankyou for helping me turn TestDriven.NET from an obsession into a job! If you have any questions please contact me.