Requirements

Articles

A pile of documents Slim Down Your Test Plan Documentation

Test plans are essential for communicating intent and requirements for testing efforts, but excessive documentation creates confusion—or just goes unread. Try the 5W2H method. The name comes from the seven questions you ask: why, what, where, when, who, how, and how much. That's all you need to provide valuable feedback and develop a sufficient plan of action.

László Szegedi
A line of identical rubber ducks The Unspoken Requirement: Testing for Consistency

It's easy to see that style consistency is important when discussing the user interface. But there are other areas where being consistent is just as important, even though they are not as visible. Consistency is one of the quality attributes of a product—any product—even if it is not stated clearly in the requirements documents, and testers have a responsibility to check for it.

Michael Stahl
Passing the baton Testing during Transition: Test Criteria for Outsourced Software

In the world of IT outsourcing, it is not uncommon for a company to have its applications and infrastructure developed or maintained by others. As vendors compete for this business, a common trial is testing the transition activity as a whole. How would you design acceptance criteria of a transition trial so that it is testable and clearly communicated?

Jesper Ottosen
Application logs Who’s Using Your App? Examine Logs for Testing Insight

When testing an application, have you ever thought to yourself, "I wonder who uses this"? Examining the app's logs can give you some idea. Logs are helpful for testers because they provide real feedback and insight into an application as it’s being used, as well as information that describes or can even help solve bugs. Here's how to use them to inform your testing.

Josh Grant
mobile phone Weighing the Costs and Benefits of Mobile Test Automation

Today’s market is teeming with attractive options for automating your mobile testing—each with a price tag. You may perceive mobile automation solutions as too expensive, but before you dismiss test automation as a viable solution for your business, let’s break down the benefits, options, and costs of automating your mobile QA process.

Michael W Cooper
man guessing Don’t Guess Your Tests—Strive for Complete Requirements

Many teams struggle with test creation due to miscommunication or a lack of requirements, testers not being present during design phases or discussions, a shortage of time, or incomplete information. But that doesn’t mean you should turn to guesswork. Your tests will suffer in quality and completeness. We must always strive to get the desired requirements.

Nishi Grover Garg
lock Using the Principles of the CIA Triad to Implement Software Security

If you're starting or improving a security program for your software, you probably have questions about the requirements that define security. Data need to be complete and trustworthy, and also accessible on demand, but only to the right people. The CIA triad defines three principles—confidentiality, integrity, and availability—that help you focus on the right security priorities.

Sylvia Killinen
Disaster Plan key on keyboard The Apocalypse Plan: What to Consider before Things Go Wrong

Undoubtedly, your organization has disaster plans in place for recoverable situations. But what about for going out of business? Thinking about your obligations to clients, users, customers, and partners before the worst happens can make the transition easier for everyone. Here are some people and things you should incorporate into your apocalypse plan.

Brian Noggle
puzzle The Collaboration of Unit Testing

Unit testing can be one of those polarizing topics in software development. But Joe DeMeyer says good unit testing allows you to explore products deeper, lowers your estimate, improves quality, and maintains productivity pace. Here, he talks about how you can get your developers and business team on board.

Joe DeMeyer
Big data Big Data’s Relationship with Business Intelligence and Data Warehousing

You’ve probably heard the buzz about big data and business intelligence data warehouses. Both deal with collecting information for analysis, but how are they different? When should you use one or the other? This article explains these two data solutions in a user-friendly way with real-world examples.

Nels Hoenig

Pages

StickyMinds is a TechWell community.

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