Skip to main content

Posts

Showing posts from April, 2013

Lets compromise....

Compromise. That word doesn't sit well with me, its not a natural state of mind. The further I progress in my testing career I find it around every corner:

'Lets compromise on quality to hit the date.'
'Lets compromise on testing depth so we can increase our coverage.'
'Lets just do a smoke test, it'll be fine.'

I often think that compromising in testing is seen as the grown up thing to do:

'Its your product buddy, I'm just an information giver. Go or no go, no skin off my nose. I'm just a tester.'

Its also a little naive in a way. The customer says:

'Yes lets cut down the testing so I have my stuff when I want it.'
When they actually mean:

'Yes lets cut down the testing so I have my stuff when I want it. Oh and make sure it works perfectly too.'

Thing is, I'm not just a tester. I'm a fierce (some would argue too fierce) believer in testing as craft, who leverages business facing, technical, exploratory, automatio…

The testing marathon...

The world may or may not know that I'll be running the London Marathon next week. During my long hours pounding the streets to be ready for the marathon itself I've reflected on a few ways my training has reflected my testing journey:

Push yourself a little bit further over time - you can only prepare your body for a marathon in one way, and that's very gradually. I believe this can be applied to your mind too, specifically how you develop yourself as a tester. Acknowledge that you will not reinvent yourself overnight, pick a development path and review regularly to check progress and verify you are on the right path.

Find a sustainable pace - a marathon is made more difficult if executed at an ever changing pace. The same can be said for testing. If your testing does not flow, your execution of testing as a craft will not be as effective as it could be. Testing in small chunks, incrementally and continuously is the aim.

Do hard yards - there have been a few times I haven&#…

Flat file creator in Groovy for SoapUI

Quick code share for creating flat files in SoapUI via Groovy.

I used this to create a linearly increasing file size for an extract, transform and load tool to do some basic load testing.

SoapUI is great for this kind of thing, nice and simple IDE, with the ability to extend to use pretty much any jar you can think of. Enjoy!

/*This script will create a new flat file with number of records taken from a test case level property:
* Steps:
* 1.Create the basics for use throughout the file. Primarily dates and account numbers
* 2.Create the relevant filename
* 3.Create the header
* 4.Create the body of records with amended account numbers
* 5.Add a footer
* 6.Output the lot to a separate file, its size configurable by test case property.
*/

import java.util.*;
import org.apache.commons.lang.RandomStringUtils;

//Create the static bits to be used
def number_Records = context.expand( '${#testcase#Number_Records}' ).toInteger();