Automating regression testing

One of the things that has been a concern of mine for a long time is how to go about automating regression testing of workflows, templates, and such. I've just never gotten around to doing anything about it. It seems like with 6.x, more stuff is directly exposed as action urls, so in theory, it should be a lot easier to build a generic framework for automated tests. Has anyone out there put any thought into this?

Find more posts tagged with

Comments

Dwayne

I would think it would still be pretty difficult to pull off. The workflow instantiation pages and the data capture pages aren't directly exposed, as far as I know. So you're still having to use some sort of "user similulator" software (Winrunner, etc) to automate the processing of the forms. Once the workflows and DCRs have been created, you could probably automate the rest of the testing, however (transitioning tasks, page generation, etc).

If you get it working, you might want to see if Interwoven wants to lease it from you.

Current project: TS 5.5.2/6.1 W2K

nipper

run it once. if it works it is tested.

Any problems are user error

Any questions ?

Migrateduser

That's been the main thing that has held me back from doing any serious work on it. A couple of years back I had some downtime and started working on a local proxy server written in perl to intercept the calls and cache the responses. Since, with the exception of launchpad, it's a completely web driven app, one should be able to do a basic level of user recording that way and then asemble it into some sort of a framework to make calls and substitute different types of data. Unfortunately, I got downsized before I got to play with it too much.

Now someone else has gone and built a proxy like I was messing around with. It's called HTTP::Recorder

http://www.perl.com/pub/a/2004/06/04/recorder.html

I'm thinking this is more easily doable now than it was a couple years back.

Dwayne

That would probably work for regression testing between minor releases, but I doubt that it would carry through to a major release change. The odds that the data going over the pipe would remain that consistent between major releases is fairly slim, I would think

--

Current project: TS 5.5.2/6.1 W2K

Migrateduser

Correct - but I'm not concerned about regression testing in order to move from one release of IWOV to another. What I care about is being able to run a regression against one's own codebase of templates, workflow, etc. It's also a handy thing to have in order to test performance impact, if you can simulate a userload on a test server.

Dwayne

Sorry. I misunderstood. There was another thread that talked about changes to TeamSite breaking custom-developed code, and I so I had that set in my mind.

Given your requirement, it sounds like your solution might be workable. Good luck!

--

Current project: TS 5.5.2/6.1 W2K

Migrateduser

It's an understandable misunderstanding. It was actually that thread that got me to thinking about it again.