Hello world!

and so it begins…

This will be the development diary for all things Automation Solutions – I have much to do just to make it look like my site. I’ll be making images and picking themes

Then we’ll have some posts

For example: I have 2 projects in mind – the Loadrunner batch scheduler (multi-version), the Execution scheduler (which is just a booking system with a fancy name) and there will also be snippets of code in multiple languages as I get up to speed in perl, ruby, java et al.



And then there were 2…

I’ve just been asked by my boss to build a proof of concept for a scheduling system, not to execute performance tests but to book time slots on the shared controller.
It’s not unusual that a controller would be shared by a number of testers, very few projects require and use 24.7 access to Loadrunner, most scripting is done on an independent machine (VUGen can be installed and run independantly of the Controller) and there are often multiple workstreams.

Now I’ve worked in a million different places, and I’ve seen some booking solutions over the years and it is my opinion that most automated testers can’t be doing with them, they’re clunky, slow to complete and just another layer of irritating bureacracy. Mine will no doubt be the same.

Looking at 2 possibilities off the top of my head:
1. Spreadsheet on a shared drive. This has the advantage of being simple to build, but sharing requires opening and closing the document to prevent locking, and there’s usually one hog in my experience.
2. Online booking system with a php-based calendar and a webform tied into a mysql database at the back-end. I can build that with resources acquired on the net and customise to fit but it will still take longer than the spreadsheet.

As a POC-request, I’ll end up doing both and asking the testers which they prefer, and the answer will almost certainly be “Neither, can’t we just get together and figure out who needs it when they need it.”
Yes, yes we can. Over a beer?

IT doesn’t rain but it pours…

Further to my last post, on the vague subject of a test run database and results repository. There are, of course, additional features to add to that. Especially if you wanted to provide it to clients at a cost.

It would need to be able to cross-match results on the fly, comparing like-for-like transactions/scripts/scenarios.

I’m not proposing to re-develop the analysis tool for loadrunner, that’s outside my scope at the moment (probably 😉 )
But something comparing Run A vs Run B of the same test in pure numerical terms sounds like a job for perl to me.
And yeah, maybe have it draw a graph, pretty sure that’s do-able on the fly.

So Working, Building and Researching. What’s new?

So what have you been doing?

It’s been a long time since I had the time and inclination to update the site. Partly because I’ve been busy working and partly because I was hideously aware that the next stage for the site was complicated and not exactly in my wheelhouse. I can code, clearly, since I automate everything and work as an automation expert internationally. But I’m not a business analyst, a technical architect, a data analyst or a developer. Not really, at least.

Continue reading