This project is read-only.

History - what is this project and why should I care?

Following my natural interests and curiosities during the course of my software development career has led me to the area of automated testing. I write software to test other software. Over the past few years I have noticed a disturbing trend: testing "solutions" are being implemented at a prodigious pace as companies strive to automate the testing of their software, but many of those solutions quickly become a tangle of spaghetti code due to a lack of coding structure within the solution, primarily because people don't think of the testing solution as an application, but rather view it as a collection of individual tests.

I have begun to challenge conventional wisdom surrounding testing in general, and this project is an attempt to provide some tools to facilitate implementation of some alternatives to the conventional way of doing things.

Last edited Jan 11, 2017 at 11:50 AM by nhuntera, version 5