search

jbubriski / ST4bby

A POCO generator that doesn't rely on the Entity Framework.
MIT License
18 stars 8 forks source link

Spike: Investigate Unit Testing options #12

Open jbubriski opened 12 years ago

jbubriski commented 12 years ago

How hard is it to unit test T4? Would we have to write more T4? Would we have to compile our code into a separate assembly? GRAW?

codeimpossible commented 12 years ago

Most of the resources for testing T4 directly suggest writing tests in... more T4. Which sounds disgusting and hacky. We could package all of our logic into a DLL and test that with anything (xUnit, NUnit, Machine Spec) but we'd have to ship the dll and the T4.

I believe we could get around having people add a reference by just using an import in the t4 with the path our dll, but we'd need a install.ps1 in our nuget to get this working.

OTOH: this isn't a very complex piece of coding (yet) so I honestly think unit testing can be replaced by good 'ol manual testing and code reviews.

Thoughts?

jbubriski commented 12 years ago

Yeah let's skip the unit testing for now. But like you said, when we figure out how to setup the Nuget package we can move the code into DLL(s).

On Jan 29, 2012, at 3:58 PM, Jared Barbozareply@reply.github.com wrote:

Most of the resources for testing T4 directly suggest writing tests in... more T4. Which sounds disgusting and hacky. We could package all of our logic into a DLL and test that with anything (xUnit, NUnit, Machine Spec) but we'd have to ship the dll and the T4.

I believe we could get around having people add a reference by just using an import in the t4 with the path our dll, but we'd need a install.ps1 in our nuget to get this working.

OTOH: this isn't a very complex piece of coding (yet) so I honestly think unit testing can be replaced by good 'ol manual testing and code reviews.

Thoughts?

Reply to this email directly or view it on GitHub: https://github.com/jbubriski/ST4bby/issues/12#issuecomment-3711207