Systems | Development | Analytics | API | Testing

September 2022

Fused testing pushes teams closer to continuous integration

You’ve heard from us about fused testing before, and get ready to hear more. Fused testing is a methodology that goes beyond just executing manual and automated testing frameworks. (Though it does do that exceptionally well.) Fused testing is also a big push toward continuous integration (CI). Yes, that CI/CD pipeline.

Part II: Build a Bridge Between Shift Left & Shift Right

In the first blog of this series, I used the metaphor of a bridge connecting two towns to illustrate the importance of establishing purposeful connections between your shift left and shift right testing initiatives. Modern product organizations that fail to engineer a bridge to link the two “towns” (shift left and shift right) will, at a minimum, suboptimally utilize precious human and machine testing resources.

A Pragmatic Test Automation Journey

This guide explains how the logical principles of fused testing debunk common test automation journey assumptions. Together, humans and machines run rapid test cycles conducted in short timeframes to release quality apps and better end-to-end customer experiences. This guide explains how the logical principles of fused testing debunk common test automation journey assumptions. Together, humans and machines run rapid test cycles conducted in short timeframes to release quality apps and better end-to-end customer experiences.

Engineers are not testers. Here's how to build a QA team.

Great software engineers are expensive, in-demand, and incredibly hard to find. Building an engineering team is a heroic feat – but stop asking them to moonlight as testers and build a QA team instead. Trying to offload QA duties onto your engineers is not as effective as you might hope. Unhappy developers lead to high turnover, slower release time, and an expensive talent search. Take it from the experts; build a QA team if you want high-quality products and releases.