As the Agile environment has efficient principles that allow quick responses to changes and the ability to deal with uncertainty, exploratory testing may seem like a perfect match for such projects. However, this is only partially true. In reality, diverse reasons impede its usage in Agile projects, and companies should take them into account before designing QA strategies.
DevOps does speed up your processes and make them more efficient, but companies must focus on quality as well as speed. QA should not live outside the DevOps environment; it should be a fundamental part. If your DevOps ambitions have started with only the development and operations teams, it’s not too late to loop in testing. You must integrate QA into the lifecycle in order to truly achieve DevOps benefits.
Faster DevOps processes also create new challenges. It was difficult enough to add security into a traditional waterfall software development lifecycle with monthly or quarterly releases, but now software updates are released several times a day! What can developers do to build and maintain more secure applications? Here are some ways to encourage better security practices throughout the DevOps lifecycle.
The concept of accessibility has been around for more than twenty years, yet it’s only recently that more companies have started including it in their development efforts. Developers and testers are recognizing the advantages of incorporating accessibility techniques into their processes. Here are some of these methods specific to agile software development, including a handy checklist.
QA testers often take on more of a role than just testing software code. When the team needs help, QA should lend a hand in assisting with business analysis, customer communication, user experience, and user advocacy.
The internet of things (IoT) continues to proliferate as connected smart devices become critical for individuals and businesses. Even with test automation, performing comprehensive testing can be quite a challenge.
John McConda, principal consultant at Mozer Consulting, discusses his workshop designed to aid testers who work in a regulated environment to implement agile and automated testing. He talks about how those who work in businesses that are regulated by federal agencies, the Sarbanes-Oxley Act, and other compliance requirements can still work within those rigid specifications to introduce agile and automated processes.
Technologist and evangelist Peter Varhol and Gerie Owens, a test architect and certified ScrumMaster, discuss their STARWEST presentation, “What Aircrews Can Teach Testers about Testing.” They talk about how testers can apply airline safety practices to their teams’ delivery of high-quality applications through complementary expertise, collaboration, and decision-making. They also explain how blind deference to authority and automation can be detrimental to a testing team, and how to use everyone’s skills to achieve success.
In this interview, Mary Thorn of Ipreo explains how to get the most out of your team's test automation strategy. She explains why you need to implement automation, the balance between manual and automated testing, and what to do when a team's automation completely lacks a strategy.
In this interview, TechWell speaks with Wim Demey, a solution architect working for CTG Belgium. At STARWEST, he gave a presentation titled "Take Your Test Center of Excellence to the Next Level with ITIL."
API testing can be challenging—especially for the uninitiated. Ever wonder what makes an API test great? Patrick Poulin will arm you with an understanding of the benefits of automating API testing over doing it manually.