Back to Forum

Should Developers Test UI?

Last post 07:22 am March 28, 2014 by Justin Todd
3 replies
Justin Todd
04:10 am March 28, 2014

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
05:56 am March 28, 2014

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
07:04 am March 28, 2014

> 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
07:22 am March 28, 2014

Ok, thanks for the feedback all.

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. For privacy concerns, we cannot allow you to post email addresses. 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.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.