ANASTASIOS DASKALOPOULOS - Director Of Quality Automation, DemandBridge

THE TEAM NATURE OF DEVTESTOPS: THE DIFFERENT ROLES AND HOW TO BRING THEM INTO THE EFFORT

Testing/QA has always been a group effort, but in DevOps, the various roles of a Project/Team are integral to the success of testing in the DevOps framework. From Project Management to Systems Operations and Development, all provide different forms of information that all in combination provide the data needed for the success of DevTestOps. We will first examine briefly what DevTestOps is, how it can be of advantage to the project or company, how to communicate to the different project and company roles to bring them into the DevTestOps framework, and how to make the team effort work for greater coverage.

MAX SAPERSTONE - Technical Sales Manager, Steampunk

PAGE OBJECT MODEL PITFALLS

Selenium has been around for over 15 years, and by now organizations have realized that Selenium tests need to be treated the same as any other functional code. This means not just keeping your tests in source control, but also designing them to be maintainable and robust. A common design pattern known as the Page Object Model (POM) has emerged, which greatly assists with the organization and maintenance of tests. But there are scalability, speed, and robustness issues with this pattern. This has caused organizations to move away from Selenium for another tooling, however, most organizations are encountering the same problems, because they are using the same problematic design patterns. Max will outline these issues, how to avoid them, and better patterns to use. He'll discuss how to transform your tests to be more effective, using patterns like Arrange Act Assert, and not relying solely on Selenium to exercise the system.

ADAM SANDMAN - Director, Inflectra

READY TO RUN THE RISK? - APPLYING A RISK-BASED APPROACH TO TESTING

One of the most underappreciated aspects of testing is risk. There is never enough time to do all the testing that would be needed for 100% coverage (this is true for automated testing and manual testing). Consequently, there is a tradeoff between spending time on different types of testing and focusing on specific features, modules or requirements. By applying a risk-based approach to testing, you can seek to optimize these trade-offs with a data-driven methodology.

In this talk I will discuss the different types of risk that you should be considering (technical, business, etc.) and how you can use the assessment of risk to create a test plan that gives you the greatest risk coverage in the time available. I will cover prioritization techniques such as business feature importance, technical code stability, test stability, user flow and critical service mapping to determine where the risk lies in each software release and what testing should be done.

PETER KIM - Director of Quality Engineering, Kinetica

TEST AUTOMATION STRATEGIES TO DRIVE EFFICIENCY AND ROI IN AGILE

Test automation strategies can drive efficiency, in the SDLC, while expediting the time to verify and validate your product from one quality gate to the next. However, test automation strategies can also stagnate progress by incurring tech debt and swallowing up valuable team resources where refactoring and brittle tests can create bottlenecks and contribute to a misguided trajectory on the quality objectives. Furthermore, with refactoring and employee churn, there are opportunities and risks such as unreliable test results, test gaps, and loss of domain knowledge .. all of these are threats to the quality of the product.

This talk will address how the QE team can tackle these issues by focusing on empowering the quality team with understanding the taxonomy of test management, gaining a powerful, yet simple, the foundation on test automation, and learning hands-on modeling and design patterns (testing and software) to level-up the team.

NICK SHRIMANKAR - VP of Technology, Elasticity

SHIFT LEFT, RIGHT, AND CONTINUOUS AUTOMATION TESTING

For the past few years, Shift-Left has been given importance in the IT world. However, with the emergence of Reliability, Resiliency, and Observability it is imperative that testing be shifted right as well. Agile and DevSecOps methodologies and frameworks allow teams to deliver value faster posing challenges in areas of Testing. Teams no longer can afford a 1-month long regression testing cycle and have to be proactive in staying ahead of the curve when it comes to testing. Teams must consider testing from ideation till delivery and continue to test post-delivery.

SANJAY SUNKARA - Senior Manager, Capgemini Government Solutions

INTEGRATING AUTOMATED TESTING INTO DEVOPS AND AGILE

1. How the trends have been in the past, how the outlook is currently and what holds into the future.

2. Need for integrating Automated Testing into DevOps and Agile

3. Benefits of this integration

4. Automation & CI/CD Tools integration

MARCUS THOMAS - President, QUART Consulting

WHY SHOULD AUTOMATING TEST CASES BE AS EFFORTLESS AS CREATING A MANUAL TEST CASE?

The agile movement has significantly increased the speed of development. But test automation hasn’t kept pace with the agile movement because the industry approach to test automation has remained mostly the same or has changed in a way where the tester has to write code at the same skill level as a developer to keep pace. Even skilled developers struggle with rapid test automation and can’t produce the same productivity that rapid development makes.

Marcus will discuss the following:

• The Codeless Myth
• The POM Bomb
• The B-D-Debacle
• How Shift Down is changing how we approach test automation
• Why automating like a tester is the most effective test automation approach