Failure of test iteration during Quick Execute is almost impossible to notice

2 posts, 1 answers
  1. Konstantin
    Konstantin avatar
    11 posts
    Member since:
    Oct 2012

    Posted 12 Mar 2013 Link to this post

    I have single trivial test which tries to navigate somewhere and executes 4 other steps.
    I made it data bound so it does it for 3 different URLs. One of the navigations fails (bad URL).

    When this test is part of the test list and it is run with the list, then its result looks quite clear: 14 out of 15 passed. Test has 5 steps, was run three times, so 15 total. In one case one step failed, so 14/15 looks right.

    Now when I run the same test using Quick Execution it again executes 15 steps for exactly the same reason, but after that the status on top shows 5/5 passed! It only shows the last iteration, not all of them. This is VERY bad because unless sumebody is careful enough to open test run log and search for the word "Fail" there is no way to tell that one of the iterations actually failed.

    Please let me know if I missed something.

    Thank you!
  2. Answer
    Plamen avatar
    8 posts

    Posted 15 Mar 2013 Link to this post

    Hi Konstantin,

    When you are running a data driven test via Quick Execution, there is dropdown showing the iterations. In order to view the failed/passed/total steps for a specific iteration you need to select that iteration from the dropdown list(see screenshot).
    However I agree with you that it will be useful to also have something like a summary showing the sum of all steps from all iterations, so I logged this as a feature request. You can track its progress and vote for it here: Public URL. We take these votes into account when we determine what to focus on in terms of features.

    All the best,
    the Telerik team
    Quickly become an expert in Test Studio, check out our new training sessions!
    Test Studio Trainings
Back to Top