QASource sponsors The East Bay Agilistry & QA Meetup Group. The goal of the meetup group is to create a community where software engineers and developers can meet once a month to learn new skills, build on current skill sets as well as network with other business professionals.
Though QA is very closely linked to programming and software development, it is a separate industry with its own distinct culture and thought leaders. There are plenty of online resources for expanding your testing skills, but where does one turn for more candid, personal perspectives from within the QA world? The blogosphere, of course!
Whether you’re a Director of QA trying to keep up with the latest testing trends or a budding test engineer looking for relevant leisure reading, this list of QA blogs will keep you occupied and informed.
For product companies, there’s never been a better time to be in the market for QA. Similarly, there’s never been a better time to be a QA engineer. Companies are releasing high-value products that shape the way users engage with the world, and they need high-caliber testing to protect customer experience, stakeholders and their market share.
When your QA team is in-house, you’ve got several things going for you. First, the team is already familiar with the product and the company culture. Second, communication between the dev and QA teams is simple -- a test engineer just walks down the hall to find a developer, and vice versa. Though these are undeniably valuable benefits of having QA under the same roof as dev, experienced testing partners help bridge the gap between onsite and outsourced teams with a project kick-off meeting and several important QA processes.
Agile processes have been adopted by most software testing companies to keep up with rapid release schedules and customer demand. Gone are the days of slow but big results under the waterfall model -- Agile requires dev and testing teams to work hand-in-hand to produce fresh, fast results on a weekly basis.
There’s no way that this approach is working without a significant of automated testing in place, so let’s make that first on the list.
To match the pace of an ever-expanding market, many organizations are transitioning to the Agile method for project management. The same is true within the QA industry, and at QASource we've become quick experts of Agile processes. What separates the Agile approach from other methods of working, such as the Waterfall model? Agile is defined by collaboration, iteration, and rapid and repeatable delivery schedules. Adopting these new processes can be challenging at first, so in this blog post, we'll be reviewing a few helpful tips for getting your QA team up to speed.
Agile QA methodology was developed to help engineers meet deadlines, reduce documentation time, and reduce release cycle time. It enables QA engineers to deliver high business value in the shortest time possible, effectively resolving these issues. But with a new approach comes a new set of challenges. As you transition to the Agile method, your QA team will have to assimilate an entirely new work culture and adapt to a new set of tools.