public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Richards <gizmo@giz-works.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Automatic testing on Gentoo
Date: Tue, 10 May 2011 16:10:57 -0500	[thread overview]
Message-ID: <4DC9A9E1.2020601@giz-works.com> (raw)
In-Reply-To: <4DC99C77.1050105@gentoo.org>

On 05/10/2011 03:13 PM, Jorge Manuel B. S. Vicetto wrote:
> So, why "more testing"? For starters, more *automatic* testing. Then
> more testing as reports from testing can help greatly in identifying
> when things break and why they break. As someone that looks over the
> automatic stage building for amd64 and x86, and that has to talk to
> teams / developers when things break, having more, more in depth and
> regular automatic testing would help my (releng) job.
While I agree whole-heartedly with the sentiment being expressed here, I 
just want to point out and remind everyone that automated testing is no 
substitute for real live people using (and breaking) things.  People are 
remarkably inventive and creative when it comes to finding ways to break 
things in ways that the developers never even considered.

All I'm trying to say is that I've seen (and worked on) far too many 
teams in the past that fell into the trap of thinking automated testing 
was sufficient.  It isn't, but it certainly goes a long way towards 
helping make the manual tester's lives better, by letting them focus on 
finding those problems that aren't (for one reason or another) 
reproducible in an automated testing scenario.

Later,
Chris



  reply	other threads:[~2011-05-10 21:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 20:13 [gentoo-dev] Automatic testing on Gentoo Jorge Manuel B. S. Vicetto
2011-05-10 21:10 ` Chris Richards [this message]
2011-05-11 13:12 ` Jack Morgan
2011-05-11 17:39   ` Alec Warner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DC9A9E1.2020601@giz-works.com \
    --to=gizmo@giz-works.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox