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 posess.
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.
Anna is a renowned international speaker and recognized expert in Software Test Leadership. In 2015, she founded Test Masters Academy which runs major international events: Test Leadership Congress, Test Masters Online, and ConTEST NYC, which made the list of the best global Software Testing conferences in 2018-2020. Anna held various test management roles for 14+ years, served as the Executive At Large on Association for Software Testing Board of Directors (2016-2017), as the President of AST Quality Leader SIG (2012-2014), and as the Software Test Professionals Community Advisory Board Member (2014 2015). Anna is the founder of several Test/QA meetups in New York.
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.
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
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.
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.
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.
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:
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.
Automating games for desktop or mobile has long been a challenging task. With Appium 2.0, I’ve developed a new plugin that allows you to hook into AltUnityTester, a popular testing tool that integrates with your Unity-based game or application. In this workshop, we’ll start from scratch with a new Unity game and show how to take advantage of the new Appium plugin to write automated tests for the game using the Appium API you already know!
Do you struggle to take notes?
Do you find it difficult to recall details from an important meeting?
Do you wonder if there was a better way to capture ideas and refer notes?
If you asked me these questions 3 years back, my answer to these 3 questions would have been a “Yes”.
I started learning Sketchnotes 2-3 years back and gradually produced work that saw millions of views on social media. I could use Sketchnotes creatively to simplify various aspects of my work.
Visual Thinking is an underrated and an often unexplored skill for professionals. We all are adept at growing our visual thinking capabilities yet we don’t know where/how to get started.
In this workshop, my mission is to help you reduce the fear of representing your ideas with simple drawings. I will using be an art form called Sketchnotes. Sketchnotes are rich visual notes created from a mix of handwriting, drawing, hand-drawn typography, shapes and visual elements like arrows, boxes, and lines.
By the end of this workshop, you will:
1. Understand the importance of Visual thinking.
2. Be able to create a few Sketchnotes on your own.
3. Understand how you can use Sketchnotes to differentiate your work.
Prerequisite: Pen and Paper is enough. A few colored pen and paper woube a plus. A digital note taking app, stylus is not mandatory but it can help, if available.
Gesture-driven devices changed the way we think about interactions. The success of mobile applications depends on how well the interactions are being implemented and in turn its user experience. Touch Actions were ruling the way we automate mobile gestures for quite a while. As of Appium 2.0, we are completely W3C compliant i.e. we have deprecated touch action in favor of Actions API from W3C specifications. In this workshop, we will take you through the ways in which you could automate mobile gestures with and without Appium Plugins.
Evolution of touch gestures
Intro to W3C Actions API
Non standard ways to automate gestures
Intro to Appium 2.0
Appium Gestures plugin
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
Becoming a Code Listener – A products source code can help testers learn about risks, derive great test ideas, and identify factors which could significantly influence software’s performance, behavior, and utility. You don’t need to be a skilled programmer to become a great “Code Listener”.
Testing projects are increasingly time constrained, no matter what the business, technical, organizational, or cultural context. I see many testers base their work exclusively on a products functionality. But testing is intractable. Even the simplest feature potentially has an infinite number of tests. I encourage testers to learn how to focus their efforts. “Code Listening” is a set of skills to help focus testing based on knowledge of software structure. “Code Listeners” sense risks impacted by change.
“Code Listeners” collaborate with programmers, architects and other technical stakeholders engaging in software design, testing, debugging, and troubleshooting – not just finding and reporting bugs.
In this workshop Rob will share several aspects of Code Listening walking through examples taken from real software development projects.
By the end of this workshop testers will have applied code listening skills to discover many great test ideas. Delegates will be well positioned to collaborate with their peers in programming, architecture, and implementation, focusing on risks based on what is really changing in the source code.
Q: Worqference will have live workshops or recorded?
A: Worqference will have live Atomic Workshops in most cases.
Q: What is the duration of the event?
A: Duration of the event would be up to 6-7 hours on all the three days. Session on Day 1 would be in IST morning hours and then in late evening hours. All this while we cover multiple time zones. You can, of course, select and attend only your favourite Workshops.
Q: 4th of March is Friday which is a weekday. Will it be a full day session as well?
A: For 4th March, the sessions will be in Non-working IST hours so that attendees can manage their office and Worqference both. Those who miss, can watch session replay which would be available right after the session.
Q: Can I watch recording if I miss a particular session?
A: During the event duration(all three days), replay of all the completed sessions would be available by default to all the attendees. Post Event also you would be provided with Recording Access.
Q: Will session recording be shared with attendees post the event?
A: Yes, session recordings will be shared with the registrants.
Q: How can I support this event?
A: -You can bring in your testing peers to register for the event and join The Test Tribe community.
– You can spread the word on social media using the hashtag #Worqference and tag us.
Q: When do I get event joining instructions?
A: Event link and instructions will be shared with registered participants 2 days prior to the event
Q: I want my entire team to attend, is there a way to do bulk registrations with Team discount?
A: You can share the list of participants with First Name, Last name, Email address, Country, Organisation, Designation with us at [email protected] and we will bulk register your teams after confirming on possible discount.