It’s graduation season, and with that comes a whole new wave of aspiring software testers who are ready to make their mark. The world these graduates are entering into, however, is significantly different than the one graduates of, say, the late ‘90s entered into. Testing methods back then were highly process-oriented and black box-focused, with no automation.
Do you have a process in place to properly prioritize tests and tasks?
On any given software development project, there is so much ground for software testers to cover. With the added burden of looming release deadlines, software testers may feel bogged down with too much work and too little time. This is why it has never been more important for QA teams to efficiently prioritize tests and tasks.
This article outlines ways in which your organization can do so, starting first with identifying which aspects of your application pose the greatest threat to its performance. Take a look.
Today, the US Neotys Team will arrive in France to celebrate the company’s 10 year anniversary. I can’t speak for the rest of my colleagues, but my French skills are pretty much non-existent. I’m sure it will be incredibly overwhelming to be surrounded by people I can’t understand, but it’s not like I’m going to turn down a trip to France!
A language barrier is a daunting thing, whether you’re venturing into a new country or even a new software testing project. If you’re ever handed a testing assignment that includes testing a web or mobile app in a language you don’t understand, fear not! Author Brian Noggle has had to do this several times and in this write-up, he explains a few different ways you can effectively test without fluency. Read more…
Where do you believe a somewhat traditional tester might fit into an Extreme Programming environment or development cycle?
“I’ve been a QA in an agile environment before, but I’ve now found myself at a company that practices Extreme Programming to the T. I was wondering where you guys think that a somewhat traditional tester might fit into such an environment or development cycle. In particular, all of the devs here are iterating with TDD and writing their own automated tests and pushing to their CI as soon as they are done.”
This poster to the Software Quality Assurance and Testing forum asks anyone with resources and/or experience with a similar situation to respond here.