Behavior-Driven Testing Using Page Object Models

Does it feel like you spend half of every sprint fixing failing automated functional tests? Are programmers unwilling to work with automation code? Is test automation a maintenance nightmare? There is a better way. The Page Object Model (POM) is a powerful design pattern for building test automation. A lack of design discipline can lead to test automation code that is buggy, brittle, and almost impossible to maintain.

Brian Hicks

5 Ways to Make Load Testing Work for You

[video: width:300 height:200 align:right]

Israel Rogoza

7 Sure-fire Ways to Ruin Your Test Automation

[video: width:300 height:200 align:right]

Seretta Gamba

A Tester’s Role in Requirements Exploration

Having a shared understanding of desired and undesired behaviors for each new product feature is key to delivering value to the business frequently and predictably. However, many teams lack this understanding even as they start coding. As testers, we can explore feature specifications early, contributing to a successful and timely delivery. With a testing mindset, testers can elicit examples from stakeholders and help turn them into test scenarios that guide development.

Janet Gregory

Automation in Aviation and Mission-Critical Software

[video: width:300 height:200 align:right]

Alexandre Bauduin

Combatting Threats to Payment Processing in the Era of Connected Ecosystems

[video: width:300 height:200 align:right]

Elizabeth Koumpan

Delivering the Goods: Harmonizing Regulated and Agile Practices

Agile testing is hard. Testers contend with terse requirements, minimal process, little documentation, continually evolving business, technical and organizational factors. Auditors demand proof of compliance. Some teams have trouble conforming to regulations while preserving agile practises.

Griffin Jones

Devices and Desires: As Humans How Do We Experience Software?

We consume and still we desire more. More devices, more apps, more data, more bandwidth, more connectivity. The more we have, the more we want …. We assume that to be true – those of us who work in the software industry. But is that true? To understand what is really required of our products, we need to design and test a pyramid of interlocking quality attributes, that build together to make an optimum experience for the people who use our products, matching their needs, and their desires.

Isabel Evans

Ditch Your Bug-Tracking Tool: 3 Solid Tactics to Minimize Bug Counts

A bug-free product release is an ideal that testers, developers, and project managers strive for, but when it comes to the go/no-go decision, the balance is often struck between "good" and "good enough," leaving behind a rotting to-do pile in the bug-tracking tool that is rarely acted upon in the next release. How can testers stop adding new bugs to the ever-growing list and clean up the “bug dump”? Is it possible to speed development and deliver better software by sidestepping the bug-tracking tool?

Jerry Penner

Docker and the Path to a Better Staging Environment

Staging environments are notoriously difficult to set up and maintain. Unless you have a top-notch DevOps team, staging environments are usually different from production environments, and consequently, they are fraught with problems—failing deployments, "out of disk space" errors, and various other issues. Even when the staging environment is great, there's still a problem: There’s only one. If you want to test a feature branch, you must allocate time or, alternatively, install the feature branch and risk disrupting other testers.

Gil Tayar


CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.