-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Matt,
Glad to have another ninja onboard :)
On 25/09/2012 21:41, Matt Corallo wrote:
Although Jenkins may not be the best system, we already have
jenkins and pull-tester (which is a dumb python script I wrote to
test all incoming pull requests
Steve,
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
-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
Running a concurrent Mantis tracker would be confusing and fragment the
development pathway. We have an issue tracker; it's on github.
What's being talked about here are two separate things. Jenkins is a
continuous integration system. It can be configured to run the suite of
unit tests,
On Wed, Sep 26, 2012 at 12:06 PM, Mark Friedenbach m...@monetize.io wrote:
Certainly developers should be responsible for making sure that regression
tests for bugs they fix make it either into the unit tests or Matt's
functional test repository. QA should hold them accountable for that
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,
6 matches
Mail list logo
