Swapping this out for Azure means that any unit test I run that (a) targets a component that's been moved out to Azure, and (b) isn't an indealised "perfect world" unit test that mocks everything bar the code under test will have a direct and tangible cost. It's true, having local infrastructure to run build servers, test instances, unit tests, all the different bits and pieces on costs money, however running unit tests on my local machine doesn't incur a direct and tangible cost.
In the interim though, it occured to me that as I start migrating bits and bobs into Azure, running the associated unit tests will actually cost me money. Shouldn't be a surprise, right? I will need to work out a "whole solution" solution to unit tests somewhere along the line, I'll also need to look at integration tests and will probably at least think about some of the cool CI/Deployment things you can do with Azure. netĪs I'm gearing up to continue my series of posts on the subject of migrating an application to Azure, one of the things that occured to me was that the existing implementation has unit tests.
0 kommentar(er)
