Unchecked Test Step still executes

3 posts, 0 answers
  1. James
    James avatar
    6 posts
    Member since:
    May 2013

    Posted 28 Jun 2013 Link to this post

    Hi Telerik Team,

    I have a test that was created and stored in TFS awhile ago (prior to me joining the company). This test is part of a test list that also exists in TFS. There are two changes that need to be done to this test:

    1. Change a date from 01/01/10 to 01/01/13 (this is a different test step than the below item).
    2. Remove two steps that interact with an object that is being removed from the application (radcombobox).

    I am able to perform the first change no problem. Updating that data without committing the test to TFS & running the test works as-expected. If I uncheck the two test steps however and run the test, the steps are still executed which does not seem correct. I then committed the test to TFS with both changes and the test continues to execute those two steps even though it should not (right?).

    Next I deleted the test list and re-created it and ran the test list and it still executes those two unchecked steps. I know I will eventually simply delete those two steps and commit the change but nevertheless, shouldn't TS skip any unchecked steps?

    Please see the attachment for screenshots. Pic1 is the first step and Pic2 is the second step, both which should not run.

    Thank you for any help.

  2. Cody
    Cody avatar
    3354 posts

    Posted 03 Jul 2013 Link to this post

    Hello James,

    Agreed, unchecked test steps are not supposed to be executed. I don't have any immediate explanation why they would still execute.

    Your screen shots only show that the steps were unchecked. Can you show me evidence the steps executed anyway?

    Was this a test run on your local development machine or a remote execution server? If it was a remote execution server I wonder if somehow the two are out of sync. In other words you changed the test on your local machine at C:\Test Studio\ProjectA, but the execution server is actually running the tests from it's C:\Test Studio\ProjectA folder, i.e. an old copy of the test, not the current copy that you just updated. Is something like this feasible?

    Free summer webinars on advanced web automation tactics hosted by Jim Holmes & Adam Goucher.
    Reserve your seat today!
  3. James
    James avatar
    6 posts
    Member since:
    May 2013

    Posted 03 Jul 2013 Link to this post

    Hi Cody,

    I just figured out the problem. It turns out there was a step I missed that was checking for the existence of the object (step 5) in the wrong place as there was no interaction with said object until step 9/10.

    So sometimes the answer is right in front of you is the moral of this post. Once I unchecked step 5 the test runs as expected. Thank you for your time.

Back to Top