Related Content
2 Quick Wins for Building Context in Testing Testers fill in their assumptions about the project, domain, and technology with things they learn while testing and while talking with people. Sometimes the information they learn is good, but sometimes they miss something important. Here are two quick wins for filling in those assumptions with good information. |
||
6 Steps to Achieve Realistic, Reliable Load Testing Simulating real users’ behavior gives you a transparent picture of your software's load capabilities. To reproduce users' actions accurately, you can use a request flow design from when the system is in the production environment. Here are six steps for achieving the most realistic load for your load testing process. |
||
The AI Testing Singularity Machine learning is rapidly growing more powerful, already sometimes imitating the actions and judgments of humans better than humans. In the near future, even before machines are conscious, they will be able to mimic human software testers. What will be the impact of AI on testing? Jason Arbon has a bunch of ideas. |
||
Leveraging Kubernetes as a Tester Kubernetes is a scalable, production-grade container orchestration tool with automated deployment, scaling, and management capabilities. Using it shortens the feedback loop and enhances communication. Here’s how testers can leverage Kubernetes to quickly gauge application quality and speed up the delivery of value. |
||
The What, Who, and How of Developing a Test Strategy In the world of agile, people often think of test strategy documents as outdated or unnecessary. But having a defined plan of action for how you're going to test a system, application, or business function is always useful. Here's how to break that down into what, who, and how so you can understand your tests' purpose. |
||
Making the Switch from Quality Assurance to Quality Engineering The quality engineering approach differs from QA in that quality teams partner with business users and product managers to better understand requirements and to catch problems as products are being built—not after the fact. There are two pillars to building a true quality engineering organization: culture and process. |
||
Robotic Process Automation in Software Testing Robotic process automation (RPA) systems develop a list of actions to automate a task by watching a user perform that task in the application's GUI, and then repeating those tasks directly in the GUI. But RPA tools differ from other tools because they can handle data among multiple applications—including for testing. |
||
The Developer’s Role in Testing and Quality Of course a developer's primary job is to produce good code, but there's also a lot they can do to contribute to quality and test their code before it gets to a tester. Code quality techniques help developers write better code, more thoroughly understand their changes, and avoid builds with many easy-to-find problems. |