This page will be a collection of resources used in the development or inception of this project.
This course was the inspiration for this project. I wanted to practice what I had learned, and a Unit testing API seemed to be good practice.
This site provided the code, which is used to implement the Fluent API methods. Specifically, it defined a decorator for fluency. The decorator returns a complete copy of the DeclareATest instance. This would, in theory, allow you to re-use partial test declarations. Such as just declaring the arrangement, if it was complex. Not that this currently saves a lot. I have used it because I like the Decorator style for fluency better than others. But also because I like the protection that deepcopy provides when using the API.
Strictly speaking this might be a memory hog, and otherwise an un-useful feature. I will evaluate it later for its potential value in user-protiections againts memory and possibly performance concerns.
- StackExchange Discussion-Fluent Interface vs. Args
- Consulted but not used, as I somewhat disagree.