Renaming "Test Framework" folder to just "Framework"
Adding "Framework" TestCategory attribute to all tests
Fixing a default exception message that was wrong
Adding baseline functionality for assertions upon an executable's output/error, wall clock run time, memory consumption, processor time, or exit code

There's a problem where you cannot use Process to access both a sequentially consistent output (as you might see in a console application) and a separated output at the same time; it's not even clear if Windows supports doing this whatsoever. This informed the decision to create 3 classes where one is just an interface to the other 2 - this means that the process is executed twice and has performance implications. The API is set up to choose which sort of output you want at the class level. I still need to add some mechanism for either supporting input into processes that are requesting input or detecting that input is required, but this is a good start.
Renaming content files to start with _ so they're sorted in the same spot and aren't in the middle of other files
Adding "readonly" modifier to static things that should not be altered
Cleaning up a few superfluous usings
Changing parameter order on comparison assertions (it didn't make much sense to say GreaterThan(0, field) for example because when you type it out, you use field > 0)
Jury still out on whether InRange should be lower bound, value, upper bound or consistent with the rest
Making the comparison tests suck slightly less; there were duplicate tests and I suspect this was a problem
Also added cases to a couple tests
Some documentation
Additional validation of ProcessResult objects
Adding more documentation comments
Adding a few see crefs
Reworking the interface API for IProcessSpawner a bit (a more robust use case isn't really needed for now and just complicated things)
Adding some documentation
Merge branch 'master' of https://github.com/LazyBui/CsTestProj