|
Shifting Testing Left Bakes In Quality from the Start “Shift left” is one of the latest buzz terms in software testing. Movements like agile and DevOps recommend that testers shift left, but what does that mean, exactly? Here's how one tester became a believer in the shift-left movement; how he got his team's developers, analysts, designers, and managers on board; and how his entire organization has benefited from the shift.
|
|
|
4 Steps to Successfully Implement Mind Maps in Testing Mind maps can encourage a new perspective in your test team and promote collaboration. These maps make it easier for colleagues to grasp your work process, your progress, and your understanding of the project. How do you get started? Here are four steps that will help you implement mind maps successfully in your testing efforts.
|
|
|
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.
|
|
|
Manage the Business Risks of Application Development with Continuous Testing Continuous testing provides a real-time, objective assessment of the business risks associated with an application under development. Ultimately, continuous testing can provide a quantitative assessment of risk and produce actionable tasks that will help mitigate these risks before progressing to the next stage of the software development lifecycle.
|
|
|
Redistributed Testing: A Shift to Refine Requirements In short, redistributed testing is a shift in the emphasis and responsibility for testing. Testers are reassigned to work closer to the business with users or business analysts or are embedded in the development team.By being involved in story and scenario writing, the testers help to refine requirements and improve their quality. How could your systems benefit from redistributed testing?
|
|
|
Fixing the Brittleness Problem with GUI Tests One common complaint about test automation is that it’s too brittle. Small changes in the system can cause lots of rework during the automated checks. In this article, Clint Hoagland shows a way to fix “the brittleness problem” by using the right abstractions in your automation design.
|
|
|
How to Maintain a Compatible User Experience Tara Nicholson explains why it's important to take into account compatibility, which refers to the ability of a software system to function across a variety of client software (browsers), operating systems, and hardware combinations. In this article, Tara shares some helpful strategies for you to consider when maintaining a compatible user experience.
|
|
|
Using Containers for Continuous Deployment Pini Reznik explains how containers can help shorten the software development feedback loop by drastically reducing the overhead involved in deploying new software environments. This leads to faster build and test executions and simplifies the standardization of the development and production environments, allowing for an easier transition to continuous deployment.
|
|
|
Risk-Based Testing: Test Only What Matters Rajnish Mehta writes that test teams need to have a scientific way to support the business need of shipping a product out the door. Risk-based testing is a practical approach for test teams to utilize as it allows them to think from a business perspective.
|
|
|
How Skeleton Strings Can Help Your Testing Brian Noggle writes about how he uses "skeleton strings" to help him when he probes an application under test. Just as skeleton keys unlock doors, these generic skeleton strings open up access to a wide variety of defects.
|
|