Forums

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Should Developers Test UI?
Last Post 28 Mar 2014 02:22 AM by Justin Todd. 3 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Justin Todd
New Member
New Member
Posts:48
Justin Todd

--
27 Mar 2014 11:10 PM
    Morning,

    Once a developer is finished with their coding and the feature is ready for UA testing, should the developer run through the UI before marking it ready for testing? Having the dev and the UATesters both testing creates waste, but sometimes the UI "fails" immediately and UATesters cant even perform their tests.

    Thanks,
    Justin

    Chee-Hong Hsia
    New Member
    New Member
    Posts:73
    Chee-Hong Hsia

    --
    28 Mar 2014 12:56 AM
    Hi Justin,

    What’s the teams response when you mention about this issue during the retrospective?
    Seems like there is a quality issue on your team, so be conscious that your developers are not cutting corners purely because they know that the stories will eventually be tested by an UA Tester.
    Despite your feeling of producing waste, I would let the UA tester and developer run the test together. Wouldn’t call it waste but rather fixing issues on-the-fly.

    Cheers, Chee-Hong
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1614
    Ian Mitchell

    --
    28 Mar 2014 02:04 AM
    > Once a developer is finished with their coding and the feature is ready for UA testing,
    > should the developer run through the UI before marking it ready for testing? Having
    > the dev and the UATesters both testing creates waste,

    No, it's waiting until development is finished before testing that creates waste, because it invites rework. Abdicating responsibility for the quality of your own code, and leaving it to someone else to check it, similarly leads to rework and waste.

    If testing early (i.e. during development) reduces the need for rework, then the effort expended in doing so isn't wasted at all. Remember that in agile and lean ways of working the purpose of testing is not to find defects but rather to prevent them.
    Justin Todd
    New Member
    New Member
    Posts:48
    Justin Todd

    --
    28 Mar 2014 02:22 AM
    Ok, thanks for the feedback all.
    You are not authorized to post a reply.


    Feedback