QA
Articles
The Value of Test-Driven Development when Writing Changeable Code Writing changeable code makes it easier and more cost-effective to add features to existing software. Writing changeable code doesn’t take longer, but it does require paying attention to certain things when building a system. It's important to have a good suite of unit tests that support refactoring code when needed, and test-driven development helps you create independently testable code. |
||
Hybrid Verification: Mixing Formal Methods and Testing The ability to verify contracts either statically or dynamically, coupled with recent advances in proof technology, has opened up a new and promising approach to verification. Critical code can be proved with formal methods, and less critical code can be verified using traditional testing, with a clear separation at the interfaces between the two. |
||
Linguistic Testing: Setting Up Your Software for Global Quality Globalization is an important step in ensuring your product is ready for worldwide markets, and linguistic testing is a crucial piece of the puzzle. This article looks at what linguistic testing is, product examples, and how locale-specific cultures play an important part in enabling linguistic support. Here’s how to design the best strategy for implementing a linguistic test effort. |
||
4 Strategies for a Structured QA Process Being a software tester is no longer just about finding bugs. It is about continuous improvement, defining a clear test strategy, and going that extra mile to improve quality. Following a consistent, structured approach to QA will help you acquire more knowledge about the product you are testing, ask questions you otherwise may not have thought of, and become a true owner of quality. |
||
Using Bug Taxonomy to Design Better Software Tests In software testing, bug taxonomy involves defining feature categories and collecting lists of possible bugs in each category. These lists can be used to give inexperienced testers some starting points, to help experienced testers brainstorm new ideas, and to evaluate the completeness of a test case. Using an existing bug taxonomy can be useful, but creating your own is even better. |
||
Endgame Testing: Exploring Your Agile Product End to End The main goal of endgame testing is to test the system end to end from the user's perspective. This should ensure continuity between components developed by different teams, continuity in user experience, and successful integration of new features. Endgame testing will often identify gaps that are difficult to discover inside agile teams, including flows across the product. |
||
Has Continuous Deployment Become a New Worst Practice? Software development has been moving toward progressively smaller and faster development cycles, and continuous integration and continuous deployment are compressing delivery times even further. But is this actually good for businesses or their users? Just because you can deploy to production quickly and frequently, should you? |
||
Test Techniques for Today’s Telephones Telephones look very different today from when they were first invented, and their many capabilities and components make for some interesting test cases. Krishnan Govindarajan details his team's recent experience testing a phone, including its splitter, cloud backup, voicemail and answering machine, and VoIP, and gives some techniques to use when testing modern telephones. |
||
Accessibility Testing 101: Getting Started and Catching Up As with any other quality attribute, it is ideal for accessibility to be incorporated in the early stages of design and engineering. But organizations that didn’t initially take accessibility into account can still address it now—it’s better late than never. Here are the main attributes you should consider from the design, development, and testing angles, whether you're building accessibility in from the beginning or adding it now. |
||
What Testers Need in Their Accessibility Testing Toolkits A software tester’s accessibility testing toolkit should contain various tools, both to help testers “walk in the shoes” of their users and to quickly flag obvious problems and expose accessibility features (or a lack of them). High performance is only achievable with human skill, but these tools will help you uncover potential issues and make your product a better user experience for a wider audience. |
Pages
Recommended Web Seminars
Mar 28 | The Testing Practices Fueling High-Performing Software Teams |
On Demand | Building Confidence in Your Automation |
On Demand | Leveraging Open Source Tools for DevSecOps |
On Demand | Five Reasons Why Agile Isn't Working |
On Demand | Building a Stellar Team |