MS Test Failed test failures after changes when the project is under source control?
I noticed that if I have a regression test suite and you decide to change a property on one of my objects (DTOs) from int to decimal, for example, I make all other changes and the tests run as usual. But if this project is under source control (VSS on purpose) this small change will cause something weird ...
Like this question
Testing in Visual Studio succeeds individually, failing to set
But a little differently. I can make this change and try to run my tests and any test that asserts that this new datatype will fail, but if I then click debug tested tests and then run through the previously failed tests, they fail. No changes to the test code / etc
Does anyone know why this might be happening? I hate to work outside of source control, but if my tests are not reliable ... why would they do that at all ... and I live to test the code: P
source to share
Given the age of the question, I doubt this is still a problem for you, but I am wondering if you have bin or obj folders under source control or the assembly that is in them?
If that is when you compile the application (before running MSTest), the source controlled collections will be read-only and will not be overridden by the compiler, and therefore your tests will contradict the legacy binaries.
source to share