You develop an ASP.NET web application that uses a Windows Azure web role.
The application includes a startup script that installs a third-party component.
You are developing a test plan for the startup script.
What should you recommend?
A.
Enable Remote Desktop Protocol (RDP) and deploy the application without the startup script.
Connect to the web role instance by using RDP, and then manually test the startup script.
B.
Deploy the application in the Windows Azure Compute Emulator.
C.
Deploy the application with a custom error page.
D.
Deploy the application and then use IntelliTrace.
Explanation:
So, here are my thoughts on how you might test an OSS/Azure applicationfrom easiest to best. All of these approaches assume that you are deploying a testing framework and test suite with your application.1. RDP to staging instance and run command-line tests. This approach involves enabling RDP access to a deployment (Im assuming deployment to a staging slot), opening a command prompt, and running your tests as (many of you) normally would. The benefit to this approach is that you likely wont have to deviate much from your normal testing routine. The drawbacks are that you have to manually run your tests and disable RDP access to your instances after you push to production.