test techniques

Conference Presentations

STARWEST 2018 Reduce Wait Time with Simulation + Test Data Management
Slideshow

Data has become the most significant roadblock that testers face today. In fact, up to 60% of a tester’s time is spent waiting for data. Chris Colosimo shows that many factors contribute to this wait time, including internal requirements from the test data management team to pull data in the proper form, wait times for sanitized or “test-safe” data, or, most importantly, building data sets that do not exist. Compounding these challenges is the inherit complexity of today’s data. You have to be a DBA to even begin to understand the structure and relationships needed to support your testing. There has to be a better way! Learn how to solve these challenges by providing a self-service method where users can model and repurpose their data on demand. Discover how to use a test data assistant automation to capture, model, and generate data for efficient use in API tests and virtual services.

Chris Colosimo
Engineering for Compatibility
Slideshow

Modern software development has brought us an incredibly powerful tool: continuous integration and deployment. However, taking advantage of this new system isn’t always straightforward. With powerful new tools come powerful new ways of making mistakes that can take your product down in a heartbeat. Melissa Benua has years of experience making CI and CD work for her, with lots of insights—both good and not so good. Come and learn from her as she shares key tips and tricks for coding and testing for both forward and backward compatibility in software releases. Useful for both traditional testers as well as combined engineers, Melissa provides technical and actionable advice to enable your team to make the right trade-offs and the right time investments, allowing your product to release to your customers safely and successfully.

Melissa Benua
STARWEST 2018 Why "Why...?" Can Be the Most Important Question for QA to Ask
Slideshow

To test a product, there are so many questions to ask, and so little time in which to ask them. More often than not, we get caught up in the who, what, when, and how, but Jane Jeffers from Riot Games explains that “why…?” questions can be the most important ones to ask when it comes to QA work. When missing the whys, we can wind up only focusing on specific details like who needs to do the work or when our deadlines are, and subsequently lose the bigger picture of why a project matters, and why we do what we do. Learn some of the key ways that you can ask why for product, for process, and for people, and how the answers you get will help you with everything from how to devise your overall test strategy to how you communicate with your teammates to get them thinking about quality.

 

[video:https://youtu.be/Bm_rtOmpIqg width:300 height:200 align:right]

Jane Jeffers
STARWEST 2018 A Tale of Continuous Testing
Slideshow

When the atmosphere is hostile to QA, and yet the demands on the QA Team are increasing, how do you transform a team where everything is tested and deployed manually, to an organization that delivers great software multiple times a day? Where do you start and how do you create the strategy for implementing Continuous Testing? Join David Lumpkin as he shares his company's journey to answer these questions and the team's evolution along the way. Over a three-year period, Craftsy went from an environment hostile towards QA, to one that embraces automation and exploratory testing, achieving the right level of coverage for every use case, device and browser. It wasn’t easy though and David shares their experience through many experiments, failures and revisions that finally made Continuous Testing a reality.

David Lumpkin
STARWEST 2018 Measuring and Maximizing Crowdsourced Vulnerability Discovery
Slideshow

There are many crowdsourcing vulnerability discovery techniques available today, making it difficult for testers to choose an approach that finds important vulnerabilities while offering the best bang for the buck. Join Mike Shema as he shares several years of real-world data that will help you understand the different discovery techniques, such as bug bounty programs and scanners, and the best time to use each technique. Mike also will discuss how your approach may change according to your lifecycle, and ways to think about integrating security within that process. You'll see how metrics play a pivotal role in determining where to focus your time in order to work as efficiently as possible while achieving the best results. Learn three key measures that help drive risk-based decisions while balancing your team’s efforts with the stakeholders’ need for information.

Mike Shema
STARWEST 2018 No More Shelfware—Let’s Drive
Slideshow

When Isabel Evans learned to drive a car, she also learned how to check, clean, and change spark plugs, mend the fan belt with a stocking, and indicate speed and direction changes with arm and hand signals. Now, we don’t expect to have to do any of those things; we just drive the car. That’s how test tools and automation could be. Just drive and concentrate on the journey of delivering software continuously—concentrate on engineering the solutions, not on the automation. To be effective engineers, we need the support of a powerful toolset that we understand. Is that what we have? Or do we still have shelfware sitting around expensively doing nothing, because we don’t know how to "clean the spark plugs"? Can we remove the difficulties and make using test automation a better experience, just like driving a car?

Isabel Evans
STARWEST 2018 The Logic of Verification
Slideshow

Software testing is sometimes described as “verification and validation”—or, according to Wikipedia, “the process of checking that a software system meets specifications and that it fulfills its intended purpose.” Yet, renowned tester and teacher Michael Bolton argues, if we examine the concept and logic of verification, we quickly recognize that there are serious limitations to what can and cannot be checked and verified. This is not to say that checking is a bad thing—on the contrary; checking can be very valuable. Still, it’s important for testers and their clients to recognize the fundamental limitations of checking and to address those limitations in our testing strategies.

Michael Bolton
STARWEST 2018 Use Soap Opera Testing to Twist Real-Life Stories into Test Ideas
Slideshow

Reality is a great source of inspiration. Real-life situations can present complexities that are not always anticipated—and, as a consequence, not always handled well. Business functional tests should try to present situations that are routed in reality but also aren’t too obvious. Testing and automation pioneer Hans Buwalda came up with a concept for test design called "soap opera testing" based on this concept. It is a style of writing tests where one writes as if they were episodes in an imaginary soap opera on television. Soap opera episodes are based on real life, but usually they are more condensed and somewhat exaggerated, which are great properties for efficient and effective test design. Thinking of test development as writing soap operas can encourage creativity and be more fun. It also paves a way for nontechnical domain experts to contribute.

Hans Buwalda
STARWEST 2018 Automation and Test Strategies to Save Our Project from the Brink of Collapse
Slideshow

Teams are sometimes asked to turn a mess of undocumented, poorly structured legacy code into a robust product under impossible deadlines. Test strategies blending automation, exploration, and refactoring can help focus development efforts and converge even the most chaotic projects. But, where do you start? Join Jonathan Solórzano-Hamilton as he shows how automation can help drive products into a state of release readiness. Learn how refactoring, test-driven development, SOLID principles, dependency injection, and mocking frameworks help break down complex development problems into actionable chunks to delivering reliable, self-documented, and high-performing products. Jonathan walks you through the concepts of “Single responsibility”, “Open/closed”, “Liskov substitution”, “Interface Segregation”, and “Dependency Inversion”.

Jonathan Solórzano-Hamilton
STARWEST 2018 Frontend Testing: Stepping in and Collaborating with Developers
Slideshow

Testing is shifting left, moving closer to testing the code itself before the full product is ready for release. While the backend world already has established methodologies for testing, frontend developers and testers are still trying to figure out how to work together to effectively test the code. Gil Tayar suggests testers need to communicate with the frontend developers to understand the framework by which frontend code is tested, the various kinds of testing that can be performed on frontend code, and which tools can be used. During this session, Gil helps ease your fear of the unknown by teaching you how to test developer code. He discusses various test methodologies you can use and how they fit together in a coherent way. Gil also includes sample code that you can use as a template in your own project. If time permits, we'll get hands on and do a bit of live coding.

Gil Tayar

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.