During this evolving presentation, Erik discusses existing testing methods and techniques. Which ones really work, and which ones provide the most valuable contribution towards project success? It does not have to be perfect, often good enough testing is sufficient (depending on the domain in which you are working). Five important and indispensable recommendations are presented that every (Agile) project should implement in order to be successful. This presentation is based on many practical experiences in various domains where Erik discusses testing methods and techniques that can make a difference. You‘ll learn the most important and indispensable recommendations that every (Agile) project should implement in order to be successful. Clear testing priorities (risk-based) Effective reviews Developers doing unit testing Test design techniques as tools Experienced and skilled tester (the people aspect). The presentation stresses where and when you can be good enough, when there is no reason to be perfect, and where you need to be perfect as well. Erik Van Veenendaal

If you’re not physically fit, you feel physical stress as you climb a steep hill. Likewise, if you’re not mentally fit, you will feel mental stress, such as anxiety, frustration, or unhappiness, as you handle work and relationship challenges. Recent events such as the coronavirus, disruption in financial markets, social unrest, and political changes have over-stretched all of us. As software engineers, we’ve adapted to #WorkFromHome in many ways including Zoom and other #FutureofWork collaboration methods. Some of us have even adapted our exercise routines to home workouts without the need for equipment or going to the gym. However, many of us ignore the need and possibly are not aware that we can Reset and upgrade our mental fitness operating system to not just survive but thrive in these tumultuous times. Listen in to this impactful 20-minute session with our special guest, Julie Wong, and Take charge of your mind and your life with a simple operating system to impact: Peak Performance Peace of mind/wellness Healthy Relationships

In spring 2020, Rachael Lovallo’s company joined many others in going fully remote due to the Covid-19 pandemic. They needed to significantly rework test strategies to continue ensuring a top-quality communication platform for emergency medical professionals and their patients. After over a year of adapting, they are thriving and may never return to old methods. In this talk, Rachael will share her team’s three most impactful test strategy shifts. First, physical devices still outperform simulators for non-automated testing, but the group needed to know who had what devices, reach out for help with test coverage, and make time to help others. They also found an investment in screen mirroring software worth every penny for providing a semblance of being in the same room crowded around a mobile phone. Second, being a cross-functional test team quickly grew challenging when the office closed. The group kept everyone in the loop by adding structure to team dynamics, including weekly meetings, monthly feature demos from the tester perspective, scenario-based bug bashes, and even designated time for water-cooler talk. Lastly, they involved testers in projects earlier. With physical distance, communication became more labored on the development team, especially around defining requirements and release sequencing. The testers used their knowledge of the various moving parts of the product to ensure quality from requirements gathering through development, automating and testing, to eventual release to customers. Join Rachael as she shares how her team faced the challenges brought by 2020, remained flexible, and came into 2021 stronger than ever.

QA people traditionally focus on dynamic testing: they either click and type their way through the software under test as it executes, or they write automated tests that let the computer do that work for them. But does this approach overlook the potentially low-effort, high-reward approach of static testing? Static testing tools analyze the source code of the software under test without running it. At first glance, this might not look like a powerful or promising strategy, but static tools have come a long way since the glorified linters you might have tried years ago. If you have questions such as: What kinds of problems can we find with static testing? Does static testing reduce the need for dynamic testing, or does it cover a different range of issues? How much time does it take to configure and run static testing tools? Are they easily integrated into CI/CD pipelines? Are their false-positive and false-negative rates acceptable? In short, can static testing improve the life of a QA professional, or is it yet another expensive technology of questionable value?