Steve Kudlak wrote:
> Well I always liked to see if people could break something by using it.
> Better than a simple checklist. Probsbly why people like to Beta-Test.
But if a beta-test is your sole test routine, it's not going to test
thoroughly. It will miss obscure features, boundary condit
Julie wrote:
> From: <[EMAIL PROTECTED]>
> > My test plans tend to be big long checklists that developers hate. If
> > anyone's got a better way, PLEASE say so...
>
> Sounds a lot like my testplans ;-)
>
> My =designs=, on the other hand, everyone loves. Except for the
> people who review them
On Wed, Nov 22, 2000 at 11:06:47PM +, [EMAIL PROTECTED] wrote:
> > So, technical discussion #2: How do you deal with an immediate superior
> > who is a non-techie (especially when your pay is low, your top priority is
> > uni or other reasons why you don't want to be a defacto project manager)
On Tue, 21 Nov 2000, Laurel Fan wrote:
> So, how do you test well? What testing procedures and methodolgies
> should be used? And how can adequate coverage be ensured?
>
It's different from company to company. It's also different depending on
what your program is expected to do. It's also d
Mary Gardiner wrote:
> Well the project I'm thinking of is being completed by a group of uni
> students in a small business that has explicitly refused them written
> specs at all.
Take it to their lecturer/project coordinator. This is not a situation
uni students should have to deal with, it's
From: <[EMAIL PROTECTED]>
> My test plans tend to be big long checklists that developers hate. If
> anyone's got a better way, PLEASE say so...
Sounds a lot like my testplans ;-)
My =designs=, on the other hand, everyone loves. Except for the
people who review them because I write novels. Ditt
Laurel wrote:
Scenario: You are designing a test plan for a small to medium sized
(say, 5 core developers, 20,000 lines of code) open source/free
software project. All of your fellow developers recognize the wisdom
of testing, but some have no experience in more formal (meaning
'or
On Wed, Nov 22, 2000 at 06:36:02AM +, [EMAIL PROTECTED] wrote:
> Ah .. well, you see, if I've got the luxury of setting my own
> conditions, I'd say 'sorry, we signed off on a spec which didn't include
> that feature. It can go in the next release'.
>
> Of course, I have that luxury in every
Mary Gardiner wrote:
>
> The
> programmers are still feature-bloating (at management request) and hunting
> out old and new bugs.
Ah .. well, you see, if I've got the luxury of setting my own
conditions, I'd say 'sorry, we signed off on a spec which didn't include
that feature. It can go in the
Laurel Fan wrote:
>
> Excerpts from linuxchix: 21-Nov-100 [techtalk] Re: Technical is.. by
> [EMAIL PROTECTED]
> > And not just free of known bugs, but tested well.
>
> So, how do you test well? What testing procedures and methodolgies
> should be used? And how can adequate coverage be ensured
On Wed, Nov 22, 2000 at 09:09:53AM +1100, Mary Gardiner wrote:
> On Tue, Nov 21, 2000 at 01:25:38PM -0500, Laurel Fan wrote:
>
> >
> > What factors would you take into consideration, and what
> > would your plan look like?
>
> And where do you concentrate your energies?
>
> Do you subscribe to
On Tue, Nov 21, 2000 at 01:25:38PM -0500, Laurel Fan wrote:
>
> What factors would you take into consideration, and what
> would your plan look like?
And where do you concentrate your energies?
Do you subscribe to the 10% of the code == 90% of the bugs thing and look
in the areas where known b
Excerpts from linuxchix: 21-Nov-100 [techtalk] Re: Technical is.. by
[EMAIL PROTECTED]
> And not just free of known bugs, but tested well.
So, how do you test well? What testing procedures and methodolgies
should be used? And how can adequate coverage be ensured?
Scenario: You are designing a
Just to see what I can see
--
Steve - Cheltenham, UK
-
In love and light we are
In darkness we are no less
___
techtalk mailing list
[EMAIL PROTECTED]
http://www.linux.org.uk/mailman/listinfo/techtalk
Deb Richardson wrote:
>
> had a few notes that this list wasn't working (foo), so just trying to
> track down the problem.
This officially gets filed as a "works for me" bug :)
If anyone has any problems with any of the lists, please let me know...I
think I've ironed out all the wrinkles now.
had a few notes that this list wasn't working (foo), so just trying to
track down the problem.
- deb
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
___
techtalk mailing list
[EMAIL PROTECTED]
http://www.linux.org.uk/mailman/listinfo/techta
Tina Johnsson wrote:
>
> ...
>
>
> [EMAIL PROTECTED] http://www.linuxchix.org
It worked fine:)))
[EMAIL PROTECTED] http://www.linuxchix.org
...
[EMAIL PROTECTED] http://www.linuxchix.org
18 matches
Mail list logo
