public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed

From: Gavin Andresen <gavinandresen@gmail•com>
To: steve <steve@mistfpga•net>
Cc: Bitcoin Development List <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Testing Project
Date: Wed, 26 Sep 2012 14:09:55 -0400	[thread overview]
Message-ID: <CABsx9T119rT1NssV6YO8KPse3sEGHZJ-vzFFD3o=aAQ161g6-A@mail.gmail.com> (raw)
In-Reply-To: <50633F02.6030807@mistfpga.net>

[-- Attachment #1: Type: text/plain, Size: 837 bytes --]

There are test cases that can be automated. That's Jenkins, and those will
be run automagically.

Then there are tests that cannot be automated; things like "Does the GUI
look OK on all of the platforms that we support (Windows XP/2000/Vista/7/8,
Ubuntu/Debian blah with window managers foo and bar, OSX 10.5/6/7/8)."

Thanks to Matt, we're doing great with automated functional test cases (can
always do better, of course).

We're failing on simple, boring stuff like making sure we actually run on
all of the platforms that we say we run on BEFORE final release. That is
where I think a QA team can add a lot of value.

Steve: I'm worried you're over-designing The Process. A release acceptance
test plan could be nothing more than a step-by-step checklist on a wiki
page, Google Doc, or Drobox shared folder...

-- 
--
Gavin Andresen

[-- Attachment #2: Type: text/html, Size: 1008 bytes --]

next prev parent reply	other threads:[~2012-09-26 18:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 18:32 steve
2012-09-25 20:41 ` Matt Corallo
2012-09-26  5:49   ` Wladimir
2012-09-26 11:41     ` Daniel F
2012-09-26 12:00       ` Luke-Jr
2012-09-26 12:28   ` steve
2012-09-26 12:49     ` Wladimir
2012-09-26 13:22       ` steve
2012-09-26 16:06         ` Mark Friedenbach
2012-09-26 17:10           ` Jeff Garzik
2012-09-26 17:44           ` steve
2012-09-26 18:09             ` Gavin Andresen [this message]
2012-09-29 18:26               ` steve
2012-10-01 13:52                 ` Arklan Uth Oslin
2012-10-01 14:28                   ` steve
2012-10-01 16:52                     ` Peter Vessenes
2012-10-03  1:15                       ` steve
2012-10-03  2:02                         ` Gregory Maxwell
2012-10-03  3:00                           ` steve
     [not found]                         ` <CAMGNxUu=LTZyAxKt3pAYSVxyhHBU9pyJPCiFs-tA_weYNNXbtw@mail.gmail.com>
     [not found]                           ` <CAMGNxUuHRBkE_MbmY=A0vQvq=gMfzCFG8Us7SdBn-14KiKMaNg@mail.gmail.com>
2012-10-03  5:04                             ` Peter Vessenes
2012-10-03 16:06                             ` steve
2012-10-03 16:11                               ` Arklan Uth Oslin
2012-10-03 16:15                           ` [Bitcoin-development] Fwd: " steve
2012-10-03 17:09                             ` Peter Vessenes
2012-10-03 17:30                               ` Gavin Andresen
2012-09-27  0:53     ` [Bitcoin-development] " Matt Corallo
2012-09-27  2:29       ` Gregory Maxwell
2012-09-25 20:49 ` Daniel F
2012-09-25 21:25   ` Gary Rowe

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='CABsx9T119rT1NssV6YO8KPse3sEGHZJ-vzFFD3o=aAQ161g6-A@mail.gmail.com' \
    --to=gavinandresen@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=steve@mistfpga$(echo .)net \
    /path/to/YOUR_REPLY

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox