 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Scout
Guest
|
 Posted: Tue Jul 27, 2004 9:39 am Post subject: QA: how to find people |
 |
|
Hi,
Any ideas on how to find folks who are good at providing realistic QA
tests?
We already have a number of people working at QA in our shop, but most
of them don't have the faintest idea of how to check for memory leaks or
long-running transactions.
While most QA work is related to "does this actually work?" in all
sorts of weird situations, I still like the idea of having a QA person
who knows what the software is doing to the computer in abstract terms.
We have one guy who is sufficiently skilled to be able to look at the
Header Page of an Interbase (or Firebird) Database and make some sense
of it, and to run a memory profiler. He's really young, and I only
hired him 'coz he was mates with my boy.
The other testers seem to have no idea.
Any strategies better than hiring your kid's friends welcomed.
Scout
|
|
| Back to top |
|
 |
Erik Springelkamp
Guest
|
| Posted: Tue Jul 27, 2004 10:16 am Post subject: Re: QA: how to find people |
|
|
Scout wrote:
| Quote: | Hi,
Any ideas on how to find folks who are good at providing realistic
QA tests?
|
To start with, you should think about the structure of your testing
procedures.
There are technical tests to be done by the programmers.
They should be structured, and should be filed in an organised manner.
There are functional tests, which require documentation on how the
programs should function.
This can be done by people without much technical knowledge, but they
need to be methodical and logical, and a bit curious.
Then you can do stress-testing and endurance testing, which will
probably best set up in a cooperation of software engineers,
administrators and testers.
| Quote: | We already have a number of people working at QA in our shop, but
most of them don't have the faintest idea of how to check for memory
leaks or long-running transactions.
|
These errors should appear during the stress/endurance-tests, or even
better, already in the early technical tests.
They do not typically show up during functional testing.
| Quote: | While most QA work is related to "does this actually work?" in all
sorts of weird situations, I still like the idea of having a QA
person who knows what the software is doing to the computer in
abstract terms.
|
The test-group should have at least one technically skilled
'administrator', who can deploy applications, handle the versioning,
administer databases.
| Quote: | We have one guy who is sufficiently skilled to be able to look at
the Header Page of an Interbase (or Firebird) Database and make some
sense of it, and to run a memory profiler. He's really young, and I
only hired him 'coz he was mates with my boy.
The other testers seem to have no idea.
Any strategies better than hiring your kid's friends welcomed.
|
Good testing is expensive.
Ideally you have some engineers who like testing, but have the
technical skills of a programmer.
Here in the Netherlands there are lots of shops specialised in testing,
but their personnel is as expensive as programmers are.
--
Erik Springelkamp
http://springelkamp.nl/
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
