Related Content
 |
Maintaining Testable Requirements and Acceptance Criteria Once a testable requirement or acceptance criteria have been “created,” there is a tendency to assume that the task can be considered completed. Because that may or may not be true, it is better to continue to pay attention to testability. Here are four ways to maintain testable requirements. |
|
 |
Successful Performance Testing Begins at Requirements Discovering performance issues in early builds allows more time to correct the design. By including critical performance-related features and elements earlier, we can take advantage of the incremental nature of the development process to avoid creating engineering in potential performance issues. |
|
 |
Tools—Some Assembly Required A tool architecture is simply a picture of all your development, testing, and deployment tools and how they fit together. Creating a "current state" diagram and then looking forward and creating a "future state" diagram helps you understand where tool integrations would be beneficial. |
|
 |
How Can I Create Good Definitions? It is vital that everyone communicates properly if we are to build software applications that meet the needs of our organizations. However, creating clear and unambiguous requirements necessitates good definitions, which can sometimes be difficult. Conrad Fujimoto shares his starting technique. |
|
 |
Creating Testable Requirements and Acceptance Criteria Testable requirements, or acceptance criteria, are the communication of an expectation between its originator and potential stakeholders. Many testers struggle with this starting point. But once you succeed, you know the processes that can build and test a system implementing “good” requirements. |
|
 |
Mobile Testing: The First Step—or Two On many mobile projects, testing is not practiced well—or sometimes not done at all. Many testers from the desktop world are moving into mobile, and there is much they can take from traditional testing into the mobile space. Here are some ideas to get you thinking about testing mobile devices. |
|
 |
Accessibility Testing: It's Essential More than 27 percent of the world's population has some form of disability, meaning they could have special needs when it comes to accessing the Internet. Following accessibility guidelines improves the overall usability of the software under consideration, which helps all people using it. |
|
 |
Stop Making the Same Mistakes We keep changing the names of the development processes we use, but we do not fix the fundamental error they all suffer from: the failure to set a date and control the scope of the project—including proper estimation of testing efforts. Customers and IT must work together to truly be successful. |
