The Latest
![]() |
Testing through the Ages[presentation]
Slideshow
How long have you been in software testing? What was testing like when you first started? How did the discipline of software testing get to where it is today, and where is it headed in the future? |
![]() |
![]() |
Full-Coverage Testing in Small-Business Environments[presentation]
Slideshow
In small-business environments, testing is often completed in hindsight—or overlooked entirely. |
![]() |
![]() |
A Practical Guide to Testing in DevOps[presentation]
Slideshow
Where does testing fit in a DevOps world? DevOps encourages the development and operations teams to work together. |
![]() |
![]() |
No One Really Cares about Testing: A Perspective from a Billion-Dollar App Team[presentation]
Slideshow
When is the last time you read a five-star review in the App Store or Play Store that raved, “This app is so well-tested! Their quality assurance team really knows what they’re doing. |
![]() |
![]() |
Automated Security Scanning for Your Delivery Pipeline[presentation]
Slideshow
Agile development and DevOps depend on an automated pipeline to build, test, and deploy code quickly. Security is all too often viewed as a manual task that is too difficult to automate and is left for later—not a good decision! |
![]() |
![]() |
Postmodern Testing[presentation]
Slideshow
The modern world of testing gets noisier, more fragmented, and more confusing every day. Postmodern Testing is an admission of the imperfect world we live in—a new test strategy framework for today’s agile, continuous, and multiplatform teams. |
![]() |
![]() |
5 Key Factors to Achieve Agile Testing in DevOps[article] Part of the path to DevOps requires adoption of agile methodologies. What does it mean for testing when you switch from the traditional waterfall model, with a few long release cycles per year, to the agile model, with changes occurring every two weeks? Here are five key factors to achieve the agile software testing necessary in DevOps. |
|
![]() |
The Shift-Left Approach to Software Testing[article] The earlier you find out about problems in your code, the less impact they have and the less it costs to remediate them. Therefore, it's helpful to move testing activities earlier in the software development lifecycle—shifting it left in the process timeline. This article explores the shift-left methodology and how you can approach shifting left in your organization. |
|
Lightning Strikes the Keynotes[presentation]
Slideshow
Lightning Talks consist of a series of five-minute talks by different speakers within one presentation period. |
![]() |
|
![]() |
Clone of Lightning Strikes the Keynotes[presentation]
Slideshow
Lightning Talks consist of a series of five-minute talks by different speakers within one presentation period. |
![]() |
![]() |
The Evolution of a Continuous Integration Pipeline[presentation]
Slideshow
Each month more than 120 million unique visitors access content from USA TODAY and Gannett’s local media organizations, making them the largest US newspaper publisher by total daily circulation. |
![]() |
![]() |
Diversity without Disclosure: Rethinking Our Norms[presentation]
Slideshow
Organizational diversity isn't just about the attributes we can see. Every team has members with a near-infinite spectrum of needs, some of which we know about and a lot more we probably don't (and might never). |
![]() |
![]() |
Nontechnical Managers Leading Technical Teams[presentation]
Slideshow
Technology is complicated and changes every day. Even leaders with a technical background and deep understanding of tools and processes have trouble keeping up, and it’s virtually impossible to be an expert on every single aspect of a product. |
![]() |
![]() |
Picking the Right Branch-Merge Strategy[article] A good branch-merge strategy facilitates processes among multiple developers and is the basis for any well-functioning DevOps pipeline that uses continuous integration. Let’s explore branching strategies, merging strategies, and how you can put them together in a way that’s right for your team in order to bring quality features to production faster. |
|
![]() |
Testing a Software Rewrite[article] Suppose we’re looking at a system rewrite where the stakeholders have none of the original engineering documentation. (This isn't surprising; documentation becomes obsolete—or even misleading—as the system changes, and corresponding docs don't get updated.) What can we do? Here are some tactics to use—and risks to anticipate—when testing a system rewrite. |