Comment: Re:Variety Pack! (Score 1) 223
There's a "horizontal" distinction in testing, by colour: Black Box, grey box, and white box.
Black box is what the post above is doing - everything "under the hood" is not to be looked at, only the results. This is the easiest form of testing. It can be automated using scripts, if the UI's field order is stable. I like Black Box - you just get to "fuck shit up". My fave was to copy and paste the Unabomber manifesto into everything and watch the fireworks. Also, in the early stages, Black Box can have a lot of say in the design, because if the UI is crap, the black box tester will notice immediately - workflow is retarded, or there are too many clicks to a result, or similar issues. Also, Black box usualy entails running the daily build server, and doing a daily test of the build to see if it meets minimum criteria. If it doesn,t then the programmers are informed to not use that build and stick with the old one until it passes muster.
Grey Box is in between - you're looking at the code when you can, and you're developing test scenarios for scripting engines of other systems. For example: you need to test load balancing - so you need to know where in the code stuff goes in and out and how the server takes the data, processes it, and sends it out - that takes a bit of programming - the programmer can write that for you - and then it's your job to suss out what the results mean. Also, when something breaks, you need to find where in the code it's broken. How to fix it is not your job or problem - but you need to be able to say "this is where it divides by zero and causes the computer to puke blood".
White Box is where you're managing low level testing of each software component (after the programmer runs it to see if it works at all) and if it doesn't work, you need to be able to flag it properly and send it back saying "it broke here because" kind of stuff. I find white box even more stressful and difficult than actual programming. You have to be a "programmer's programmer". Pain inth e ass, and rarely worth the money or hassle.
I like doing black box testing. It's a blast. I love to just fuck shit up. It's a trip. It's a bit like doing detective work. Grey Box is more intense, but can also be fun, dpending on the app you're testing and the team you're with. IF they hired by the "No Asshole Rule" then grey box can be rewarding - it pays better than black box and it often includes a lot of black box.
That's how it was when I left software dev in 2005. From what I gather it hasn't changed that much - it's more automated than before, but only after the app is mature enough to withstand it.