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.

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 (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.