Finding time to learn test techniques, mentor other testers, grow application knowledge, and cross-train your team members is a daunting task with a complicated recipe. What if you could do these things while testing and finding bugs? Enter Pair Testing. What’s that? Well, maybe you’ve heard of pair programming. It’s like that—only you’re testing rather than programming. And it’s the secret sauce of agile testing because it makes your routine, bland testing so much more fun! Testers on Jess Lancaster’s team use pair testing not only to make better software but also to foster better relationships along the way. Jess explores why pairing works, how to run an effective pairing session, and just how easy it is to get started with pairing. Armed with Jess’ easy-to-use Pair Testing recipe card, plan your first pairing encounter so you are ready to roll when you get back to the office. This sounds easy enough, but you know there will be mistakes when you try it. Jess has you covered there, too. Learn his team’s pairing mistakes and the things he did to improve their pairing sessions.
Reduce Development Cost with Test Driven Developmentsthicks14
A collaboration between NetServ Applications and Celtic Testing Experts on Test Driven Development and Design. This presentation demonstrates how an organization can reduce development cost by implementing TDD.
Scaling Scrum hurts. There are coordination challenges, technical challenges, and communication challenges. But there are some patterns you can use to overcome these pains. This is an experience report from a 30+ person 5 team scaled Scrum project. It gives you practical tips on what to try if you experience any of the pains we did when we scaled Scrum.
Continuous Integration: Getting your department to drink the Kool-AidJenKnight
Everyone wants automated regression, automated builds, and single click deployments. Who wouldn’t want day to day development blockers eliminated. However, getting these things happening in your office might often face fierce resistance. Here is how one small department banded together for success.
Presented by Jen Knight, Michael Benning
Reduce Development Cost with Test Driven Developmentsthicks14
A collaboration between NetServ Applications and Celtic Testing Experts on Test Driven Development and Design. This presentation demonstrates how an organization can reduce development cost by implementing TDD.
Scaling Scrum hurts. There are coordination challenges, technical challenges, and communication challenges. But there are some patterns you can use to overcome these pains. This is an experience report from a 30+ person 5 team scaled Scrum project. It gives you practical tips on what to try if you experience any of the pains we did when we scaled Scrum.
Continuous Integration: Getting your department to drink the Kool-AidJenKnight
Everyone wants automated regression, automated builds, and single click deployments. Who wouldn’t want day to day development blockers eliminated. However, getting these things happening in your office might often face fierce resistance. Here is how one small department banded together for success.
Presented by Jen Knight, Michael Benning
This presentation aims of covering all the issues related to PAIR-TESTING , a module of SOFTWARE TESTING PARADIGM. I would like to thanks all my friends and mentors for bringing up this presentation in such a good and effective way.
Test Estimation Hacks: Tips, Tricks and Tools WebinarQASymphony
In this webinar, Matt Heusser explains how not only how to deal with tough questions, but how to prepare and defend estimates that stand up to scrutiny. The conversation includes six estimating models - comparison, functional decomposition, timeboxed, and prediction, along the Guru Method and, perhaps, a little on #NoEstimates.
Don’t miss this opportunity to learn:
Learn the common mistakes in software test estimation
How Testing is different than linear tasks like development (and how to talk about it)
Learn what goes wrong in discussions about schedule
An explanation of ways to estimate for test - by comparison, functional decomposition, timeboxing, prediction and the guru method
How to recognize when you are actually in test negotiation, not test estimation...and what to do about it
Matt Heusser will discusses these topics and much, much more! Watch now: http://pi.qasymphony.com/test-estimation-hacks-webinar-lp057
A Rapid Introduction to Rapid Software TestingTechWell
You're under tight time pressure and have barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Michael Bolton introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and "minds-on" exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Michael to see how rapid testing focuses on both the mind set and skill set of the individual tester who uses tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.
Agile Testing examines software from the customer point of view, and requires that the entire team tests the product to deliver value.
According to James Bach, testing is the questioning of a product in order to evaluate it.
Agile Testing takes the fundamentals of software testing, and provides options for testing products delivered in Agile workflows. It focuses on early involvement of testers, defect prevention, quick feedback loops, test automation, and exploratory testing.
This presentation will start with selected ideas from Agile Testing, and
More Agile Testing, then Dag Rowe will tie in ideas from other practices and practitioners, notably BDD and Specification by Example
A test strategy is the set of ideas that guides your test design. It's what explains why you test this instead of that, and why you test this way instead of that way. Strategic thinking matters because testers must make quick decisions about what needs testing right now and what can be left alone. You must be able to work through major threads without being overwhelmed by tiny details. James Bach describes how test strategy is organized around risk but is not defined before testing begins. Rather, it evolves alongside testing as we learn more about the product. We start with a vague idea of our strategy, organize it quickly, and document as needed in a concise way. In the end, the strategy can be as formal and detailed as you want it to be. In the beginning, though, we start small. If you want to focus on testing and not paperwork, this approach is for you.
This has been shared with many outsiders, so I guess good to share it here. This is a barometer we have used to have software development teams assess their own functioning within the FSC whole. It is not necessarily accurate for other companies and environments, but certainly should be inspirational. Part of the credit should go to the awesome GM team that helped me hone it.
Presented in BSPIN Conference (http://bspin.org/conference2014/) on "Succeeding in SMAC World". Had great interactions and glad to see great interest on Agile Testing concepts with Participants.
Ken Johnston - Big Bugs That Got Away - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Big Bugs That Got Away by Ken Johnston . See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Agile Testing Days -Trends and future in testing 2017Derk-Jan de Grood
Today I gave a presentation at the Agile Testing Days. The room was packed and we talked about the way the testing profession in evolving.
5 years ago the Dutch Test Association published a book that described the changes in the testing profession. I was one of the 7 authors and we organized a few workshops on the theme. Last may we hosted a retrospective workshop during which the participants evaluated the 2012 predictions. Key question during this workshop was: What is the status of the profession and what skills and role should a tester take in order to add value and a job.
In my 2017 ATD presentation I shared the results that of this workshop. I shared the highlights of the book, told what predictions were correct and which were incorrect. But most of all I will shared the opinion of or fellow testers: What do roles do they have now, and what roles do they expect to have in 5 years from now.
Join this session if you are sometimes worried about the sustainability of your role, if you want to specialize yourself but wonder what specialisms are a safe bet, if you want to stay ahead of the game and be prepared for the future.
Continuous Deployment and Testing Workshop from Better Software WestCory Foy
In this workshop from the 2015 SQE Better Software West conference, Cory Foy details the Continuous Paradigm companies are embracing - including Continuous Integration, Continuous Deployment, and Continuous Testing. This presentation was co-created by Jared Richardson.
What are the latest trends and learning for Software Testers.pdfAnanthReddy38
As software development continues to evolve and become more complex, software testers are facing new challenges and opportunities. Here are some of the latest trends and learning for software testers to keep up with the demands of the industry.
This presentation aims of covering all the issues related to PAIR-TESTING , a module of SOFTWARE TESTING PARADIGM. I would like to thanks all my friends and mentors for bringing up this presentation in such a good and effective way.
Test Estimation Hacks: Tips, Tricks and Tools WebinarQASymphony
In this webinar, Matt Heusser explains how not only how to deal with tough questions, but how to prepare and defend estimates that stand up to scrutiny. The conversation includes six estimating models - comparison, functional decomposition, timeboxed, and prediction, along the Guru Method and, perhaps, a little on #NoEstimates.
Don’t miss this opportunity to learn:
Learn the common mistakes in software test estimation
How Testing is different than linear tasks like development (and how to talk about it)
Learn what goes wrong in discussions about schedule
An explanation of ways to estimate for test - by comparison, functional decomposition, timeboxing, prediction and the guru method
How to recognize when you are actually in test negotiation, not test estimation...and what to do about it
Matt Heusser will discusses these topics and much, much more! Watch now: http://pi.qasymphony.com/test-estimation-hacks-webinar-lp057
A Rapid Introduction to Rapid Software TestingTechWell
You're under tight time pressure and have barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Michael Bolton introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and "minds-on" exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Michael to see how rapid testing focuses on both the mind set and skill set of the individual tester who uses tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.
Agile Testing examines software from the customer point of view, and requires that the entire team tests the product to deliver value.
According to James Bach, testing is the questioning of a product in order to evaluate it.
Agile Testing takes the fundamentals of software testing, and provides options for testing products delivered in Agile workflows. It focuses on early involvement of testers, defect prevention, quick feedback loops, test automation, and exploratory testing.
This presentation will start with selected ideas from Agile Testing, and
More Agile Testing, then Dag Rowe will tie in ideas from other practices and practitioners, notably BDD and Specification by Example
A test strategy is the set of ideas that guides your test design. It's what explains why you test this instead of that, and why you test this way instead of that way. Strategic thinking matters because testers must make quick decisions about what needs testing right now and what can be left alone. You must be able to work through major threads without being overwhelmed by tiny details. James Bach describes how test strategy is organized around risk but is not defined before testing begins. Rather, it evolves alongside testing as we learn more about the product. We start with a vague idea of our strategy, organize it quickly, and document as needed in a concise way. In the end, the strategy can be as formal and detailed as you want it to be. In the beginning, though, we start small. If you want to focus on testing and not paperwork, this approach is for you.
This has been shared with many outsiders, so I guess good to share it here. This is a barometer we have used to have software development teams assess their own functioning within the FSC whole. It is not necessarily accurate for other companies and environments, but certainly should be inspirational. Part of the credit should go to the awesome GM team that helped me hone it.
Presented in BSPIN Conference (http://bspin.org/conference2014/) on "Succeeding in SMAC World". Had great interactions and glad to see great interest on Agile Testing concepts with Participants.
Ken Johnston - Big Bugs That Got Away - EuroSTAR 2010TEST Huddle
EuroSTAR Software Testing Conference 2010 presentation on Big Bugs That Got Away by Ken Johnston . See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Agile Testing Days -Trends and future in testing 2017Derk-Jan de Grood
Today I gave a presentation at the Agile Testing Days. The room was packed and we talked about the way the testing profession in evolving.
5 years ago the Dutch Test Association published a book that described the changes in the testing profession. I was one of the 7 authors and we organized a few workshops on the theme. Last may we hosted a retrospective workshop during which the participants evaluated the 2012 predictions. Key question during this workshop was: What is the status of the profession and what skills and role should a tester take in order to add value and a job.
In my 2017 ATD presentation I shared the results that of this workshop. I shared the highlights of the book, told what predictions were correct and which were incorrect. But most of all I will shared the opinion of or fellow testers: What do roles do they have now, and what roles do they expect to have in 5 years from now.
Join this session if you are sometimes worried about the sustainability of your role, if you want to specialize yourself but wonder what specialisms are a safe bet, if you want to stay ahead of the game and be prepared for the future.
Continuous Deployment and Testing Workshop from Better Software WestCory Foy
In this workshop from the 2015 SQE Better Software West conference, Cory Foy details the Continuous Paradigm companies are embracing - including Continuous Integration, Continuous Deployment, and Continuous Testing. This presentation was co-created by Jared Richardson.
What are the latest trends and learning for Software Testers.pdfAnanthReddy38
As software development continues to evolve and become more complex, software testers are facing new challenges and opportunities. Here are some of the latest trends and learning for software testers to keep up with the demands of the industry.
Exploratory Testing: Make It Part of Your Test StrategyTechWell
Developers often have the unfortunate distinction of not thoroughly testing their code. It’s not that developers do not understand how to test well; it’s just that often they have not had an opportunity to understand how the product works. Kevin Dunne maintains that implementing a team-wide exploratory testing initiative can help build the collaboration and knowledge sharing needed to elevate all team members to the level of product master. Exploratory testing can be performed by anyone, but the real challenge is making sure that the process is properly managed, documented, and optimized. Kevin describes the tools necessary to drive a deeper understanding of software quality and to implement an effective and impactful exploratory testing practice. Creating better software is not just about writing code more accurately and efficiently; it is about delivering value to the end user. Well-executed exploratory testing helps unlock this capability across the entire development team.
Basically this slid will help to Learn software quality testing on scratch level.
Software testing is the quality measures conducted to provide stakeholders with information about the quality of the product or service. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. It is an important part of the entire Software Development ensuring that the functionalities of the system are tested to the finest and assures the quality, correctness and completeness of the product. Software testing, depending on the testing method employed, can be implemented at any time in the development process.
Stages of testing:
o Test planning
o Test Analysis
o Test verification & Construction
o Test execution
o Defect tracking and management
o Quality Analysis Bug tracking
o Report
o Final testing & implementation
Agile Testing: Best Practices and Methodology Zoe Gilbert
Get more control and bug free code to ensure no crash in your application, employ agile testing which restricts your testing efforts for repetitive task. Read this blog to understand details for agile testing including all type of testing methods and best practices.
How to Create Effective Test Plans and Test Cases for Software TestingOprim Solutions
It is important to test any new software before it goes live. This helps improve IT security and identifies any issues.
Also, you can opt for an expert to do the best software testing and planning job for you. At Oprim, we have a dedicated software testing team to identify and debug issues in any software making them flawless.
Connect today to partner with us- https://oprim.ca/ | info@oprim.ca | +18335567746
A test strategy is the set of ideas that guides your test design. It's what explains why you test this instead of that, and why you test this way instead of that way. Strategic thinking matters because testers must make quick decisions about what needs testing right now and what can be left alone. You must be able to work through major threads without being overwhelmed by tiny details. James Bach describes how test strategy is organized around risk but is not defined before testing begins. Rather, it evolves alongside testing as we learn more about the product. We start with a vague idea of our strategy, organize it quickly, and document as needed in a concise way. In the end, the strategy can be as formal and detailed as you want it to be. In the beginning, though, we start small. If you want to focus on testing and not paperwork, this approach is for you.
Guided by Optimizely's training team, participants will leave this session armed with the tools and resources to enable their organization with the technical and strategic skills needed to build a successful optimization program. Through modeling of best-practices and facilitation techniques, participants will gain a strong foundation in the three key Optimizely training modules: Optimizely X - Platform Training, Strategy Ideation, and Hypothesis Creation, and Result Review and Analysis.
This workshop focuses on how to facilitate and what to expect before, during, and after a training. We will discuss the key learning objectives, common questions and takeaways, and follow-up resources from each module.
Join us and learn how to deliver powerful Optimizely trainings to enable your team.
Tips and Best Practices for Learning Software Testing
To accelerate your learning process and achieve success in testing, consider the following tips and best practices:
Start with the Basics and Build a Strong Foundation
Begin by mastering the fundamental concepts of software testing. Understand the different types of testing, testing methodologies, and testing levels. This foundation will serve as a solid base for further learning and skill development.
Join Testing Communities and Forums
Engage with the testing community by joining online forums, attending webinars, or participating in local meetups. Connecting with fellow testers allows you to exchange knowledge, gain insights from experienced professionals, and stay updated with the latest trends and industry practices. Active participation in communities fosters learning and networking opportunities.
Stay Updated with Industry Trends and Tools
The field of software testing is constantly evolving. Stay updated with the latest industry trends, emerging technologies, and testing tools. Follow influential testing blogs, subscribe to newsletters, and explore industry publications. Being aware of the current advancements helps you adapt to changing testing methodologies and enhances your marketability.
Network and Collaborate with Other Testers
Building a network of like-minded testers is invaluable. Connect with other testers through social media platforms like LinkedIn or Twitter. Engage in discussions, share your experiences, and learn from the experiences of others. Collaborating with fellow testers fosters knowledge sharing, provides different perspectives, and broadens your understanding of software testing.
Embrace Continuous Learning and Skill Development
Testing is a dynamic field, and continuous learning is essential for professional growth. Dedicate time to explore new testing techniques, take advanced courses, and acquire additional certifications. Continuously honing your skills keeps you competitive in the job market and opens doors to new opportunities.
Conclusion:
Learning software testing is an exciting journey that requires dedication, continuous learning, and practical experience. By understanding the different learning approaches, acquiring essential skills, following effective learning strategies, and avoiding common mistakes, you can become a proficient software tester. Embrace the challenges, stay curious, and never stop learning to thrive in this dynamic field.
FAQ's :
Q: Is coding knowledge necessary to learn software testing?
A: While coding knowledge is not mandatory, it is highly beneficial. Basic programming skills allow you to create automated test scripts and understand the software under test more comprehensively.
Q: How can I stay updated with the latest trends in testing?
A: To stay updated, follow industry-leading blogs, subscribe to newsletters, attend webinars and conferences, and participate in testing communities.
COURSE IS NOW FULLY AVAILABLE AND LIVE HERE: https://goo.gl/gVukvc
This is the first section of six parts to cover what you need to learn about ISTQB foundations exam. Broken down into pieces and examples to pass. Check out more on my blog: https://www.rogeriodasilva.com/
Similar to Pairing: The Secret Sauce of Agile Testing (20)
Do you ever feel you have lost confidence in your own abilities? Why does this happen? Isabel Evans spends a lot of time painting. Someone once commented, “Why are you doing this, when you are not very good at it?” And gradually she stopped drawing and painting, after being intimidated by a conventional vision of what good art should look like. At the same time, she experienced a parallel loss of confidence in her professional abilities. Attempting creative pursuits like drawing and painting is essential to cognitive, emotional, creative abilities and she began to understand the correlation between her creative activities and her confidence. Making errors, being wrong, failing – that is a generous gift we receive when we practice outside our skill level. By staying in a comfort zone and repeating successes, we stagnate. As Isabel started to create again she thought “I don’t feel good at it, I do feel good doing it” The difference was that she was learning, having ideas and the act of re-engaging with failure, together with the comradeship of friends and colleagues, including at Women Who Test, Isabel has regained her confidence in her professional abilities, and been able to reboot her career and joy. Join Isabel to share a journey from self-perceived failure, to recovery and renewed learning.
Instill a DevOps Testing Culture in Your Team and Organization TechWell
The DevOps movement is here. Companies across many industries are breaking down siloed IT departments and federating them into product development teams. Testing and its practices are at the heart of these changes. Traditionally, IT organizations have been staffed with mostly manual testers and a limited number of automation and performance engineers. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add greater value to the business. DevOps really starts with testing. Join Adam Auerbach as he explains what DevOps is and how it relates to testing. He describes how testing must change from top to bottom and how to access your own environment to identify improvement opportunities. Adam dives into practices like service virtualization, test data management, and continuous testing so you can understand where you are now and identify steps needed to instill a DevOps testing culture in your team and organization.
Test Design for Fully Automated Build ArchitectureTechWell
Imagine this … As soon as any developed functionality is submitted into the code repository, it is automatically subjected to the appropriate battery of tests and then released straight into production. Setting up the pipeline capable of doing just that is becoming more and more common and something you need to know about. But most organizations hit the same stumbling block—just what IS the appropriate battery of tests? Automated build architectures don't always lend themselves well to the traditional stages of testing. In this hands-on tutorial, Melissa Benua introduces you to key test design principles—applicable to organizations both large and small—that allow you to take full advantage of the pipeline's capabilities without introducing unnecessary bottlenecks. Learn how to make highly reliable tests that run fast and preserve just enough information to let testers and developers determine exactly what went wrong and how to reproduce the error locally. Explore ways to reduce overlap while still maintaining adequate test coverage. Take back ideas about which test areas could benefit from being combined into a single suite and which areas could benefit most from being broken out altogether.
System-Level Test Automation: Ensuring a Good StartTechWell
Many organizations invest a lot of effort in test automation at the system level but then have serious problems later on. As a leader, how can you ensure that your new automation efforts will get off to a good start? What can you do to ensure that your automation work provides continuing value? This tutorial covers both “theory” and “practice”. Dot Graham explains the critical issues for getting a good start, and Chris Loder describes his experiences in getting good automation started at a number of companies. The tutorial covers the most important management issues you must address for test automation success, particularly when you are new to automation, and how to choose the best approaches for your organization—no matter which automation tools you use. Focusing on system level testing, Dot and Chris explain how automation affects staffing, who should be responsible for which automation tasks, how managers can best support automation efforts to promote success, what you can realistically expect in benefits and how to report them. They explain—for non-techies—the key technical issues that can make or break your automation effort. Come away with your own clarified automation objectives, and a draft test automation strategy to use to plan your own system-level test automation.
Build Your Mobile App Quality and Test StrategyTechWell
Let’s build a mobile app quality and testing strategy together. Whether you have a web, hybrid, or native app, building a quality and testing strategy means (1) knowing what data and tools you have available to make agile decisions, (2) understanding your customers and your competitors, and (3) testing your app under real-world conditions. Jason Arbon guides you through the latest techniques, data, and tools to ensure the awesomeness of your mobile app quality and testing strategy. Leave this interactive session with a strategy for your very own app—or one you pretend to own. The information Jason shares is based on data from Appdiff’s next-gen mobile app testing platform, lessons from Applause/uTest’s crowd, text mining hundreds of millions of app store reviews, and in-depth discussions with top mobile app development teams.
Testing Transformation: The Art and Science for SuccessTechWell
Technologies, testing processes, and the role of the tester have evolved significantly in the past few years with the advent of agile, DevOps, and other new technologies. It is critical that we testing professionals evaluate ourselves and continue to add tangible value to our organizations. In your work, are you focused on the trivial or on real game changers? Jennifer Bonine describes critical elements that help you artfully blend people, process, and technology to create a synergistic relationship that adds value. Jennifer shares ideas on mastering politics, maneuvering core vs. context, and innovating your technology strategies and processes. She explores how new processes can be introduced in an organization, what the role of organizational culture is in determining the success of a project, and how you can know what tools will add value vs. simply adding overhead and complexity. Jennifer reviews critically needed tester skills and discusses a continual learning model to evolve your skills and stay relevant. This discussion can lead you to technologies, processes, and skills you can stake your career on.
We’ve all been there. We work incredibly hard to develop a feature and design tests based on written requirements. We build a detailed test plan that aligns the tests with the software and the documented business needs. And when we put the tests to the software, it all falls apart because the requirements were changed without informing everyone. Mary Thorn says help is at hand. Enter behavior-driven development (BDD), and Cucumber and SpecFlow, tools for running automated acceptance tests and facilitating BDD. Mary explores the nuances of Cucumber and SpecFlow, and shows you how to implement BDD and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber and SpecFlow bridge the communication gap between business stakeholders and implementation teams. In this workshop, practice writing feature files with the best practices Mary has discovered over numerous implementations. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, Mary has answers for you.
Develop WebDriver Automated Tests—and Keep Your SanityTechWell
Many teams go crazy because of brittle, high-maintenance automated test suites. Jim Holmes helps you understand how to create a flexible, maintainable, high-value suite of functional tests using Selenium WebDriver. Learn the basics of what to test, what not to test, and how to avoid overlapping with other types of testing. Jim includes both philosophical concepts and hands-on coding. Testers who haven't written code should not be intimidated! We'll pair you up to make sure you're successful. Learn to create practical tests dealing with advanced situations such as input validation, AJAX delays, and working with file downloads. Additionally, discover when you need to work together with developers to create a system that's more easily testable. This tutorial focuses primarily on automating web tests, but many of the same concepts can be applied to other UI environments. Demos and labs will be in C# and Java using WebDriver. Leave this tutorial having learned how to write high-value WebDriver tests—and stay sane while doing so.
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Eliminate Cloud Waste with a Holistic DevOps StrategyTechWell
Chris Parlette maintains that renting infrastructure on demand is the most disruptive trend in IT in decades. In 2016, enterprises spent $23B on public cloud IaaS services. By 2020, that figure is expected to reach $65B. The public cloud is now used like a utility, and like any utility, there is waste. Who's responsible for optimizing the infrastructure and reducing wasted expenses? It’s DevOps. The excess expense, known as cloud waste, comprises several interrelated problems: services running when they don't need to be, improperly sized infrastructure, orphaned resources, and shadow IT. There are a few core tenets of DevOps—holistic thinking, no silos, rapid useful feedback, and automation—that can be applied to reducing your cloud waste. Join Chris to learn why you should include continuous cost optimization in your DevOps processes. Automate cost control, reduce your cloud expenses, and make your life easier.
Transform Test Organizations for the New World of DevOpsTechWell
With the recent emergence of DevOps across the industry, testing organizations are being challenged to transform themselves significantly within a short period of time to stay meaningful within their organizations. It’s not easy to plan and approach these changes considering the way testing organizations have remained structured for ages. These challenges start from foundational organizational structures and can cut across leadership influence, competencies, tools strategy, infrastructure, and other dimensions. Sumit Kumar shares his experience assisting various organizations to overcome these challenges using an organized DevOps enablement framework. The framework includes radical restructuring, turning the tools strategy upside down, a multidimensional workforce enablement supported by infrastructure changes, redeveloped collaborations models, and more. From his real world experiences Sumit shares tips for approaching this journey and explains the roadmap for testing organizations to transform themselves to lead the quality in DevOps.
The Fourth Constraint in Project Delivery—LeadershipTechWell
All too often, the triple constraints—time, cost, and quality—are bandied about as if they are the be-all, end-all. While they are important, leadership—the fourth and larger underpinning constraint—influences the first three. Statistics on project success and failure abound, and these measurements are usually taken against the triple constraints. According to the Project Management Institute, only 53 percent of projects are completed within budget, and only 49 percent are completed on time. If so many projects overrun budget and are late, we can’t really say, “Good, fast, or cheap—pick two.” Rob Burkett talks about leadership at every level of a team. He shares his insights and stories gleaned from his years of IT and project management experience. Rob speaks to some of the glaring difficulties in the workplace in general and some specifically related to IT delivery and project management. Leave with a clearer understanding of how to communicate with teams and team members, and gain a better understanding of how you can be a leader—up and down your organization.
Resolve the Contradiction of Specialists within Agile TeamsTechWell
As teams grow, organizations often draw a distinction between feature teams, which deliver the visible business value to the user, and component teams, which manage shared work. Steve Berczuk says that this distinction can help organizations be more productive and scale effectively, but he recognizes that not all shared work fits into this model. Some work is best handled by “specialists,” that is people with unique skills. Although teams composed entirely of T-shaped people is ideal, certain skills are hard to come by and are used irregularly across an organization. Since these specialists often need to work closely with teams, rather than working from their own backlog, they don’t fit into the component team model. The use of shared resources presents challenges to the agile planning model. Steve Berczuk shares how teams such as those providing infrastructure services and specialists can fit into a feature+component team model, and how variations such as embedding specialists in a scrum team can both present process challenges and add significant value to both the team and the larger organization.
Pin the Tail on the Metric: A Field-Tested Agile GameTechWell
Metrics don’t have to be a necessary evil. If done right, metrics can help guide us to make better forward-looking decisions, rather than being used for simply managing or monitoring. They can help us identify trade-offs between options for what to do next versus punitive or worse, purely managerial measures. Steve Martin won’t be giving the Top Ten List of field-tested metrics you should use. Instead, in this interactive mini-workshop, he leads you through the critical thinking necessary for you to determine what is right for you to measure. First, Steve explores why you want to measure something—whether it’s for a team, a portfolio, or even an agile transformation. Next, he provides multiple real-life metrics examples to help drive home concepts behind characteristics of good and bad metrics. Finally, Steve shows how to run his field-tested agile game—Pin the Tail on the Metric. Take back this activity to help you guide metrics conversations at your organization.
Agile Performance Holarchy (APH)—A Model for Scaling Agile TeamsTechWell
A hierarchy is an organizational network that has a top and a bottom, and where position is determined by rank, importance, and value. A holarchy is a network that has no top or bottom and where each person’s value derives from his ability, rather than position. As more companies seek the benefits of agile, leaders need to build and sustain delivery capability while scaling agile without introducing unnecessary process and overhead. The Agile Performance Holarchy (APH) is an empirical model for scaling and sustaining agility while continuing to deliver great products. Jeff Dalton designed the APH by drawing from lessons learned observing and assessing hundreds of agile companies and teams. The APH helps implement a holarchy—a system composed of interacting organizational units called holons—centered on a series of performance circles that embody the behaviors of high performing agile organizations. Jeff describes how APH provides guidelines in the areas of leadership, values, teaming, visioning, governing, building, supporting, and engaging within an all-agile organization. Join Jeff to see what the APH is all about and how you can use it in your team and organization.
A Business-First Approach to DevOps ImplementationTechWell
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Databases in a Continuous Integration/Delivery ProcessTechWell
DevOps is transforming software development with many organizations adopting lean development practices, implementing continuous integration (CI), and performing regular continuous deployment (CD) to their production environments. However, the database is largely ignored and often seen as a bottleneck in the DevOps process. Steve Jones discusses the challenges of database development and why many developers find the database to be an impediment to the CD process. Steve shares the techniques you can use to fit a database into the DevOps process. Learn how to store database code in a version control system, and the differences between that and application code. Steve demonstrates a CI process with SQL code and uses automated testing frameworks to check the code. Steve then shows how automated releases with manual gates can reduce the stress and risk of database deployments while ensuring consistent, reliable, repeatable releases to QA, UAT, and production.
Mobile Testing: What—and What Not—to AutomateTechWell
Organizations are moving rapidly into mobile technology, which has significantly increased the demand for testing of mobile applications. David Dangs says testers naturally are turning to automation to help ease the workload, increase potential test coverage, and improve testing efficiency. But should you try to automate all things mobile? Unfortunately, the answer is not always clear. Mobile has its own set of complications, compounded by a wide variety of devices and OS platforms. Join David to learn what mobile testing activities are ripe for automation—and those items best left to manual efforts. He describes the various considerations for automating each type of mobile application: mobile web, native app, and hybrid applications. David also covers device-level testing, types of testing, available automation tools, and recommendations for automation effectiveness. Finally, based on his years of mobile testing experience, David provides some tips and tricks to approach mobile automation. Leave with a clear plan for automating your mobile applications.
Cultural Intelligence: A Key Skill for SuccessTechWell
Diversity is becoming the norm in everyday life. However, introducing global delivery models without a proper understanding of intercultural differences can lead to difficulty, frustration, and reduced productivity. Priyanka Sharma and Thena Barry say that in our diverse world, we need teams with people who can cross these boundaries, communicate effectively, and build the diverse networks necessary to avoid problems. We need to learn about cultural intelligence (CI) and cultural quotient (CQ). CI is the ability to relate and work effectively across cultures. CQ is the cognitive, motivational, and behavioral capacity to understand and respond to beliefs, values, attitudes, and behaviors of individuals and groups. Together, CI and CQ can help us build behavioral capacities that aid motivation, behavior, and productivity in teams as well as individuals. Priyanka and Thena show how to build a more culturally intelligent place with tools and techniques from Leading with Cultural Intelligence, as well as content from the Hofstede cultural model. In addition, they illustrate the model with real-life experiences and demonstrate how they adapted in similar circumstances.
Turn the Lights On: A Power Utility Company's Agile TransformationTechWell
Why would a century-old utility with no direct competitors take on the challenge of transforming its entire IT application organization to an agile methodology? In an increasingly interconnected world, the expectations of customers continue to evolve. From smart meters to smart phones, IoT is creating a crisis point for industries not accustomed to rapid change. Glen Morris explains that pizzas can be tracked by the minute and packages at every stop, and customers now expect this same customer service model should exist for all industries—including power. Glen examines how to create momentum and transform non-IT-focused industries to an agile model. If you are struggling with gaining traction in your pursuit of agile within your business, Glen gives you concrete, practical experiences to leverage in your pursuit. Finally, he communicates how to gain buy-in from business partners who have no idea or concern about agile or its methodologies. If your business partners look at you with amusement when you mention the need for a dedicated Product Owner, join Glen as he walks you through the approaches to overcoming agile skepticism.
Into the Box Keynote Day 2: Unveiling amazing updates and announcements for modern CFML developers! Get ready for exciting releases and updates on Ortus tools and products. Stay tuned for cutting-edge innovations designed to boost your productivity.
A Comprehensive Look at Generative AI in Retail App Testing.pdfkalichargn70th171
Traditional software testing methods are being challenged in retail, where customer expectations and technological advancements continually shape the landscape. Enter generative AI—a transformative subset of artificial intelligence technologies poised to revolutionize software testing.
SOCRadar Research Team: Latest Activities of IntelBrokerSOCRadar
The European Union Agency for Law Enforcement Cooperation (Europol) has suffered an alleged data breach after a notorious threat actor claimed to have exfiltrated data from its systems. Infamous data leaker IntelBroker posted on the even more infamous BreachForums hacking forum, saying that Europol suffered a data breach this month.
The alleged breach affected Europol agencies CCSE, EC3, Europol Platform for Experts, Law Enforcement Forum, and SIRIUS. Infiltration of these entities can disrupt ongoing investigations and compromise sensitive intelligence shared among international law enforcement agencies.
However, this is neither the first nor the last activity of IntekBroker. We have compiled for you what happened in the last few days. To track such hacker activities on dark web sources like hacker forums, private Telegram channels, and other hidden platforms where cyber threats often originate, you can check SOCRadar’s Dark Web News.
Stay Informed on Threat Actors’ Activity on the Dark Web with SOCRadar!
Software Engineering, Software Consulting, Tech Lead.
Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Security,
Spring Transaction, Spring MVC,
Log4j, REST/SOAP WEB-SERVICES.
Accelerate Enterprise Software Engineering with PlatformlessWSO2
Key takeaways:
Challenges of building platforms and the benefits of platformless.
Key principles of platformless, including API-first, cloud-native middleware, platform engineering, and developer experience.
How Choreo enables the platformless experience.
How key concepts like application architecture, domain-driven design, zero trust, and cell-based architecture are inherently a part of Choreo.
Demo of an end-to-end app built and deployed on Choreo.
Quarkus Hidden and Forbidden ExtensionsMax Andersen
Quarkus has a vast extension ecosystem and is known for its subsonic and subatomic feature set. Some of these features are not as well known, and some extensions are less talked about, but that does not make them less interesting - quite the opposite.
Come join this talk to see some tips and tricks for using Quarkus and some of the lesser known features, extensions and development techniques.
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...Shahin Sheidaei
Games are powerful teaching tools, fostering hands-on engagement and fun. But they require careful consideration to succeed. Join me to explore factors in running and selecting games, ensuring they serve as effective teaching tools. Learn to maintain focus on learning objectives while playing, and how to measure the ROI of gaming in education. Discover strategies for pitching gaming to leadership. This session offers insights, tips, and examples for coaches, team leads, and enterprise leaders seeking to teach from simple to complex concepts.
Understanding Globus Data Transfers with NetSageGlobus
NetSage is an open privacy-aware network measurement, analysis, and visualization service designed to help end-users visualize and reason about large data transfers. NetSage traditionally has used a combination of passive measurements, including SNMP and flow data, as well as active measurements, mainly perfSONAR, to provide longitudinal network performance data visualization. It has been deployed by dozens of networks world wide, and is supported domestically by the Engagement and Performance Operations Center (EPOC), NSF #2328479. We have recently expanded the NetSage data sources to include logs for Globus data transfers, following the same privacy-preserving approach as for Flow data. Using the logs for the Texas Advanced Computing Center (TACC) as an example, this talk will walk through several different example use cases that NetSage can answer, including: Who is using Globus to share data with my institution, and what kind of performance are they able to achieve? How many transfers has Globus supported for us? Which sites are we sharing the most data with, and how is that changing over time? How is my site using Globus to move data internally, and what kind of performance do we see for those transfers? What percentage of data transfers at my institution used Globus, and how did the overall data transfer performance compare to the Globus users?
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoamtakuyayamamoto1800
In this slide, we show the simulation example and the way to compile this solver.
In this solver, the Helmholtz equation can be solved by helmholtzFoam. Also, the Helmholtz equation with uniformly dispersed bubbles can be simulated by helmholtzBubbleFoam.
How Recreation Management Software Can Streamline Your Operations.pptxwottaspaceseo
Recreation management software streamlines operations by automating key tasks such as scheduling, registration, and payment processing, reducing manual workload and errors. It provides centralized management of facilities, classes, and events, ensuring efficient resource allocation and facility usage. The software offers user-friendly online portals for easy access to bookings and program information, enhancing customer experience. Real-time reporting and data analytics deliver insights into attendance and preferences, aiding in strategic decision-making. Additionally, effective communication tools keep participants and staff informed with timely updates. Overall, recreation management software enhances efficiency, improves service delivery, and boosts customer satisfaction.
Experience our free, in-depth three-part Tendenci Platform Corporate Membership Management workshop series! In Session 1 on May 14th, 2024, we began with an Introduction and Setup, mastering the configuration of your Corporate Membership Module settings to establish membership types, applications, and more. Then, on May 16th, 2024, in Session 2, we focused on binding individual members to a Corporate Membership and Corporate Reps, teaching you how to add individual members and assign Corporate Representatives to manage dues, renewals, and associated members. Finally, on May 28th, 2024, in Session 3, we covered questions and concerns, addressing any queries or issues you may have.
For more Tendenci AMS events, check out www.tendenci.com/events
Developing Distributed High-performance Computing Capabilities of an Open Sci...Globus
COVID-19 had an unprecedented impact on scientific collaboration. The pandemic and its broad response from the scientific community has forged new relationships among public health practitioners, mathematical modelers, and scientific computing specialists, while revealing critical gaps in exploiting advanced computing systems to support urgent decision making. Informed by our team’s work in applying high-performance computing in support of public health decision makers during the COVID-19 pandemic, we present how Globus technologies are enabling the development of an open science platform for robust epidemic analysis, with the goal of collaborative, secure, distributed, on-demand, and fast time-to-solution analyses to support public health.
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
Enterprise Resource Planning System includes various modules that reduce any business's workload. Additionally, it organizes the workflows, which drives towards enhancing productivity. Here are a detailed explanation of the ERP modules. Going through the points will help you understand how the software is changing the work dynamics.
To know more details here: https://blogs.nyggs.com/nyggs/enterprise-resource-planning-erp-system-modules/
May Marketo Masterclass, London MUG May 22 2024.pdfAdele Miller
Can't make Adobe Summit in Vegas? No sweat because the EMEA Marketo Engage Champions are coming to London to share their Summit sessions, insights and more!
This is a MUG with a twist you don't want to miss.
Providing Globus Services to Users of JASMIN for Environmental Data AnalysisGlobus
JASMIN is the UK’s high-performance data analysis platform for environmental science, operated by STFC on behalf of the UK Natural Environment Research Council (NERC). In addition to its role in hosting the CEDA Archive (NERC’s long-term repository for climate, atmospheric science & Earth observation data in the UK), JASMIN provides a collaborative platform to a community of around 2,000 scientists in the UK and beyond, providing nearly 400 environmental science projects with working space, compute resources and tools to facilitate their work. High-performance data transfer into and out of JASMIN has always been a key feature, with many scientists bringing model outputs from supercomputers elsewhere in the UK, to analyse against observational or other model data in the CEDA Archive. A growing number of JASMIN users are now realising the benefits of using the Globus service to provide reliable and efficient data movement and other tasks in this and other contexts. Further use cases involve long-distance (intercontinental) transfers to and from JASMIN, and collecting results from a mobile atmospheric radar system, pushing data to JASMIN via a lightweight Globus deployment. We provide details of how Globus fits into our current infrastructure, our experience of the recent migration to GCSv5.4, and of our interest in developing use of the wider ecosystem of Globus services for the benefit of our user community.
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
In software engineering, the right architecture is essential for robust, scalable platforms. Wix has undergone a pivotal shift from event sourcing to a CRUD-based model for its microservices. This talk will chart the course of this pivotal journey.
Event sourcing, which records state changes as immutable events, provided robust auditing and "time travel" debugging for Wix Stores' microservices. Despite its benefits, the complexity it introduced in state management slowed development. Wix responded by adopting a simpler, unified CRUD model. This talk will explore the challenges of event sourcing and the advantages of Wix's new "CRUD on steroids" approach, which streamlines API integration and domain event management while preserving data integrity and system resilience.
Participants will gain valuable insights into Wix's strategies for ensuring atomicity in database updates and event production, as well as caching, materialization, and performance optimization techniques within a distributed system.
Join us to discover how Wix has mastered the art of balancing simplicity and extensibility, and learn how the re-adoption of the modest CRUD has turbocharged their development velocity, resilience, and scalability in a high-growth environment.
1.
W4
Agile
Testing
5/10/17
11:30
Pairing:
The
Secret
Sauce
of
Agile
Testing
Presented
by:
Jess
Lancaster
TechSmith
Brought
to
you
by:
350
Corporate
Way,
Suite
400,
Orange
Park,
FL
32073
888-‐-‐-‐268-‐-‐-‐8770
·∙·∙
904-‐-‐-‐278-‐-‐-‐0524
-‐
info@techwell.com
-‐
http://www.starwest.techwell.com/
2.
Jess
Lancaster
Jess
Lancaster
is
the
QA
practice
manager
at
TechSmith,
the
makers
of
Snagit,
Camtasia,
and
other
visual
communication
software
applications.
He
coaches
and
equips
testers
with
the
skills
to
be
quality
champions
on
agile
teams.
With
more
than
twenty
years
of
information
systems
and
software
development
experience,
Jess
has
been
a
consultant,
test
lead,
and
test
manager
with
government,
financial,
insurance,
and
commercial
software
organizations.
Jess
is
passionate
about
getting
into
the
trenches
with
other
testers,
exploring
software,
and
trying
new
testing
techniques.
Cofounder
of
the
Lansing
Area
Software
Testers
meetup,
he
also
helps
grow
the
next
generation
of
software
testers
by
teaching
software
testing
courses
at
Lansing
Community
College.
4. 5/1/2017
2
About Jess
In this session you will learn:
Why pairing works, and reasons why you as a
tester or agile team member need to be
pairing
How to get started
My team’s pair testing mistakes and what
worked well
The recipe for making this secret sauce back
at work
5. 5/1/2017
3
What is Pair Testing?
Pair Testing is testing of software by two team members sitting
behind one machine
One team member is the Driver, in control of the mouse and
keyboard, the other one is the Notetaker, making notes, discussing
the test ideas and asking questions, and making observations
6. 5/1/2017
4
Primary styles of pairing
Tester/Tester with Driver/Notetaker
Tester/Other Team Member with
Driver/Notetaker
Tester/Developer
Why you need to be pairing
Mentoring
Collaborative learning sessions
Knowledge sharing – Testing or otherwise
Gave birth to Co-Testing: Testing together
with more than one machine
Builds team relationships
7. 5/1/2017
5
Why you need to be pairing
Gives a product team-based tester added
perspective
Productivity
Provides focus and direction in testing
New feature bug harvesting
The software benefits from perspectives
colliding
Experience report: How we
cooked up pair testing
@TechSmith
Our testers work a matrixed structure, embedded in
agile teams reporting to a Practice Manager
Wanted to get our testers sharing testing
knowledge and product knowledge
Started with other collaboration exercises, but that
wasn’t directly tied to daily work that needed to get
done and fell off
8. 5/1/2017
6
Where we started with
pairing
We experimented with pair testing:
Researched it
Created a one page job aid, I termed the
Pair Testing Cheat Sheet
Trained it
Tried it
Reported on it
Improved it
Kept doing it
What Pairing
looks like
@TechSmith
9. 5/1/2017
7
That’s all great, but how
do I make the sauce!?!
Steps to Making Awesome
Sauce
Think of P.A.I.R. as a Four Step mnemonic
Partner
Arrangements
Investigation
Retrospective
10. 5/1/2017
8
Step 1 – Choose a Partner
Choose a tester, developer, or other team member
you want to partner with in a pair testing session
Step 2 – Arrangements -
Quick Planning
Plan your pairing session. Determine the following:
Schedule a time to test and the length of the
session
Define the testing focus. Clarify the goals and what
you expect for outputs of your pairing session
Determine at what point you want to switch who’s
in the driver’s seat.
Choose an environment that is suitable for two
people to test together at one machine. Be sure you
can work without interruptions and are free to talk
to each other.
11. 5/1/2017
9
Pick a suitable feature or
small set of features to test
Define an exploratory test charter.
One way of expressing charters is with
the simple template:
Explore area with resources,
constraints, tools, etc. to discover
information.
Pair testing works great when testing
new features or functionality.
Check out Exploratory Testing on
Agile Teams and charters in this book
Test Charter
Two Named Individuals Testing
Pair Testing
Session Inputs
What Hardware
do I need?
Access set up?
Application
install?
Configuration?
Clarify your focus - Based on your
charter generate ideas of things to
test
What’s in scope, out of scope?
How long is your pairing session?
12. 5/1/2017
10
What did you discover through the course of testing? These
are the session notes of your Pair Testing effort. The things
you tested, bugs discovered, what didn’t you get to, and list
of any follow up items – questions, tasks, etc.
Explore Image Advanced Capture options of Snagit with effects/sharing options to
determine if any new bugs were introduced when Advanced Capture code was refactored.
Jess Lancaster and Emeril Lagasse
• A Windows 10 laptop
• Current Snagit
development build
installed
• Multiple monitors
• Network access for
sharing options
• In Scope
• All Advanced capture options
• Start with ensuring all option perform as expected before
going to capture permutations
• Use Effects
• Sharing options: TechSmith products
• Modify Capture defaults Preview, Copy, Cursor, Time Delay
• Out of Scope
• Sharing options outside of those listed above
• Downloadable sharing options
• Video capture
90 min.
13. 5/1/2017
11
Exercise: Using your Recipe Card
Create your own Pairing Recipe for
a Session
Charter: Explore area with resources,
constraints, tools, etc. to discover information.
Example:
Explore the printing options of Snagit without modifying
printer properties to determine if any new bugs were
introduced the page setup options were refactored.
Explore area with resources, constraints, tools, etc. to
discover information.
Two Named Individuals Testing
Pair Testing
Session Inputs
What Hardware
do I need?
Access set up?
Application
install?
Configuration?
Clarify your focus - Based on your
charter generate ideas of things to
test
What’s in scope, out of scope?
How long is your pairing session?
14. 5/1/2017
12
Step 3 – Investigation -
(TEST)
Run the pair testing session
One team member (the Driver) is in control of the
keyboard and mouse. The second team member
thinks out-loud, asks questions, and makes session
notes. Driver starts by driving the testing session.
Tip: Don’t forget to take a break for longer pairing
sessions!
Switch roles at the defined interval.
Tip: Your mileage may vary on switching in short
pairing sessions.
Step 4 – Retrospective -
Report and Evaluate
15. 5/1/2017
13
Session Reporting
Summary of what you tested
Test Notes
Bugs
Issues – things you are unsure of, follow up
items, such as questions
Risks identified
Example Session Report
16. 5/1/2017
14
Evaluate
Complete a quick retrospective on the
session:
What worked well?
What would you improve based on the
session?
Mistakes I’ve made…
Setting team pairing goals, then backing off too
much
Hiding the pairing data from the team
Being too restrictive
17. 5/1/2017
15
Team Member Mistakes
Some didn’t do testing, but collaborated on ideas,
techniques for testing
Going over time limit…like way over…
Not having a more focused goal in what we want to
test: assumptions and scope
Setup: Plan for more time for getting things set up,
otherwise it eats into your testing time
Awesome Sauce…
People reached out to each other!
Learned from our mistakes and those of others due to team
shareouts
Tester/Dev pairing, Tester/Designer pairing, Tester/Support Rep
pairing, Test Manager/Program Manager pairing…
Testers discovered some new methods and tools that worked for
them: Co-Testing
Testers had a lot of good feedback for the initial user experience
Found plenty of bugs
Testing in front of the developers which helped to spur
conversations around the product and raise pairing awareness
Get to see partner’s approach to testing
18. 5/1/2017
16
Getting Started Tips
Review and follow the 5 steps
Find a pairing partner and try a session for 60
minutes, then do a quick evaluation
Try it again
Share it out: Expose others to the benefits!
Thank You!!!
Slides - http://bit.ly/pairtestingstareast
Jess Lancaster
Twitter: @jessclancaster
LinkedIn: JessLancaster
19. 5/1/2017
17
Resources
Sources for pairing information
http://www.kohl.ca/articles/pairtesting.pdf
http://katrinatester.blogspot.com/2015/05/pair-testing.html
Session-Based Test Management
http://www.satisfice.com/articles/sbtm.pdf
For more information on Exploratory Testing on Agile Teams and
charters: http://testobsessed.com/wp-
content/uploads/2011/08/ETinAgile-agile2011-final.pdf
Maaret Pyhäjärvi – Two Styles of Pairing
https://www.youtube.com/watch?v=ctRD2KBUYSI