Technology - thinking about getting back into it
 

About nine years ago, I was heavily involved in software testing, known in some circles as Quality Assurance testing. At the time, I wrote and conducted test cases as well as used automated testing software such as WinRunner.

I see that there are quite a few open positions in QA testing these days, and on a personal front, would not mind taking a look back into that field.

But then again, I've been about nine years out of the loop for me. While I'm certain I can still manually write and execute test cases, I'm not up to speed with the new testing software. Secondly, because I performed my QA work during the dot.com boom, many of the companies for whom I worked are no longer in existence. That equates to a big Zero on any resume I write showcasing my experience.

So I'm wondering if the tech people on the board have any suggestions. It was definitely something I enjoyed at the time.

Thanks for the help.

dd SmileWavy

QA (at least in my area, which is web-based financial services) is heavily dependent on automated test suites, so aptitude there is important... I don't really know anything about WinRunner per se, we use Mercury LoadRunner in my MS shop. My personal opinion is that the best QA folks I know have a mindset and a background that allows them to anticipate where the code might fall short or where problems are likely to arise. Although the technologies have changed since the dotcom era, if you had chops back then you probably will have chops now.

What kind of work are you doing currently, and is it applicable to QA?

I'd recommend writing a good cover letter explaining what you said above. If you can throw out the correct buzzwords to get an interview you'll have your chance to shine. It will be quite evident whether or not you know your stuff. Since QA is process driven, those processes matter more than specific testing software. Remember, monkeys can be trained to push buttons. ;) BTW, I always appreciate QA folks who can think outside the box and think like the customer. Too many times test plans are put into place by Development....whom have a vested interest in stuff passing QA.

Nothing wrong with a resume listing dead companies, it happens all the time.

Thanks, guys.

Yes, I have a page full of dead companies and pissed off venture capitalists.

BTW, I've done website testing, too.

WinRunner, Load Runner - I have experience with both software.

Were you mainly working in the Linux or Windoze side when you were testing?

Windows, and some Mac OS.

I’m a developer in the MS .NET / MS C++ suite of tools. I may get slammed for saying this, but
corporate America (if your looking in that arena) runs on the .NET Team Foundation servers and tools now
days.

It has integrated QA’ing stuff built in it right out of the box which makes it kinda nice as you have only one
QA tool to learn instead of the plethora of QA tools on the market right now.

There are plenty of books published on using the TF QA tools, might be a good start?

Learning C#, .NET and some TSQL wouldn't hurt. .

TF Overview:

http://msdn.microsoft.com/en-us/library/ms242904(VS.80).aspx

Whoa! I'm feeling the learning curve.

Maybe I'll cover both bases - TF and the Mercury suite. Hopefully Mercury has a demo download available.

Thanks, fellas. :cool:

Welcome to the 100 hour work week. SmileWavy

100 hours a week only?? Man you have a kickback job! ;)

I'm alright 99.5 hrs. a week. But jeez, what about bathroom breaks? :D

I think you're right, it was more when I worked for IBM.

Some of use Java on Unix for the presentation layer and COBOL/C/Other Languages for the backend/batch/data retrieval. I know we use some automation tool for test scripting, but I'm not aware what as I work in a specialized language that doesn't have any automation tools available for it.