|
Six Tips for Building a Better Load Testing Environment Building a realistic test environment is essential for the success of your load testing, but it is also a challenging task that can require resolving technological, organizational, and security issues. This article can serve as a roadmap for building a faster and more efficient load testing environment that leads to quicker deployments.
|
|
|
A Tester among Developers: Life beyond the Code Tester Anastasia Kotsevich got the chance to work side by side with her company’s coders. This experience opened her eyes to some problems she wasn’t aware of before, and some solutions: designating a common team goal and opening clear lines of communication.
|
|
|
Crowdsourced Testing Lets Your Apps “Go Wild” It simply isn’t feasible to test every possible user scenario with a new app, and the testers who already know how the app should perform can't approach using it the same way as someone unfamiliar with the process. Enter crowdsourced testing, where you gather a customizable pool of people from outside your organization to test your apps for defects and usability.
|
|
|
Managing Acceptance Criteria Plans Some of the hardest and most crucial instances in any project execution are the user acceptance test phases. But having a thorough and clearly documented process for evaluating acceptance and exit criteria that you previously agreed on with the end-user will help you handle expectations and plan on results.
|
|
|
Guide Your Agile Development with Traceable Tests Testing professionals who are learning about agile often want to know how they can provide traceability among automated tests, features, and bugs and report on their testing progress. Here, Lisa Crispin gives an example of how her previous team worked together to integrate testing with coding and helped everyone see testing progress at a glance.
|
|
|
Testing Economics Everything we do has an economic impact because what we do has costs and benefits. Testing is about getting real feedback quickly, reducing wasteful testing activities, and putting a mirror in front of our applications. It becomes advantageous to understand the costs of these activities and direct the effort investment where it’s most beneficial.
|
|
|
Using Business Decisions to Drive Your Testing Coverage In a business setting, software testers have a great challenge: to articulate how they support the business lines. One way to approach this is by addressing the business decisions—and there are plenty around. Use them to drive your testing activities and increase the business decisions being covered by testing.
|
|
|
Is Code Coverage a Silver Bullet? While code coverage is a good number to look at in terms of reach achieved in a testing cycle, is it foolproof? Is this metric a silver bullet for understanding the team’s coverage and vouching for testing scope? In short, no. But it is a vital step on the way to solving your testing coverage issues.
|
|
|
The Role of Testers in an Agile Environment There are many diverse ideas about what being a tester means in agile development environments. This leads to confusion between how agile testers and agile QA “fit” into agile teams and what the QA tester responsibilities are. John Stevenson explains why there appears to be some fear and a little distrust of agile environments among some testers, then offers suggestions for dealing with their confusion.
|
|
|
Awareness of Risk Identification in Software Testing When testing software, most of us identify risk seemingly effortlessly. But do we really understand the process we’ve undertaken? Do we know what methods we’ve called upon? Are we aware of how we’re identifying risks? And therefore, are we identifying all the important risks? David Greenlees uses models to assess these questions.
|
|