Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

While testing web application migrations to newer servers, what kinds of gotchya's should I be looking out for. I think that I have a pretty good handle on most of the testing, however, I have this sinking feeling that I'm missing something. As for the technology being used, it's mostly ASP classic with a little bit of .NET, so, obviously on a windows infrastruture.

share|improve this question

Two things come to head about new server migration.

  • New server environment (version differences can lead to incorrectly working application (deprecated methods, new environment bugs and so on));
  • Incorrect new server configuration;
share|improve this answer

You need to consider what is changing, and what is not.

  • Newer hardware, but unchanged software?
  • Newer software?
  • Applications changes, too?
  • Any configuration changes?
share|improve this answer
To expand a little on Joe's answer, consider also: what has changed that should not? what has not changed that should? I don't know if looking at the setup of the new machine(s) falls within your jurisdiction, but you may also look at things like disk partitioning, how and where logs are written, required connectivity between other machines, error reporting for various modes of failure. – Ben Kelly Jan 4 '12 at 3:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.