Home
We are just getting started so documentation is slim and bugs may be plentiful. If you find TestPipe or the idea behind it useful, please consider contributing to the source code or documentation (see Contributing for more information).
If you find bugs or are having issues with TestPipe, please submit a ticket on the issue tracker.
TestPipe is new and still has some pain when setting up a new project for testing. As we stabilize the domain and code we expect there to be an easier setup process and better documentation.
For now, if you want a quick overview of how to get started see Getting Started. You can view more information on using TestPipe in the Documentation.
First and foremost, we wanted to give some love to the .NET community and the developer/tester community at large. They have been good to us over the years and we wanted to give back. This was the best place to re-inject some of the things we learned on the free and open internet.
Well, TestPipe is more guidance than framework. Although, we provide various classes and interfaces that look like a test framework, TestPipe actually drives other frameworks to get the actual testing done. TestPipe is more of our way of producing maintainable test automation suites. We produced abstractions as a way of uncoupling testing from the various test frameworks and injected our opinion in terms of how to make test maintenance easier. We wanted to make it easier to extend and customize the "test framework" without having to rework thousands of tests.
Managing test scripts in a large test suite can be a nightmare and we see TestPipe as a collection concepts that help make tests more maintainable. This is the core goal of this project and the guiding principle in future development. We are OK with complexity in setup as long as writing and maintaining tests is simple.