Testing a Newer Build - Testing Fails
As vthomeschoolmom says, we need a few more details. Having a "fail" could mean any number of things. Usually, there's an error message in the log with some details.
My suspicion is that, since you edited the login for the new version, that perhaps there are other things that may need to be edited... and the fact that you needed to edit the login means that, perhaps, you haven't created your automation to be more robust for handling multiple versions of your application under test (some hard coded strings, etc, in your NameMapping and so on).
Automation, in general, takes work for it to be done right. There are a lot of factors to consider. But there is also an understanding of a maintenance cycle even for automation. Applications change, workflows through those applications change, so as the applications are updated, the automation needs to keep pace. There are a number of things you can do to mitigate this, but you will need to maintain automation after it's initial creation to some extent.
