The future of software testing

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software testing and quality assurance (QA) fundamentals Software Testing: New software testing technologies bring new challenges Testing strategies for complex environments Astronaut's STPCon advice: Teamwork delivers "The Right Stuff" How to make your software tamperproof Software consortium seeks standard quality metrics Demo: Using WebGoat, a free software testing tool Seven steps for a quality change and configuration management program Winning responses to "Why is QA always the bottleneck?" Where to find good methodology guides for software testing 5 ways to answer executives' unfair software test, QA questions Advice from Mike Kelly Integration testing: Is it black box or white box testing? Test strategy document vs. an acceptance test plan An approach to integration testing Choosing code coverage tools Performance testing and experimental design How to test software with dynamic requirements Test metrics and use case coverage during testing How to learn white box testing How to determine test coverage How testers can practice bug advocacy with developers Software Testing and Quality Assurance Why do performance testers write new scripts so often? How to create performance testing workload models Fixing Web application performance troubleshooting problems Expert advises on implementation of Selenium IDE for effective software testing When should regression testing occur in an automated test plan? Achieving peak performance in integration testing Getting answers about OpenSTA script problems Defining core software regression tests Breaking in functionality on UI application pages Where to find good methodology guides for software testing

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary build  (SearchSoftwareQuality.com) code review  (SearchSoftwareQuality.com) conformance testing  (SearchSoftwareQuality.com) error handling  (SearchSoftwareQuality.com) garbage in, garbage out  (SearchSoftwareQuality.com) load testing  (SearchSoftwareQuality.com) NUnit  (SearchSoftwareQuality.com) quality assurance  (SearchSoftwareQuality.com) stress testing  (SearchSoftwareQuality.com) white box  (SearchSoftwareQuality.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

I believe there will always be a place for skilled software testers who are passionate about their craft.

I'm sorry to hear you've been laid off. That's never good news, even if it does give you an opportunity to pursue other career paths. Off the top of my head exposure to Unix and SQL and experience with the HP Mercury suite of tools are all good things to have for a tester. Many companies utilize the HP Mercury tools, and while knowing those tools probably won't do anything for you once you have a couple years of experience, they may be just the boost you need to get a foot in the door with someone looking for entry-level testing help.

That said, I suspect your experience as a business analyst will be even more important. Make sure you highlight that during your job search. Testers use may of the same analytical skills that business analysts use, and a knowledge of the domain is always helpful. For some other ideas on learning software testing, look at a similar post I did on "Expanding software testing skills."

As for your concern about software testing jobs going offshore, certainly off-shoring is a trend in our industry that's going to continue. I have no doubt about it. However, I believe there will always be a place for skilled software testers who are passionate about their craft. And as a hiring manager who is always looking for bright entry-level talent, there is a real shortage of skilled testers at the local level (at least there is at my local level).

I've worked for several companies that have utilized offshore testing services, and all of them retained a large contingent of local testing resources. They all viewed utilizing offshore resources as one way to look at either lowering the total cost of testing or enabling them to do testing they couldn't otherwise practically do (for example, testing 24 hours a day). When I've looked at outsourcing, it's been because I couldn't find the resources locally.

Some of the best advice I've heard on the topic can be found in a post I did in 2005 on a panel discussion I hosted for the Indianapolis Quality Assurance Association. It's a little dated, but I think it's relevant because in the discussion the topics of Mercury Interactive tools, education, and off-shoring all came up. The panel experts know more about these topics than I do, so I'd trust their advice. Good luck in your search!