test techniques

Articles

Arrow pointing left Shifting Testing Left Is a Team Effort

There is a lot of talk in the testing world about shifting left. Basically, “shift left” refers to moving the test process to an earlier point in the development process, independent of the development approach. This article explores a case in which shift-left has been applied, and the lesson is that shifting left cannot be achieved by testers alone—it must result from a team effort.

Man in a suit reading the Business section of a newspaper Getting Started with Business Intelligence Testing

There’s a bit of hype in terms such as business intelligence, data analytics, and data mining. In testing terms, though, it means working with scripts and databases, often without traditional GUI interaction. But core testing skills—analysis, synthesis, modeling, observation, and risk assessment—will still help you go far in business intelligence testing.

Albert Gareev
Sign reading "Duh!" When the Code Is Too Obvious to Check

How many times does something seem too obvious to check? Most of the time this normal human response is a handy shortcut. Your brain tries to save you time—but you can’t always trust it. If your code malfunctions, each of those "too obvious to check" thoughts will bias your thinking about what caused the malfunction. We have to commit up front, before our thinking crystalizes, that the code will have to prove to us that it is correct.

Steve Poling
Icons for education and continuous learning To Be a Good Tester, Just Do What No One Else Can

If you want to have a successful career in testing—and maybe even get beyond the day-to-day at the individual level, and improve the team or division—all you need to do is things no one else can. That means staying ahead as the industry moves on, which takes an intense and continuous investment in learning and practicing new things. Here are some suggestions for what that could look like.

Matthew Heusser
A robot hand touching a keyboard 5 Things That Will Impact the Future of Software Testing

From the way we look at software, evaluate risks, think about complexity, design our test approach and strategy, and help to release a stable product to the customer, technology has had an influence on how we test software. And that influence will only continue as technology advances. On a high level, here are five key things we’re already seeing that are going to shape the future of software testing.

Raj Subramanian
Desktop with CRM software dashboards Lessons Learned in Testing CRM Software

CRM systems manage a company’s business relationships, including customers’ data, information, and interactions, so there’s a lot that can—and should—be tested. Viktar Sachuk talks about his experience in testing CRMs to provide some tips for dealing with the trickiest parts of CRM testing, specifically focusing on some preparatory measures, functional testing, integration testing, and test automation.

Viktar Sachuk
Two golden retrievers lying on the floor, photo by Gulyás Bianka The Who, What, When, and How of Pair Testing

Pair testing can help you speed up your test assignment and provide more quality to your test results. But who can do pair testing, and when should they do it? And what kind of pair testing is best for your situation? This article gives you more information about how you should conduct pair testing in order to maximize its benefits.

Simon Schrijver
Mobile phone showing social media apps Designing Test Scenarios for Social Media Mobile Apps

The definitive features of a mobile social app are the ability to send and receive messages, push notifications, and sharing media such as photos, audio, and videos. While creating a test strategy for such apps, cross-platform compatibility is an important consideration. Here are some scenarios you should include in your test strategy for a social media mobile app.

Krishnan Govindarajan
Mug of beer A Tester Walks into a Bar: Reviewing Test Techniques

A tester walks into a bar and orders a beer. Then he orders ten beers, negative one beer, zero beers ... There are many variations of this joke. So let's try to think of every variation! Continuing the scenario of ordering beers at a bar, let's build test cases for how we would test the beer-ordering process as though it were software.

László Szegedi
Car steering wheel photo by Nicolai Berntsen A Case for Test-First Development

You may feel you don't have time to write unit tests, but you really don't have time not to. Steve Poling makes the case that writing tests first not only will yield better code, but will help you get that code working right sooner. Here's how using a test-first approach changes your thinking about coding, lets you see mistakes immediately, and helps you create more testable code.

Steve Poling

Pages

StickyMinds is a TechWell community.

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