I am familiar with TDD and use it both in my workplace and in my home web applications. However, every time I used TDD in a web application, I had the luxury of having full access to a web server. This means that I can upgrade the server and then run my unit tests directly from the server. My question is that if you use third-party web hosting, how do you conduct unit tests on them?
You can argue that if your application is well designed and your build process sounds and is automated, then it is not necessary to run test blocks on your production server, but I personally like peace of mind, knowing that everything is still “green” after a major update.
For everyone who answered “just a test before deployment” and “don't you have an intermediate server?”, I understand where you came from. I have an intermediate server and a CI process. My unit tests are running, and I’m sure that they all pass before upgrading to release.
I understand that in an ideal world, I would not worry about that. But I have seen this before. If the file is not in the update or the SQL script does not start, the effects immediately become apparent when you run your unit tests, but can go unnoticed for quite some time without them.
What I am asking here is that there is some way, if only to satisfy my own compulsive desires, run unit test on a server on which I cannot install applications or remote applications (for example, the one I I will only have FTP access to update files)?
source
share