is it just me, or did peter not send his message to anyone but steve -
twice? all i see is his "and finally..." then this from steve.
Arklan
--
As long as there is light, the darkness holds no fear. And yet, even in the
deepest black, there is life. - Arklan Uth Oslin
I want to leave thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Peter,
Thank you for your in depth, forthright and professional response. You
have answered my questions. And you have cleared up a lot of
confusion I had in my mind. (and I read ditto as i dont know) I
appreciate the extra information. :)
This i
And, finally, when I say "Ditto to above" I mean "I have no idea", not
"nope". Double oops.
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know ex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/2012 03:02, Gregory Maxwell wrote:
> On Tue, Oct 2, 2012 at 9:15 PM, steve wrote:
>> Im ready to go, more or less. Please check out the links in my
>> previous emails. I have over 400 testcases (8 platforms * 50
>> release tests) - Also I a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/2012 17:52, Peter Vessenes wrote:
> I'm a big proponent of a testing project.
I am very happy to hear this, however, your actual words are slightly
evasive. I do not expect you to be up to speed on this. Gavin started
a project called 'the bi
I'm a big proponent of a testing project.
I think if one could self organize that Gavin and team wanted to bless we
could put up some BTC as bounties or funding. We won't have our heads
around the foundation budget for a few more weeks, but self-organization is
often slower than budgeting. :)
Thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/2012 14:52, Arklan Uth Oslin wrote:
> Hi guys.
>
> So, as I mentioned on the bitcointalk.org forums thread about the
> foundation, I want to get involved in the QA side of bitcoin
> development. I've done functional testing in the video gam
Hi guys.
So, as I mentioned on the bitcointalk.org forums thread about the
foundation, I want to get involved in the QA side of bitcoin
development. I've done functional testing in the video game industry for
years. I've read all the messages in this thread, but I'm left unclear how
I can most eff
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Gavin,
Sorry for the delayed response, I wanted to take a couple of days to
reflect on your email.
On 26/09/2012 19:09, Gavin Andresen wrote:
And their are other methods too.
The GUI::Test package for perl will allow this to be greatly
automa
On Wed, Sep 26, 2012 at 8:53 PM, Matt Corallo wrote:
> Jenkins currently just runs the test script after each new commit to
> bitcoin (and provides binaries to anyone who wants them), so its pretty
> basic (though jenkins has way more features than we use). The bitcoin
> one lives at http://jenki
On Wed, 2012-09-26 at 13:28 +0100, steve wrote:
> 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 inc
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,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/09/2012 17:06, Mark Friedenbach wrote:
> Running a concurrent Mantis tracker would be confusing and fragment
> the development pathway. We have an issue tracker; it's on github.
I think you misunderstand what I am proposing.
QA needs more than
On Wed, Sep 26, 2012 at 12:06 PM, Mark Friedenbach 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
> (re-opening tickets
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, regression
-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
>> - for
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
so
-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 reques
On Wednesday, September 26, 2012 11:41:13 AM Daniel F wrote:
> on 09/26/2012 01:49 AM Wladimir said the following:
> > I'm willing to write this. But I know these kinds of proposals always
> > end in a big discussion about what should be and what should not be on
> > bitcoin.org, however we should
on 09/26/2012 01:49 AM Wladimir said the following:
> I'm willing to write this. But I know these kinds of proposals always
> end in a big discussion about what should be and what should not be on
> bitcoin.org, however we should be a bit pragmatic here.
May I suggest a page bitcoin.org/developer
I think it's a great initiative Steve,
On Tue, Sep 25, 2012 at 10:41 PM, Matt Corallo wrote:
> They both run the same set of scripts, namely those at
> https://github.com/TheBlueMatt/test-scripts (its pretty basic right now,
> but since it is on github, I was hoping someone would find the
> insp
This is definitely worth doing and I wish you every encouragement.
For my part I'm working on a different area of the Bitcoin ecosystem and
that is taking up all my time so I can only cheer you on from the sidelines.
On 25 September 2012 21:49, Daniel F wrote:
> on 09/25/2012 02:32 PM steve sai
on 09/25/2012 02:32 PM steve said the following:
> Anyone interested in helping out/reviewing processes? even if it is just
> some encouragement, it is all greatly appreciated.
not enough time in the day for me to seriously help out, but since you
asked, here's some encouragement. :) more testing
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 from github).
They both run the same set of scripts, namely those at
https://github.com/TheBlueMatt/test-scripts (its pretty basic right
24 matches
Mail list logo
