1. Testers: An Integral Part of the DevOps Team
Even though DevOps doesn’t incorporate the “testing” aspect into its name, software testing should be embedded throughout the development process. Author Renato Quedas explains the lack of “testing” in the name DevOps: “because DevOps implies that testing is a part of development.”
Oftentimes, however, companies fail to embed testers into the development teams. There are several excuses for doing so, few of which are acceptable. Ultimately, DevOps organizations can only innovate, “as fast as the testing practices can move, while still minimizing the risk of any build moving into production.”
Read on in this StickyMinds article to learn why Quedas believes testing should be the heartbeat of any DevOps organization.
2. What Value Do Testers Provide to Software
Obviously, testers are a valuable asset to software development projects. They are in charge of testing and evaluating code in order to deliver a well-performing, quality application. But as a result of the growing number of devices and apps that testers have to handle, should the role change?
Not so much, according to Jason Arbon, the CEO of AppDiff.com. He asserts that testing isn’t about the platform. So how then, does one quantify quality? Check out this article from TechWell author Josiah Renaudin in which he highlights Arbon’s opinions on how testers can truly add value to software.
3. Types of Non-functional Software Testing
Performance. Performance. Performance. We couldn’t emphasize its importance enough, especially when it comes to web and mobile applications. While functional testing ensures that each function of the app operates in conformance with the requirement specification, non-functional testing is designed to validate the app’s performance requirements.
There are hundreds of different types of testing, but in this D Zone article, author Premal Dave chooses to explore nine including load testing, stress testing, volume testing, scalability testing and more! Read on here for a closer look at the types of non-functional testing you should be executing within your organization.
4. Discussion: Who is a tester in an Agile team?
Since the introduction of Agile development methods, the software testing role has taken on some fluidity. No longer pushed off until the end of the development lifecycle, testing has, and must be, infused throughout the Agile process in order to continuously validate application performance.
Every team member is responsible for the quality of software delivered. Does that make everyone a tester? A poster to the Software Quality Assurance & Testing Forum would like to know:
“In an Agile world, would you consider all of the team members testers? Are they part of defining the quality of the software? How can a team member be a good agile tester in your mind? What are the qualities you are looking for a tester in an Agile world?”
What are your thoughts? Contribute them to the discussion here!