A complex product and very little time – you are called in to test it. How do you learn the product and structure your exploration to yield deliverables? Are you confident that you have covered every component or interaction? Applicable for any product/service, stand up for scrutiny and impress all.
There are several screens with multiple sections and each section is related to some other section across multiple screens. You are called in to test the product and after a few minutes of exploration, you discover that your mind is exploding with the combinations possible. How do you explore and document in a way that it is not just understandable to you but to every stakeholder? Which approach will help you cover the multiple interactions and also focus on the individual components right up to the field level?
These techniques are recommended for teams looking to strengthen their test design, improve overall system understanding and be ‘test ready’ for every change that is made to the product.
Ajay Balamurugadas, goes by the handle ‘ajay184f’ in the testing community and is continuously re-inventing his testing methodology. He co-founded Weekend Testing – a worldwide movement for skilled testing, authored multiple books available at bit.ly/booksaj and
bit.ly/ajleanpub. His friends associate the terms – ‘Change Agent, Idea Man, Motivational’ to him. He tweets under @ajay184f and loves to have long conversations on software testing and life in general. He is currently working at GSPANN Technologies, Inc. as Senior
Director – QE. When not testing, he spends time with his wife and two children.
Balaji Ponnada, has about 15 years experience in Software testing, a context driven tester and worked extensively at different phases of test cycle – planning to execution & reporting for various clients. Comes with rich pre-sales experience, understanding client pain points and engineering a solution to address pain points, Conducting proof of concepts. Expert consultant in reviewing client processes via stakeholder interviews to address current testing problems and defining future state of testing to meet business objectives. Extensive experience working with K-12 education systems and leading LMS Moodle, Edmodo and Blackboard.
He also heads IoT research center, Responsible for research, Collateral creation and business development into IoT projects, Defining and implementing Test strategies for IoT systems. Research and collaboration into MQTT, Bluetooth, BLE, Zigbee protocol level testing and implemented devices.
Exploratory Testing is one of the most important skills testers should have. Despite fully knowing the significance of ET, it is often treated as an after-thought or simply as a type of testing one could do on top of everything else that had to be done. Simply relying on automated checks and testing acceptance criteria does not find us the information that stakeholders can use to make decisions about quality/risk. Often times testers struggle with making Exploratory Testing as a part of their test strategy or let’s say in Agile/DevOps teams they find it hard to fit ET in their testing activities.
It is crucial to involve exploratory testing as early as possible in SDLC. And it is very much possible to do so. Session Based Test Management is an approach to manage and structure Exploratory Testing. With SBTM approach testers can better plat ET and also evaluate how their testing efforts are organized.
The responsibility for product quality often falls on software testers. Yet, software testers are often divorced or even excluded from conversations around the cheapest and easiest way to inject quality into the product and the entire software development life cycle, right from the beginning: robust unit test frameworks.
Sure, unit tests are the job of developers, and some developers and companies won’t even think about writing unit tests. So why should software testers know and be able to work with unit tests? As advocates for overall product quality, being able to analyze, discuss, and improve or ask for improvements in unit tests is one of the cheapest ways to advocate for product quality at the earliest stages in the software development process.
In this workshop, using an open source python repository, testers will learn:
By the end of this hands-on workshop, testers will understand how to read source code, determine what tests are in the code, and work with developers and dev managers to help develop more robust unit testing frameworks and decrease manual and front-end test automation needs.
Automation is one of the challenges which Testers are facing every day and still most of us are unable to build a reliable script and create an environment where we can easily debug and resolve the issue, capture screenshots/videos of the entire flow, control the execution speed, store execution reports, handle flaky cases, and this list goes on and on.
We invest a lot of time to build the perfect framework as per our needs and we still end up scrapping it after a couple of years. So, I started looking for a tool that can take care of all the ad-hoc tasks and I can solely focus on adding test cases to my suite, and soon I stumbled upon Cypress.
Cypress is a tool that helps us to write Unit, Integration, and End to End test cases for UI and API. So it can be used by a Developer or a Tester.
Cypress is bundled with features like
Have you heard of Contract Testing? Are you currently working on a project involving multiple data providers? Do you want to make sure that consumers and data providers can catch broken changes earlier on in your pipeline? If the answer to these questions is yes, then this workshop is for you! In this workshop, I’ll explain what contract testing is, how it’s different from other types of testing, its features and benefits. No workshop is complete without a live demonstration so I’ll also be walking you through how to setup both consumer and provider contract testing using Pact JS with Jest.
Digital Accessibility is no longer an afterthought. It has become an important facet in software design and engineering, given the rapid digital transformation that the world is witnessing. Also, it is no longer limited to just a specific accessibility group that is responsible in enabling digital inclusion. Right from business teams to developers to functional testers, everyone needs to be sensitized on what is accessibility and how to make it a reality in products built for end user consumption. Industry standards are easily available today for global consumption that define how to embrace digital accessibility in mobile and non-mobile worlds. This workshop will give the right first view into the world of accessibility where you will go back with an understanding of the varied guidelines of WCAG (one the leading global accessibility standards) along with test techniques, tools and practices.
Introduction: 20 mins
Guidelines: 40 mins
QE: 20 mins
You might have heard me talk a lot about how waits can improve the reliability of your Selenium automated tests. But maybe you did not clearly envision how you can apply them in your own tests. Or what specific wait methods can be created for specific page interactions. In this workshop I will go over lots of examples where we will update existing non-wait tests to use waits. We will see what makes sense to wait for in each example, and how we can create the best wait method to handle each scenario.
Whether you are a seasoned manager, a senior tester tasked with leading a team or a project, a prodigy that wants to get their career rolling, or simply someone who is serious about their professional development, you want to create a career that you are passionate about.
As your expertise grows, you are assigned a higher level of responsibility, and you are expected to demonstrate leadership in your daily work – in one way or another. That could be influencing, defining strategy, coaching or leading the team (whether your direct reports or your peers) in a new direction.
Also, your professional community is looking up to you – there are expectations to see you as a role model, a thought leader, a person who can share knowledge and teach others in the expertise they possess.
These new levels of responsibility sometimes leave you with questions: Am I doing the right thing? Am I really the expert people think I am? Do I possess the level of knowledge and skills that’s necessary to make right decisions? Am I applying my best in where I am or should I put my efforts elsewhere to achieve the career satisfaction I want and deserve?
This workshop is designed to help you identify your REAL strengths, take a close look at your leadership style, and equip you with the tools that will enable you to achieve your next career goals.
Overview & Purpose:
The key goal of any bug reporter is to provide high-quality information, well written, to help stakeholders make wise decisions about which bugs to fix. Although most testers find and report bugs in their day-to-day work yet only a few are very good at it. This workshop is designed to help you be a Good Bug Advocate.
Principles Driving This Workshop:
Why someone should care about this Workshop:
Overview of Topics to be Covered:
Topic Wise Breakdown: