<< HOME

SPEAKERS – USA Season 4

AGENDA >>

DAVID MELLO - Manager of software engineering, Ultimate Kronos Group

GETTING STARTED AUTOMATING A MINIMUM ACCESSIBILITY TEST PLAN

Building accessible websites are important, but it hasn't been a focus for many existing ones until recently. This leaves many test professionals facing the challenge of how to incorporate testing a requirement that wasn't part of the product's initial design. The minimum accessibility test plan is a more natural way to get started by treating it like a feature iterated on overtime.

https://www.davidmello.com

SHIKHA HANDA - Sr. Manager Quality Assurance, Liberty Latin America

DIGITAL TRANSFORMATION IN QUALITY ASSURANCE – FOLLOWING THE CHANGE IN QA

Digital Transformation means the adoption of the digital technology to transform services or businesses through replacing non-digital or manual processes with digital processes or replacing older digital technology with newer digital technology. Quality Assurance function being the heart of any successful delivery also needs to adapt to this industry wide change.

Below are some of the key areas applicable for QA to transform:
a) Collaborate and Aid Product owners/businesses in the discovery/requirement gathering workshops. Use of modern collaborative tools replacing lengthy product specification documents.
b) Scripting the Behavior and Acceptance Tests leading to BDD/ATDD developments instead of writing acceptance after development is complete
c) Progression Test Automation followed by Regression Automation instead of automating just Regression testing
d) Continuous Integration, Testing, and Deployment
e) Automation for scaling test environments including performance and security testing
f) Continuous Monitoring

BJORN EDWIN - Principal DevOps Consultant, Liatrio

CONTINUOUS TESTING: LAST BORN CHILD OF DEVOPS

Many organizations see DevOps as a challenge to be solved for application development & delivery and often discount the testing and quality aspect of DevOps which is very important in your DevOps transformation journey.

At its core DevOps is about bringing all the right people, process and tools to help teams and organizations deliver faster and safer, my emphasis for this talk would be on safety. Speed is mostly the first and the easiest to accomplish in software delivery compared to quality. Quality is the foundation for safety for any product that is engineered and delivered, quality should be embedded in your software development and delivery process to sustain speed and delivery.

DevOps is a cultural movement and it is inevitable to create a culture of continuous testing and quality as your team and your organization embrace your DevOps transformation journey.

RATNA JANJANAM - Senior Member Of Technical Staff, Salesforce

STORY OF REGRESSION TESTING- ALL ABOUT REGRESSION TESTING AND HOW IT IS DONE

Story of Regression Testing - All about Regression testing how it is done

Dictionary meaning of the word "regression" is "the return to a former or less developed state." So, testing done with the aim of catching any regressions in an already tested functionality is called Regression Testing.

During this Talk We will be Covering the fundamentals and complexities of Regression Testing including what, why, how, where, when and who with examples. Throwing light on its importance, discussing the solutions to general problems, best practices and more.

Also, a detailed discussion on automated regression testing, how to make it beneficial and how to stay away from the common pitfall

ANDREW KNIGHT - Lead Software Engineer in Test, PrecisionLender, a Q2 Company

THE SCREENPLAY PATTERN: BETTER INTERACTIONS FOR BETTER AUTOMATION

Automating interactions for tests is hard. For the past decade, the primary way to automate web/mobile UI interactions has been the Page Object Model. Unfortunately, page objects do not scale well. By design, they allow lots of code duplication and unsafe activity. The Screenplay Pattern is a much better pattern for handling interactions. In Screenplay, Actors use Abilities to perform Interactions. In this talk, I'll introduce the Screenplay Pattern using the .NET implementation named Boa Constrictor. I'll show how to write a simple search engine test in C# using Screenplay calls with Boa Constrictor. By the end of this talk, you'll be empowered to make better interactions for better automation!

RAMAPRIYA RAJU - Global Director - M&A,Divestitures Testing, IBM

WIFU - WITH AUTOMATION, IN AGILE, FOR API & WEB TESTING, USE DATA, AI, TOOLS: LESSONS FROM THE AFRICAN WILDERNESS

Every day, we draw inferences knowingly or unknowingly from our experience of living.

My many visits to Africa have been a pivotal learning experience towards my understanding of how some things are very similar across the animal kingdom. During this discussion, I will be talking about how I took lessons from the gracious African wilderness, specifically to improve my approach to Automation, Agile, API and Web testing using Data, AI and tools within large test programs. Session focus will also be on takeaways that can help anyone to leverage some of the basic methods already available in the IT industry today and how to continuously reuse them with minimal effort. I will elaborate on how these methods draw their inspiration from our wilderness partners. I look forwards sharing my experiences, both in the testing world and travels across Africa.

MUHAMMEDALI BHARMAL - IoT & Enterprise Test Architect, Eaton

IOT ENTERPRISE SYSTEMS RELIABILITY AND PERFORMANCE TESTING

System and Software Reliability and performance is non-negotiable expectation for every product.

Systems Reliability and Performance Testing is also the most challenging and time consuming task.

Traditionally these tests are executed towards the end, during final regression testing of a product. Very often the issues found by these tests will lead to major design changes that will impact release deadlines.

NIKOLAY ADVOLODKIN - Sr Solutions Architect, Sauce Labs

A CI PIPELINE TO TEST THE COVERAGE GAPS

In 2021 we're still spending so much time talking about functional browser test automation. When in fact, this is just a tiny piece of the entire testing domain. Many companies across the globe see this as a challenge and as a result are shifting-left and right. Testing requires a cohesive strategy of a mix of tests - from functional, to unit, API, visual and even performance. Unfortunately, we're not spending enough time talking about how to have a more cohesive test strategy.

In this presentation, we will create a comprehensive test strategy, using effective test tools, and execute the tests through a CI pipeline. We will start by looking at a web app and understanding its coverage needs. Afterward, we will start tackling the coverage gaps with different types of tests. We will write some unit tests to test functionality. We will write some browser tests for functional browser coverage. We will also use visual and performance tests to gauge the quality of the end user experience. Finally, we will tie this all together into a CI Pipeline that executes multiple times per day on every single push and pull request.

CHRIS HYDE - QA Manager, Consultant

AUTOMATED & MANUAL TESTING - HOW TO MAXIMIZE BOTH, TOGETHER

In today's world of lightning-quick delivery and shrinking margins for error, Automated testing is all the rage. However, Manual testing remains an important part of the testing landscape. The most important testing in a project/company must be done first by the most senior manual resources, as this is where your unique skill set is most valuable. We can never automate every test, nor does it make sense to! There are some tests where you want the experts using the software as a human would, plain and simple.

Testers think differently, in a good way, and often find issues that were never considered (and, frankly, that's what we're paid for!). The perfect marriage for automated and manual testing is where one complements the other; not where one occurs separately from the other.. You have manual testers performing exploratory testing and helping to define what is automated, and more importantly, what the automated tests actually should test!

GEORGE UKKURU - Head of Quality Engineering, UST

DATA PROVISIONING USING BOTS

Synthetic Test Data generation facilitates data creation that is realistic and model-driven, decreasing delays for test data delivery and improving applications' quality. Synthetic test data generation and bots accelerate the test cycle by reducing wait time by eliminating dependencies. The bots can help engineers working in Agile Sprint teams to provision test data to environments. The bot's self-service capabilities reduce data provisioning cycle time provide data in various formats.

RAMESH KUMAR BOMMARAJU - Test Automation Architect, Qentelli Inc

INTEGRATING AUTOMATED TESTING INTO DEVOPS AND AGILE

Speaker will demonstrate a couple examples of integrating automated tests into CICD pipelines. This session would discuss common challenges in integrating automated tests into DevOps and possible solutions.

SRILU BALLA - QA Lead, Slalom

TESTING A BROKEN BUILD

Have you ever found yourself in a situation where you identified the new build you got is broken, you notify the Developer about it and get a reply that it will some time before they can get you a new build? Right then a senior member of the team suggests to you, to test the build further to find any issues before you get the good build, (her opinions is this saves). You explain it is a waste of time to test with a broken build or bad data since you will get false negatives which will need to be cleaned up in future which will cost time and chaos. The senior member suddenly stops suggesting testing and give you a look that implies “you are lazy, smart ass, know it all”.

Have you ever found yourself in a situation where you could log into any customer account in Production without even knowing the password? You report it and the developer closes it saying that is how the new architecture works now.

Have you ever found yourself in a situation where you found un-encrypted passwords? So, you report it and the tester who tested the feature in the past closes the ticket with the justification that “un-encrypted password” was not mentioned in the requirements and so he did not miss the bug, or this is not a bug.

HEATH HOWE - QA Automation Theorist, Theorem, LLC

THE SECRET SAUCE TO CONTINUOUS DEPLOYMENT TESTING

Add a little spice to your day and kick that software change out the door without a single set of eyes on it. Do it multiple times a day and you might think it would cause an ulcer! No need for antacids or a doctor, just come to this session to find out all the juices and spices necessary to make that delicious secret sauce of automated tests that allows for continuous deployments of both microservices and monolithic applications. These concepts can be applied to any tools that perform automated tests in any CI/CD system.

PRIYAMVADHA RAVI - Senior Quality Test analyst, LexisNexis

CONTINUOUS INTEGRATION MOBILE APP TESTING WITH JENKINS AND TESTRAIL

In the world of Mobile app development the Intensity and the flexibility of the changes are quite unique. These changes call for a continuous integration of the Mobile app test execution with the builds or a scheduled nightly job on the execution.

Further more, In order to update the execution results with Test Management tool like TestRail is a great combination. It can give better accessibility to View the progress, Metrics collection from TestRail tool.

ERIC MONTGOMERY - System Test Engineer, Progressive Insurance

WORKSHOP: HOW TO APPLY TEST TECHNIQUES TO REQUIREMENTS

Defects found earlier in development lifecycles are faster and easier to correct. Testers have tools and techniques they use to break apart a system to learn about its behaviors. What if those same techniques were applied directly to the requirements to create a solid foundation before we begin programming?

In this interactive session, Eric Montgomery will lead a conversation on several testing techniques and how to apply them to a requirements document. Come prepared to analyze mock requirements and discuss how our testing prowess can help us find defects before a single line of code has been written.

<< HOME
AGENDA >>