Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

Re: Quality, Developers and Testers: Organisational Issues

by dragonchild (Archbishop)
on Jun 11, 2005 at 18:26 UTC ( #465828=note: print w/replies, xml ) Need Help??


in reply to Quality, Developers and Testers: Organisational Issues

Effective use of testers (and any other development resource) is only possible when you have a clear-cut process. The process is the important thing; without it, you have cowboys with keyboards doing whatever the last manager who spoke to them said to do.

There are many, many ways to go about setting up a good testing strategy. These are the things I feel are common to them all:

  • A tester has veto over a developer. If the tester says it fails, no-one can override him/her. Period.
  • A tester has veto over a designer. If the tester says the design is untestable, no-one can override him/her. Period.
  • Developers should write unit tests. Testers should write system tests.
  • As many tests as possible should be automated. Ideally, the entire application is smoke-tested within 15 minutes of any checkin, with the whole team being notified of any test failures.

Beyond that ... I prefer a test-first, code-later approach, but that's because of where and how I work. Other companies prefer to have a design-code-test-recode-retest methodology, and it must work for them because they're still in business. *shrugs* YMMV.


  • In general, if you think something isn't in Perl, try it out, because it usually is. :-)
  • "What is the sound of Perl? Is it not the sound of a wall that people have stopped banging their heads against?"
  • Comment on Re: Quality, Developers and Testers: Organisational Issues

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://465828]
help
Chatterbox?
[Corion]: Nicholas Clark++ # read for a multichar block-delimiter by scanning for the last char, and only then check whether the whole delimiter was read.
[Corion]: At least if you're appending the data read to a larger buffer, this means you avoid the situation of "a delimiter was found but the other half has not been read yet"
choroba misses the context
[Corion]: choroba: Optimizing how Perl reads source code on startup (and then processes it line-by-line)
[Corion]: But in general, it seems to be an interesting approach I should think about - whenever I'm searching for something, to consider if I could search for the end of the token instead of the start of the token

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (12)
As of 2016-12-06 15:00 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    On a regular basis, I'm most likely to spy upon:













    Results (107 votes). Check out past polls.