I say this very matter of factually almost as if this statement needs no clarifying. The reality is though that running fully automated tests using a browser has proven to be very difficult. Of all the singular problems we've applied our time to, automating web tests has been one of the most frustrating and time consuming. Our current solution includes a mash up of the following:
Now when we add TeamCity to the mix and have these test run on a remote machine we don't even get to see what's going on as the service is running in the background. This makes troubleshooting almost impossible.
The point of this post is to remind me that when we need to see why these web tests are failing on a remote machine we can get a little help by doing the following.
1. Stop the TeamCity Build Agent service
2. Open a command prompt and run the build agent manually.
C:\TeamCity\buildAgent\bin>agent.bat start
