Found out we are losing time due to aborted runs. People are looking at different ways to avoid the run getting aborted. I feel it is mostly due to environment failures. Having a good environment should provent 70% of the failures. On another note, I would like to have an email sent to all of us in NFT whenever a run is triggered or when it is completed/aborted.
I have two solutions for that which depends on following info (ie whenever a run is triggered or completed/aborted, VSTS writes into the loadtest database).
1. A trigger on the database . Basically fired on “insert or update”. And this sends an email to us.
2. Wrote a script in Auto It which queries the database and finds out if a new run was introduced or not. This would require the script to know about the latest run id (which will be fed as input parameter)
Had a discussion with our architect and he felt the first option was better. I felt the same too.