One of the
accumulations that happens to testers over time is the build up of a staggering
array of test files. Files that use
"odd" characters in Japanese, a Finnish test script, an absolutely huge Excel file, etc… I tend to keep any file that ever exposed a
bug around, use it in automation and use it for ad hoc testing as time goes by.
I also have one very
simple file that I use quite often. Very
basic, but very good for "smoke testing" : simply ensuring a new
feature doesn't crash right out of the gate.
It's just a csv file
with some simple numbers and text in it:
x
|
y
|
z
|
name
|
2
|
-1
|
4
|
ant
|
4
|
0
|
-2
|
bat
|
6
|
3.1
|
1.5
|
cat
|
-1
|
0.2
|
3
|
dog
|
Super basic, but
fast to load. It also has a mix of
integers and floating point numbers, named columns, some text values and
multiple rows of data. I use it at least
a half dozen times per week and I wanted to share this since it makes a good
point that sometimes a simple test case is enough to provide some value. If my test - whatever it is - fails with this
file, I know I am blocked and I can file a bug and move on.
And if it passes,
then I know I can start to dive further into the test matrix I have. There's no guarantee that any of those other
tests will pass. But since I love
analogies, I see it like this.
This simple test
matrix is the equivalent of starting a car.
If it fails, I know I won't be testing the brakes or driving on the
highway. But just because the car starts
I still can't tell if it will work when put in gear. But at least I know the basic test - the
engine works, in this analogy - is passing.
Questions, comments,
concerns and criticisms always welcome,
John
No comments:
Post a Comment