From D to Q to C with plenty of T

2006-Jun-28 - Behavioural Databases

Posted in Testing

Not only can databases store stuff but the way people use them - or not - can be instructive.

 

The programmers on the latest project for example. They intend to just use the one.

So how are they going to test how their application behaves when it's misconfigured and there's 0 of the things they are expecting ? Or how the interface looks when there's many many items to be displayed ?

Does it behave correctly when there's just one option and the use doesn't have a choice to make ? How will they check their errors that are meant to appear when a user gets halfway along the path and finds they can't go any further as there's no data to populate the next screen ?

Or are they just intending to pass it over to the testers and tell them that it works fine when everything is happy happy ?

 

 

As part of my coding duties I'm still responsible for a program that configures a system. I had to make a small enhancement that meant adding two more fields to a table in the database and changing a dialog so it could read and write to these new fields

Made the program and passed it over to our 'tester'

 

Waited for him to ask me which database fields the enhancement used...

 

and waited...

 

No request for information arrived.

 

So I knew he wasn't looking in the database to see if the program was writing to the correct fields, he was just checking that the program was consistent with itself. If I'd made a mistake and was writing the Max value to the minimum field and the Min value to the maximum field then as long as I made the same mistake in reading the values then the program would appear to work.

Until the program that uses this data comes along and tries to use it...

 

 

I had a constructive afternoon writing a number of SQL scripts that would populate a database with one, two or many values. Mix the scripts up and I could have a large variety of differently configured systems very easily and be all set to test.

 

Now that is a sign that things are improving here - having control of the data we are testing with and not just using any old customer database that happens to be lying around and could be full of any old cr8p


2006-Jul-4 - Please don't take my suggestion the wrong way

Posted by metalbaby
Hey Phil,

Maybe if there is something specific that you think the tester should be testing then you could give him a heads up. Let him know that you expect there could be issues relating to new fields in the database and give him the details. Maybe Mr TabOrder just never thought about that. I am not defending him, but maybe you could show him that he is not doing his job properly and he might improve or run away scared and hide in a big hole in the ground. Probably to read his paper.

That might also give you more artillery if you want to try to oust him. If you are providing him with relevant testing information and he doesn't bother using it then it is another cross against his name and a gold star for you. I really appreciate it when the devs point me in the right direction. They don't always do it, but sometimes they do.

Just my 2 yen.

Chris
Permanent Link

<- Last PageNext Page ->

About Me

A developer breaking into the QA world - now broken into it and entering the world of test consultancy

Friends

neillmccarthy
testmanager
studley
csbdeady
ovidiu
strazzerj
jpweston
metalbaby
thepthial
EklecticTester
michaeljf
PeteNairn
jimtest
spikyone

Syndication

RSS Site Feed