In the feedback section of one of my blogs, Aaron Junod wrote:
“In writing this, I just realized something. I think someone should draw a line between writing tests, and actual program code, and then offer different options based on that. They are totally diff coding paradigms, and really merit diff behaviors not only in the compiler, but the IDE.. Hmm.. think I gotta think about this more.”
Note: Jay is not saying that everyone should test in his style. He is saying that both styles can be supported with less work on the Team System team.
I'd like to know your thoughts on this so I can take back some feedback on what the community thinks. I would appreciate a discussion on why you think it's a good or bad idea to force tests to be public. Addressing all of Jay's issues would be very useful, and if you can introduce points as to why limiting what the user can do here is a good thing, then we'd like to here them. Remember, jay is not saying “force the test to be private”, he's saying “support this behavior which doesn't prevent anything that a user can currently do with the system”