Kevin Dunne is the general manager of Tricentis Flood, ensuring their continued commitment to innovation and delivering tools to create software that scales. With a deep interest in the emerging trends in software development and testing, Kevin is dedicated to collaborating with thought leaders in this space. Kevin comes to Tricentis, the parent company of Flood, thanks to its joining forces with QASymphony, where he was one of the first employees. Kevin has seen many facets of the business, working in sales, customer support, marketing, and product management, and has managed testing on large government and Fortune 500 engagements while delivering ERP implementations and custom software development. Kevin holds a bachelor of science degree from Vanderbilt University.
Since the inception of load testing, the approach has been mostly the same: simulate the traffic of an application by creating load at the API level. But there have been market shifts that make load testing with browser-level users more feasible—allowing us to test with real load and measure true user performance.
A shift toward working in smaller teams on tighter releases forces organizations adopting agile to rethink what successful delivery looks like. It can be a big change for those used to silos. Here are three key symptoms of agile teams that don’t have close collaboration—and some solutions you can implement to fix them.
Behavior-driven development can bring many benefits to software delivery. But while many companies focus on customizing frameworks, tools can only achieve as much as the people and organizations behind them. You also have to consider the individual roles and personalities of your developers and testers.
Exploratory testing, or ET, is a good fit for agile processes, can be done by any member of the dev/test team, and helps develop applications that map to customers' needs. Kevin Dunne writes how with increased use of ET, testing becomes an intellectual pursuit driving product quality and agility.