From: steve <steve@mistfpga•net>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Development List
<bitcoin-development@lists•sourceforge.net>,
Bill Hees <billhees@gmail•com>
Subject: Re: [Bitcoin-development] Bitcoin Testing Project
Date: Wed, 26 Sep 2012 14:22:52 +0100 [thread overview]
Message-ID: <506301AC.90101@mistfpga.net> (raw)
In-Reply-To: <CA+s+GJBM4DwDoqT8RC0+SyrLYrLGZuGZSuoj7zbHunQa3kFoRA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 26/09/2012 13:49, Wladimir wrote:
> Steve,
Hi Wladimir,
>
>> So, currently there are 4 potential places for bugs to be
>> reported 1 - jenkins (and unit tests) 2 - git 3 - mailing list 4
>> - forum (bitcointalk...) 5? - is there still the ability to add
>> bugs via sourceforge?
>
> Currently github is the authoritative place to report issues. When
> someone reports a bug on the mailing list, IRC or forum, they are
> generally asked to make a github issue (or, someone else makes the
> issue for them). Failed tests are generally also reported on
> github, by the pull tester.
excellent, that makes things much easier.
>
> We currently have 232 issues, mostly classified into categories
> such as "Bug", "Improvement", "GUI", "Wallet", and so on.
>
> Also it's easy to refer to github issues in commits with #123, with
> automatic linking.
>
> I'm not sure it is worth the effort to move to another system
> (especially if you need a another login etc...). But I'm probably
> misunderstanding what you're trying to do.
I think you might be misunderstanding a little. I am not trying to
replace the current system, I need to make sure that what I do will be
compatible with it (seamlessly so for the developer). I do not want this
to generate extra work for the development team.
However testing is a lot more than just bug reporting, dont get me
wrong bug reports are important, but so is running a testcase and that
testcase passing, especially if that testcase is linked to the proof
of a requirement. I am trying to develop a qa environment that is
conducive to testing and will allow the testers to shine in all their
glory :) and we need different tools and methodologies.
Git is too developer centric to be useful for organising testing. -
however there is a large amount of software that is compatible with
git, so the core development team only ever need to work with git.
The linking between a bug, the requirement, the fix, the retest, and
updating of regression testplan is vital. So is the ability to
organise testing campaigns and assigning tests, work units and test
relevant docs/scripts/ideas, etc.
I hope this clears things up a bit?
Cheers,
steve
>
> Wladimir
>
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQEcBAEBAgAGBQJQYwESAAoJEFvEB9dQFvtQ/GUH/jv2c5L0OcL/kHkX/z0Yqbl/
2IntPLdjXNKLuz0A7BMz7XfUyVmWlZrw44qxmi+Vyk5PKNBjYIidm763xHnTeJLN
ULQBckYexMvan9hAyYZUOt85IpesdNgqTIsqh8f49y4roHOy8GT4M/2fhzXpnsGg
G9d2m8jWGpj/kxl9qE7/WjVQC4APwBi/NiJsCrcHswgweN+zENc/Pot9YBLxAZu/
ACBUX/xFymRdaZN8P2LWBXuKx6E2WEcBdPCCWArX07wPiBlrashx9Gz6tiNzIiNq
x2c4ltLzRa45AmiDtQhwqyTprz/DbyeAYO1sIsfpUxDeu9e3xTb/Zd96jfKIWI0=
=iHI1
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQEcBAEBAgAGBQJQYwGsAAoJEFvEB9dQFvtQxOsIAKgBBOKHNFtoV2cN+GVqzlip
yy0qiMvMTZKrraOhEw8QNNuOlB3LRchi+RDR/PvQkVfuwi/jHB2gUBzlapLoECBv
EH8pgT/MO281pXzARgRSVkRYqkb3ljhQz3mEQg9RhR9h5t9g2mL3Tvppt7249Bg8
oGXPj6xmMcrbClF5qDbwQUUDGJfOo4eti0jSVD3qp2NE7QpPVQwuN5buchpoKt3P
9aJnjeZdLmuAk2RPoDaLXUFc9unT8AcnW96juD0zoVA9wKvAa6/8IZQf0mzV4iZP
yiWGNOQtBZ+jyu2ixiEnvHqqG2ZmjtUVqWtjHkxYgrCyuuK2jOcTMNEWfn7SfKc=
=yP7N
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-09-26 13:23 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 [this message]
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
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=506301AC.90101@mistfpga.net \
--to=steve@mistfpga$(echo .)net \
--cc=billhees@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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