A while ago I answered the following question on SearchSoftwareQuality.com’s Ask The Software Quality Expert: Questions & Answers.

The development team is adding new features to an existing piece of software, and it is causing a lot of regression issues due to the addition of features while testing. As a tester (black box), what advice can I give to the development team so that the software is of good quality and released on time and within budget down the line?

Here is a clip from my answer:

As a tester, you should be able to carry some "street cred" when it comes to testing. So I'd recommend starting there. Try talking about the unit testing taking place. Talk about testability features you think may help the team with developing regression tests or that may help cut regression test cycle time in some other way. Look for projects that you could work on with the developers to help solve testing problems.

In the past, I've paired with programmers to extend unit tests they've already written. I've also had them pair with me to try to get some difficult test automation working. And I've sat down with them to design testability features like tools for data management, increased logging or alternative interfaces.

After testing, focus on design and the design process the team is following when they make their changes. As a tester, it's reasonable for you to ask to be involved there. You need to know for your testing, and most likely it's a place where you can contribute by asking questions and raising concerns. (Just don't become the tester who cried wolf.) Who's involved in designing the solutions? What peer reviews are they doing? Do they consult existing design artifacts and code or make assumptions?

You can find the full posting here.

A while ago I answered the following question on SearchSoftwareQuality.com’s Ask The Software Quality Expert: Questions & Answers.

My question is regarding education and training to develop a career in software quality and testing.

I have done some (very) minor testing on the V&V team for a client company where I was working as a tech support contractor. When I got a sampling of what QA was like, specifically testing, I was hooked.

What resources, short of investing thousands of dollars in school, can a junior SW tester use to garner some knowledge so that doors in the field are opened? I think a career in quality and testing would be great, and my particular interest resides in automation of testing process. I've done some scripting and coding, but would not consider myself a full-blown programmer.

Any advice on where to begin? And once having started down the path, what are the best options for continuing and furthering education and training?

Here is a clip from my answer:

Finally, and most importantly, find the time to practice. Each time you practice testing, you should be interested in doing some specific thing better. By improving one specific technique at a time, you gradually improve your overall ability over time. If you keep reading his tutorial on Self Education for Testers, James Bach offers more suggestions on ways to practice and techniques for rapid learning. You can also take a look at an article I wrote on practicing software testing where I recommended several ways to log some time honing your testing skills.

Longer term investments would include picking up a couple of books including Lessons Learned in Software Testing , any of the books from the How to Break Software series. Currently, I really like the Stealing the Network series for its ability to show actual problem-solving examples. I also recommend you keep working on your scripting and coding skills. This will help you not only in understanding the technology behind what you're testing, but it will be essential for effective automation and will allow you to branch into performance testing later in your career.

You can find the full posting here.