I know QA isn't quite the same thing as testing, but would there be
the resources floating around to have something like a continuous
integration server kicking around? It's a bit buzz-wordy, but knowing
a few minutes after you've pushed something* that you haven't broken
the build can be useful.
For testing, I usually go with the "everything's a failure until the few
success use-cases actually succeed" mantra.
That being said, basic testing parameters should be based on OS,
architecture, and security clearance (admin or std-user). Individual
tools/libraries could get rated based on expec
se; I make the software you use better on
Windows.
From: Jonathan Ben-Joseph [mailto:jben...@gmail.com]
Sent: Wednesday, April 21, 2010 10:48 AM
To: Ritchie Annand
Cc: Garrett Serack; coapp-developers@lists.launchpad.net
Subject: Re: [Coapp-developers] Thinking abotu testing CoApp's tools.
Well, I
e -
From: Jonathan Ben-Joseph
Date: Wednesday, April 21, 2010 11:47 am
Subject: Re: [Coapp-developers] Thinking abotu testing CoApp's tools.
To: Ritchie Annand
Cc: Garrett Serack ,
"coapp-developers@lists.launchpad.net"
> Well, I believe we could do some unit tests on the
es, but those haven't been an issue for quite some
time now.
:)
- Original Message -
From: Garrett Serack
Date: Wednesday, April 21, 2010 10:38 am
Subject: RE: [Coapp-developers] Thinking abotu testing CoApp's tools.
To: Ritchie Annand ,
"coapp-developers@lists.launchpad.net
day, April 21, 2010 9:46 AM
To: Garrett Serack
Cc: Ritchie Annand; coapp-developers@lists.launchpad.net
Subject: Re: [Coapp-developers] Thinking abotu testing CoApp's tools.
On Wed, Apr 21, 2010 at 6:38 PM, Garrett Serack wrote:
> [recycling back to the list … make sure you use reply-all :
On Wed, Apr 21, 2010 at 6:38 PM, Garrett Serack wrote:
> [recycling back to the list … make sure you use reply-all :) ]
Might be a good idea to setup the list such that this is the default
(via reply-to header).
Olaf
___
Mailing list: https://launchpa
: Ritchie Annand [mailto:wakarima...@shaw.ca]
Sent: Wednesday, April 21, 2010 9:00 AM
To: Garrett Serack
Subject: Re: [Coapp-developers] Thinking abotu testing CoApp's tools.
Is the bellwether of success a working app or library out the other side? There
are probably test cases along those lin
I know this is early, but I'd like to get some ideas rolling around testing.
We're going to be writing a few different classes of software for CoApp:
(a)A collection of command line tools/libraries (+msbuild plugins) to
automate the tasks of adapting source code to Windows, and building pac
9 matches
Mail list logo
