Related Content
 |
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. |
|
 |
NSA Adds to Open Source Tools and Tech Transfer Program The National Security Agency recently released several of the agency’s software tools as open source and added new technologies to the NSA technology transfer program patent portfolio that are ready for licensing. Could leveraging any of these technologies help your efforts? |
|
 |
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. |
|
 |
Integrating Threat Modeling into Agile Development Threat modeling helps you determine where to focus your security testing efforts when building your app. But people often wonder how it can fit into their existing agile software development process. Here are three things you can do to integrate threat modeling into your agile workflow, either early on or mid-project. |
|
 |
The Good, the Practical, and the Expedient When a process isn't working, you'll have to make a choice that will help move things along. However, some choices are less about inspecting and adapting than about getting things done quickly, and that incurs risk. To manage this risk you need to be aware of the differences between "practical" and "expedient." |
|
 |
Merging New Codeless Test Automation with Your Existing Code-Based Test Scripts Adopting a codeless solution can be an amazing boost to quality, productivity, and tester career growth, but in most organizations, such test suites will have to be merged into existing code-based test scripts. To succeed, developers, testers, and management all should consider the differences between the two options. |
