Related Content
Making a List, Checking It Twice: A Testing Strategy for the Holidays The holiday season means consumers will be doing a lot of shopping online. This poses immense challenges for the testers who have to ensure that all business channels, including mobile, offer a smooth, high-performance experience. This story gives some core components of a holiday testing strategy. |
||
The Top Four Myths about Web Accessibility There are many misconceptions about accessibility that prevent people from making a conscious effort to incorporate it into their websites. But really, developing and testing accessible websites doesn't require more work, and it has many benefits. Let’s disprove the top four web accessibility myths. |
||
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. |
||
Beware of Serial Status Meetings Standup meetings are great in many instances. But if you're calling serial status meetings, you may find that people will stop attending. To engage employees and address issues quicker, you may want to try lean coffee or a problem-solving meeting. Read on for tips on involving your team. |
||
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. |