Testing and Quality Assurance
Testing and Quality Assurance
|
Service Providers Need to Step Up When Handling Web OutagesInternet usage varies from casual browsing to multibillion-dollar online businesses. Such a wide range in usage brings in a wide range of impact when there are web outages—from a mild inconvenience to millions of dollars in lost business. Service providers need to step up when handling web outages. | 
|
|
Working Your Way Out of Large Technical Debt in a Small ProjectWhen you transition to agile with a small project and you have a reasonably sized codebase, chances are quite good that you’ve been working on the product for a while. You have legacy code—and that code comes with technical debt. Johanna Rothman has ideas about how to work yourself out of it. | 
|
|
Tips for Picking the Right Software TechnologyWhen all you have is a hammer, everything looks like a nail. You may have heard this quote before, but it applies well to software technology choices. The key to choosing an appropriate technology for a software solution is to avoid bias and carefully consider the requirements you know. | 
|
|
Developers and Testers: How to Be a Good Follower Followership is the capacity of an individual to actively follow a leader. In an autocratic world, followership would mean "do as I say," but in information technology, which is more participative in nature, followership means much more than being a robot who just follows instructions. |
|
|
Use A/B Testing to Increase Revenue and User Satisfaction Bonnie Bailey writes that software teams should use split, also called A/B, testing to capitalize on the human subconscious. Just about any software effort can benefit from knowing what increases revenue or user satisfaction, which ultimately boosts the success of the project. |
|
|
Two Reasons Why Test Automation Projects Fail Very few things catch the fancy of management as much as the compelling prospect of automating tests. Test automation, after being projected as a magic wand, often fails to live up to the expectations. The core question is—Why do test automation projects fail? |
|
|
Why You Need to Take Technical Debt into AccountTechnical debt is a metaphor for the result of skipping design or the implementation steps in order to achieve a short-term goal. The next time you work with code, remember that changes may be more costly to make because of your prior decisions. You achieved something, but you incurred debt. | 
|
|
Google Raises the Stakes for Bug BountiesTo keep security bug reports coming in for their bug bounty programs, Google is willing to write bigger checks. The company announced that it is raising security rewards—up to five times higher in some cases—for its Chromium program. Pamela Rentz highlights the recent bug bounty program changes. | 
|