Here is a bit of context:I am practicing TDD for a new application that will target .NET 3.5 CF and .NET 4.5.2 FF.I might have some part of the code that use polymorphisme to decide at run-time a strategy (the design pattern) to use while running on a .NET 3.5 CF machine and an another running on a .NET 4.5.2 FF machine. Both version are in different solution and code files are added as links as to not duplicate the code. This is out of my control since it was a corporate decision made above me and I have to live with it.My question is: Should I add a test project to both the FF version and the CF version (by adding the test cases files as links in the CF solution to be able to run these in CF) or if everything is tested in FF I can assume the CF half is OK?Note:I know the two solutions part might not be the best way to go, but this is what I have to work with.
Should I do unit tests for the same application targeted on two different version of .NET?
.net;tdd
Stop linking the code files.Instead, start extracting the shared files into actual class libraries that target 3.5. If you're already sharing them between projects, then they must already compile with that version of the compiler. Remember, you can always reference a library built against an older version of the framework.Stop the insanity. Will anyone actually know that you did the right thing and created class libraries instead? You say this is a new project, there's no reason to create a mess like this on day one. 