Agile Testing in the Enterprise 2016
•
1 like•337 views
The document discusses challenges with agile testing in large enterprises and across distributed teams. It outlines some of the common challenges such as bureaucracy, multiple concurrent projects, and dependencies between teams. The document then provides several key testing practices that can work across teams, such as coordinating test planning, creating a shared test matrix, and using examples and tests to develop a common language. It emphasizes the importance of transparency between teams by sharing information and dependencies to reduce blame and ensure everyone understands the shared goals.
Report
Share
Report
Share
Download to read offline
Recommended
Creating Agile Test Strategies for Larger Enterprises
Having difficulty creating an agile test strategy for your company? Let Testing Excellence Award winner, Derk-Jan de Grood, show you how it’s done
View webinar recording here - http://huddle.eurostarsoftwaretesting.com/resource/agile-testing/creating-agile-test-strategies-larger-enterprises/
Change the conversation keynote StarWest 2015
Change the conversation about testing and quality―from bugs and poor requirements to products and solutions.
Key Success Factors for Agile Testing 2016
Success factors and practices from the books "Agile Testing" and "More Agile Testing" by Janet Gregory and Lisa Crispin
Agile testing for distributed teams and large orgs
Some of the challenges and ideas for improving communication, testing practices that can help, and suggestions for adapting to the changes necessary to be successful in an agile world.
EuroSTAR webinar: creating Agile Test Strategies for larger Enterprises
Many organisations are reducing their test managers and Test Competence Centres. Quality is embedded in development. Testing is responsibility of the team. Still testing is on the rebound. In bigger projects and in enterprises an effective test strategy is vital to ensure that the team does the right testing, we focus on integration and we have insight in inter- team dependencies. In this webinar, Derk-Jan will share his experiences as an overall test manager in various projects and define some key ingredients of an Agile Test Strategy.
Testing is a team problem
This document summarizes Janet Gregory's work promoting agile testing practices. It notes that she has been involved with agile teams since 2000 and has authored books and online courses on agile testing. The document discusses how testing should be a shared responsibility of the whole team. It emphasizes that testing provides feedback to improve quality, not just find bugs, and explains practices like examples, acceptance test-driven development, and exploratory testing that involve the whole team in testing activities.
Holistic testing in DevOps
The document discusses holistic testing in DevOps. It emphasizes testing early in collaboration with customers to help prevent defects. It also discusses testing throughout the deployment pipeline from development to production, including testing releases and using monitoring to observe and learn. The goal is to optimize the entire process from concept to delivering value to customers through continuous testing, delivery, learning and improvement.
Using your testing mindset to explore requirements
Workshop from Agile Testing Days USA, Boston 2018 Janet Gregory and Ardita Karaj. Using different ideas to create your product backlog - understanding your ecosystem and using exploratory test charters to drive experimentation to your get to your learning releases.
Recommended
Creating Agile Test Strategies for Larger Enterprises
Having difficulty creating an agile test strategy for your company? Let Testing Excellence Award winner, Derk-Jan de Grood, show you how it’s done
View webinar recording here - http://huddle.eurostarsoftwaretesting.com/resource/agile-testing/creating-agile-test-strategies-larger-enterprises/
Change the conversation keynote StarWest 2015
Change the conversation about testing and quality―from bugs and poor requirements to products and solutions.
Key Success Factors for Agile Testing 2016
Success factors and practices from the books "Agile Testing" and "More Agile Testing" by Janet Gregory and Lisa Crispin
Agile testing for distributed teams and large orgs
Some of the challenges and ideas for improving communication, testing practices that can help, and suggestions for adapting to the changes necessary to be successful in an agile world.
EuroSTAR webinar: creating Agile Test Strategies for larger Enterprises
Many organisations are reducing their test managers and Test Competence Centres. Quality is embedded in development. Testing is responsibility of the team. Still testing is on the rebound. In bigger projects and in enterprises an effective test strategy is vital to ensure that the team does the right testing, we focus on integration and we have insight in inter- team dependencies. In this webinar, Derk-Jan will share his experiences as an overall test manager in various projects and define some key ingredients of an Agile Test Strategy.
Testing is a team problem
This document summarizes Janet Gregory's work promoting agile testing practices. It notes that she has been involved with agile teams since 2000 and has authored books and online courses on agile testing. The document discusses how testing should be a shared responsibility of the whole team. It emphasizes that testing provides feedback to improve quality, not just find bugs, and explains practices like examples, acceptance test-driven development, and exploratory testing that involve the whole team in testing activities.
Holistic testing in DevOps
The document discusses holistic testing in DevOps. It emphasizes testing early in collaboration with customers to help prevent defects. It also discusses testing throughout the deployment pipeline from development to production, including testing releases and using monitoring to observe and learn. The goal is to optimize the entire process from concept to delivering value to customers through continuous testing, delivery, learning and improvement.
Using your testing mindset to explore requirements
Workshop from Agile Testing Days USA, Boston 2018 Janet Gregory and Ardita Karaj. Using different ideas to create your product backlog - understanding your ecosystem and using exploratory test charters to drive experimentation to your get to your learning releases.
Agile Testing in the Enterprise
Introduction into testing in large and distributed organizations that are practicing agile methods. Ideas, practices and tools to help develop open communication, deal with cultural differences both within an organization and across continents specifically related to testing activities.
Test process improvement – how hard can it be?
This presentation looks at how to make any improvement project a success, and it does this by using some fun case study examples looking at how Geoff has seen things go wrong, and from the depth of despair we will look at how things can be made to be successful.
View webinar recording - https://testhuddle.com/resource/test-process-improvement-hard-can/
Will Robots Replace Testers?
This talk suggests how we might make sense of the tools landscape of the near future, where the pressure to modernise processes and automate is greatest, and what a new test process supported by tools might look like.
Takeaways:
- We need to take machine learning in testing seriously, but it won’t be taking our jobs just yet
- We don’t need more test automation tools; today we need tools that capture tester knowledge
- Tools that that learn and think can’t work for testers until we solve the knowledge capture challenge.
View On-Demand Webinar: https://youtu.be/EzyUdJFuzlE
Why agile testing isn't working
The document discusses challenges with the traditional waterfall process and separating testing from development in Agile. It advocates for a whole team approach where testers and developers collaborate throughout the sprint. Specification workshops are recommended to develop shared understanding. Automation and living documentation are presented as ways to prevent bugs. Quality is defined by how the software performs for users rather than bug counts. Measuring what matters to the business, rather than low level risks, is advised.
Testing is Not a 9 to 5 Job - talk by industry executive Mike Lyles
** FULL WEBINAR RECORDING: https://youtu.be/IC6ul_-PLj8 **
Find your hire power: Learn what managers look for when hiring (and firing...) testers.
Being an expert tester is no different. While the art and craft of testing and being a thinking tester is something that is built within you, simply going to work every day and being a tester is not always enough.
Each of us can become “gold medal testers” by practicing, studying, refining our skills, and building our craft.
In this webinar, we will evaluate extracurricular activities and practices that will enable you to grow from a good tester to a great tester.
Listen to this webinar, and enjoy these key takeaways:
** Inputs from testing experts on how they improve their skills
** Suggestions for online training and materials, which should be studied
** How to leverage social media to interact with the testing community
** Contributions you can make to the testing community to build your name as a leading test engineer
A Rapid Introduction to Rapid Software Testing
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.
The Whole Team Approach to Quality in Continuous Delivery
Lisa shares her teams' experiences with making a team commitment to quality and learning ways to build it in and fit all testing activities into continuous delivery.
Get testing bottlenecks out of your pipelines
When teams move towards continuous delivery and deployment, how do they manage the manual stages in their deployment pipeline? This talk gives some techniques to visualize pipelines, identify bottlenecks, find ways to remove them.
Test Strategy-The real silver bullet in testing by Matthew Eakin
This document provides an overview of creating a testing strategy. It begins with explaining why a testing strategy is important, as testing accounts for a large portion of IT budgets. It then discusses the key questions a testing strategy should answer: what to test, where to test, when to test, how to test, and who will test.
The document outlines a process for creating a testing strategy, including assessing the current state, defining a future vision, and creating a roadmap to get from the current to future state. It provides examples of what to include under each section of the strategy, such as system architecture under "what to test" and test environments under "where to test". Overall, the document provides guidance on developing a
'The Real Agile Testing Quadrants' with Michael Bolton
EuroSTAR Conferences, with the support of ISA Software Skillnet, Irish Software Innovation Network and SoftTest, were delighted to bring you a half-day software testing masterclass with Michael Bolton
In this session, Michael Bolton (who has extensive experience as a tester, as a programmer, and as a project manager) explained the role of skilled software testers, and why you might not want to think of testing as "quality assurance".
He present ideas about the relationship between management and testers, and about the service that testers really provide: making quality assurance possible by lighting the way of the project. For those of you who who attended this event, we really hope it was of use to you in your testing careers.
www.eurostarconferences.com
A Rapid Introduction to Rapid Software Testing
This document provides a summary of a presentation on Rapid Software Testing. The presentation was given by Michael Bolton of DevelopSense and covered the methodology and mindset of rapid software testing. It emphasizes testing software expertly under uncertainty and time pressure. The presentation defines rapid testing as testing more quickly and less expensively while still achieving excellent results. It compares rapid testing to other approaches like exhaustive, ponderous, and slapdash testing. The presentation also discusses principles of rapid testing, how to recognize problems quickly using heuristics, and testing rapidly to fulfill the mission of testing.
Testing in a Continuous World
Workshop given at Agile Testing Days 2017 together with Lisa Crispin: "Testing in a Continuous World - How to Continuously Learn for Successful Continuous Delivery"
Abstract:
Nowadays users are quite used to getting product updates every other day. Many teams want to release updates to production more frequently, but they’re struggling to complete testing activities and fear that they might deliver big bugs instead of valuable features. Continuous delivery of reliable software is a huge challenge.
Many teams already develop their products in small chunks, but how does testing and quality fit into this fast-paced scenario? How can we not only continuously deliver, but continuously provide value to our users?
Elisabeth and Lisa have worked in teams who struggled to have testing fully integrated, being able to only release once every few weeks. They’ve also experienced highly collaborative teams who could easily deliver multiple times a day to quickly validate if they added value. What's your situation, can you keep up with testing and release frequently?
In this hands-on workshop, participants will have a chance to practice techniques that can help teams feel confident releasing more frequently. We will facilitate activities in which participants will come up with new experiments to help shorten feedback cycles, make sure all essential types of testing are done continually, and fit testing into the continuous world. Let's share experiences and develop custom solutions for your specific scenarios together!
Rapid Software Testing: Strategy
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.
Are You Building the Right Thing? - Janet G @ CMBAgileConf 2016
In Agile Development, we focus on building in quality and preventing defects, rather than finding defects at the tail-end of a development cycle. Focusing our testing efforts on the things customers care about most is key. In this presentation, Janet explains how Testers and Agile teams can ensure they are building the right thing.
Accelerating Product Delivery with Design Sprints
The document discusses design sprints, which are a 5-day process to go from an idea to a tested prototype. It involves stages of understanding the problem, diverging on ideas, converging on a solution, prototyping, and user testing. The author discusses having conducted several successful design sprints across web and mobile products that significantly improved metrics like conversions, engagement, and growth. Key lessons are to properly prepare with data, stakeholders, and tools and to fully involve different teams to iterate quickly based on learnings.
Help Me, I got a team of junior testers!
The document provides guidance for managing a team of junior testers. It discusses challenges such as lack of skills and experience in junior testers. It recommends setting clear expectations, providing frequent communication and feedback, ensuring knowledge sharing, and protecting the team to help them succeed. Patience and structure are important, as is repeating key messages, to help junior testers learn and improve. The goal is for the team to work cooperatively toward a common objective.
Test Cases are dead, long live Checklists!
This document discusses why checklists are better than test cases for documentation in quality assurance. It argues that test cases become overcrowded and focus too much on documentation rather than core functions. Checklists are more time-saving and easy to update. An example compares a test case to a checklist for login/registration flows. The author's company Hipo uses a test pad and robot framework integrated with checklists to share with clients and team members.
Product Agility: 3 fundamentals from the trenches
There is no silver bullet for Product and Business Agility.
On this talk you will know which are the fundamentals and some of the initiatives in place in the OutSystems Engineering Journey to better responding rapidly and flexibly to ours customers demands.
QI, not QA
The document argues that the term "quality assurance" (QA) no longer accurately describes the role of testers in an Agile development process. QA implies monitoring and assuring quality from the outside, whereas testers are part of the development team. "Quality assistance" is also problematic as it implies assisting others rather than creating value. The document proposes using "quality intelligence" instead, which better captures how testers acquire and transform product data into useful information for stakeholders. Adopting this new term would help testing roles fully transition to an Agile paradigm.
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In Agile
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In AgileHo Chi Minh City Software Testing Club
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Nhat Do, Vu Duong
Context-Driven Testing (CDT) rejects the notion of generalized “best practices” that apply to all projects, and instead accepts that different practices work best under different circumstances. The third principle of the seven defined in CDT states that people are the most important part of any project’s context. Less of a focus on processes and tools, with more emphasis on people and their collaboration empowers testers with the freedom to make choices about how best to do their job without following a restrictive plan.
In joining the game of workshop and some theory sharing in slides, you will a better understanding of Context-Driven Testing practices, principles and its benefits as well as know how is a nice Marriage of Agile and Context-Driven Testing.Charla TestingUy 2019 - Agile testing in context
Expositor: Janet Gregory
Resumen: When agile development first gained popularity, agile meant collocated teams, including testers, programmers, analysts, and customers who were expected to perform many functions. As agile methods have spread and expanded, it becomes apparent that one size does not fit all.
For example, large organizations and those with globally-distributed teams are facing challenges with their agile deployment. Having worked with many teams, Janet Gregory has observed ways that testing in any agile teams can still help deliver a high-quality product. Whether your agile team is part of an enterprise solution, or part of a distributed team is scattered across time zones with individuals working remotely from home, or is part of an offshore outsourced project, you’ll take away techniques and tools to help develop open communication, deal with cultural differences both within an organization and across continents specifically related to testing activities.
Agile Testing: Learning Journeys for the Whole Team - Janet G @ CMBAgileConf ...
Agile Testing: Learning Journeys for the Whole Team - Janet G @ CMBAgileConf ...ColomboCampsCommunity
When Agile Development first gained popularity, Agile meant collocated teams, including testers, programmers, analysts, and customers who were expected to perform many functions. As Agile methods have spread and expanded, many organizations with globally-distributed teams are facing challenges with their Agile deployment.
Janet shares her experiences and lessons learned that show how testing activities can help develop open communication, and share data and information within a team or across continents. These ideas can help create the common understanding for what the team is building so the team can work together – with fun.
More Related Content
What's hot
Agile Testing in the Enterprise
Introduction into testing in large and distributed organizations that are practicing agile methods. Ideas, practices and tools to help develop open communication, deal with cultural differences both within an organization and across continents specifically related to testing activities.
Test process improvement – how hard can it be?
This presentation looks at how to make any improvement project a success, and it does this by using some fun case study examples looking at how Geoff has seen things go wrong, and from the depth of despair we will look at how things can be made to be successful.
View webinar recording - https://testhuddle.com/resource/test-process-improvement-hard-can/
Will Robots Replace Testers?
This talk suggests how we might make sense of the tools landscape of the near future, where the pressure to modernise processes and automate is greatest, and what a new test process supported by tools might look like.
Takeaways:
- We need to take machine learning in testing seriously, but it won’t be taking our jobs just yet
- We don’t need more test automation tools; today we need tools that capture tester knowledge
- Tools that that learn and think can’t work for testers until we solve the knowledge capture challenge.
View On-Demand Webinar: https://youtu.be/EzyUdJFuzlE
Why agile testing isn't working
The document discusses challenges with the traditional waterfall process and separating testing from development in Agile. It advocates for a whole team approach where testers and developers collaborate throughout the sprint. Specification workshops are recommended to develop shared understanding. Automation and living documentation are presented as ways to prevent bugs. Quality is defined by how the software performs for users rather than bug counts. Measuring what matters to the business, rather than low level risks, is advised.
Testing is Not a 9 to 5 Job - talk by industry executive Mike Lyles
** FULL WEBINAR RECORDING: https://youtu.be/IC6ul_-PLj8 **
Find your hire power: Learn what managers look for when hiring (and firing...) testers.
Being an expert tester is no different. While the art and craft of testing and being a thinking tester is something that is built within you, simply going to work every day and being a tester is not always enough.
Each of us can become “gold medal testers” by practicing, studying, refining our skills, and building our craft.
In this webinar, we will evaluate extracurricular activities and practices that will enable you to grow from a good tester to a great tester.
Listen to this webinar, and enjoy these key takeaways:
** Inputs from testing experts on how they improve their skills
** Suggestions for online training and materials, which should be studied
** How to leverage social media to interact with the testing community
** Contributions you can make to the testing community to build your name as a leading test engineer
A Rapid Introduction to Rapid Software Testing
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.
The Whole Team Approach to Quality in Continuous Delivery
Lisa shares her teams' experiences with making a team commitment to quality and learning ways to build it in and fit all testing activities into continuous delivery.
Get testing bottlenecks out of your pipelines
When teams move towards continuous delivery and deployment, how do they manage the manual stages in their deployment pipeline? This talk gives some techniques to visualize pipelines, identify bottlenecks, find ways to remove them.
Test Strategy-The real silver bullet in testing by Matthew Eakin
This document provides an overview of creating a testing strategy. It begins with explaining why a testing strategy is important, as testing accounts for a large portion of IT budgets. It then discusses the key questions a testing strategy should answer: what to test, where to test, when to test, how to test, and who will test.
The document outlines a process for creating a testing strategy, including assessing the current state, defining a future vision, and creating a roadmap to get from the current to future state. It provides examples of what to include under each section of the strategy, such as system architecture under "what to test" and test environments under "where to test". Overall, the document provides guidance on developing a
'The Real Agile Testing Quadrants' with Michael Bolton
EuroSTAR Conferences, with the support of ISA Software Skillnet, Irish Software Innovation Network and SoftTest, were delighted to bring you a half-day software testing masterclass with Michael Bolton
In this session, Michael Bolton (who has extensive experience as a tester, as a programmer, and as a project manager) explained the role of skilled software testers, and why you might not want to think of testing as "quality assurance".
He present ideas about the relationship between management and testers, and about the service that testers really provide: making quality assurance possible by lighting the way of the project. For those of you who who attended this event, we really hope it was of use to you in your testing careers.
www.eurostarconferences.com
A Rapid Introduction to Rapid Software Testing
This document provides a summary of a presentation on Rapid Software Testing. The presentation was given by Michael Bolton of DevelopSense and covered the methodology and mindset of rapid software testing. It emphasizes testing software expertly under uncertainty and time pressure. The presentation defines rapid testing as testing more quickly and less expensively while still achieving excellent results. It compares rapid testing to other approaches like exhaustive, ponderous, and slapdash testing. The presentation also discusses principles of rapid testing, how to recognize problems quickly using heuristics, and testing rapidly to fulfill the mission of testing.
Testing in a Continuous World
Workshop given at Agile Testing Days 2017 together with Lisa Crispin: "Testing in a Continuous World - How to Continuously Learn for Successful Continuous Delivery"
Abstract:
Nowadays users are quite used to getting product updates every other day. Many teams want to release updates to production more frequently, but they’re struggling to complete testing activities and fear that they might deliver big bugs instead of valuable features. Continuous delivery of reliable software is a huge challenge.
Many teams already develop their products in small chunks, but how does testing and quality fit into this fast-paced scenario? How can we not only continuously deliver, but continuously provide value to our users?
Elisabeth and Lisa have worked in teams who struggled to have testing fully integrated, being able to only release once every few weeks. They’ve also experienced highly collaborative teams who could easily deliver multiple times a day to quickly validate if they added value. What's your situation, can you keep up with testing and release frequently?
In this hands-on workshop, participants will have a chance to practice techniques that can help teams feel confident releasing more frequently. We will facilitate activities in which participants will come up with new experiments to help shorten feedback cycles, make sure all essential types of testing are done continually, and fit testing into the continuous world. Let's share experiences and develop custom solutions for your specific scenarios together!
Rapid Software Testing: Strategy
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.
Are You Building the Right Thing? - Janet G @ CMBAgileConf 2016
In Agile Development, we focus on building in quality and preventing defects, rather than finding defects at the tail-end of a development cycle. Focusing our testing efforts on the things customers care about most is key. In this presentation, Janet explains how Testers and Agile teams can ensure they are building the right thing.
Accelerating Product Delivery with Design Sprints
The document discusses design sprints, which are a 5-day process to go from an idea to a tested prototype. It involves stages of understanding the problem, diverging on ideas, converging on a solution, prototyping, and user testing. The author discusses having conducted several successful design sprints across web and mobile products that significantly improved metrics like conversions, engagement, and growth. Key lessons are to properly prepare with data, stakeholders, and tools and to fully involve different teams to iterate quickly based on learnings.
Help Me, I got a team of junior testers!
The document provides guidance for managing a team of junior testers. It discusses challenges such as lack of skills and experience in junior testers. It recommends setting clear expectations, providing frequent communication and feedback, ensuring knowledge sharing, and protecting the team to help them succeed. Patience and structure are important, as is repeating key messages, to help junior testers learn and improve. The goal is for the team to work cooperatively toward a common objective.
Test Cases are dead, long live Checklists!
This document discusses why checklists are better than test cases for documentation in quality assurance. It argues that test cases become overcrowded and focus too much on documentation rather than core functions. Checklists are more time-saving and easy to update. An example compares a test case to a checklist for login/registration flows. The author's company Hipo uses a test pad and robot framework integrated with checklists to share with clients and team members.
Product Agility: 3 fundamentals from the trenches
There is no silver bullet for Product and Business Agility.
On this talk you will know which are the fundamentals and some of the initiatives in place in the OutSystems Engineering Journey to better responding rapidly and flexibly to ours customers demands.
QI, not QA
The document argues that the term "quality assurance" (QA) no longer accurately describes the role of testers in an Agile development process. QA implies monitoring and assuring quality from the outside, whereas testers are part of the development team. "Quality assistance" is also problematic as it implies assisting others rather than creating value. The document proposes using "quality intelligence" instead, which better captures how testers acquire and transform product data into useful information for stakeholders. Adopting this new term would help testing roles fully transition to an Agile paradigm.
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In Agile
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In AgileHo Chi Minh City Software Testing Club
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Nhat Do, Vu Duong
Context-Driven Testing (CDT) rejects the notion of generalized “best practices” that apply to all projects, and instead accepts that different practices work best under different circumstances. The third principle of the seven defined in CDT states that people are the most important part of any project’s context. Less of a focus on processes and tools, with more emphasis on people and their collaboration empowers testers with the freedom to make choices about how best to do their job without following a restrictive plan.
In joining the game of workshop and some theory sharing in slides, you will a better understanding of Context-Driven Testing practices, principles and its benefits as well as know how is a nice Marriage of Agile and Context-Driven Testing.What's hot (20)
Testing is Not a 9 to 5 Job - talk by industry executive Mike Lyles
Testing is Not a 9 to 5 Job - talk by industry executive Mike Lyles
The Whole Team Approach to Quality in Continuous Delivery
The Whole Team Approach to Quality in Continuous Delivery
Test Strategy-The real silver bullet in testing by Matthew Eakin
Test Strategy-The real silver bullet in testing by Matthew Eakin
'The Real Agile Testing Quadrants' with Michael Bolton
'The Real Agile Testing Quadrants' with Michael Bolton
Are You Building the Right Thing? - Janet G @ CMBAgileConf 2016
Are You Building the Right Thing? - Janet G @ CMBAgileConf 2016
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In Agile
[HCMC STC Jan 2015] Workshop Of Context-Driven Testing In Agile
Similar to Agile Testing in the Enterprise 2016
Charla TestingUy 2019 - Agile testing in context
Expositor: Janet Gregory
Resumen: When agile development first gained popularity, agile meant collocated teams, including testers, programmers, analysts, and customers who were expected to perform many functions. As agile methods have spread and expanded, it becomes apparent that one size does not fit all.
For example, large organizations and those with globally-distributed teams are facing challenges with their agile deployment. Having worked with many teams, Janet Gregory has observed ways that testing in any agile teams can still help deliver a high-quality product. Whether your agile team is part of an enterprise solution, or part of a distributed team is scattered across time zones with individuals working remotely from home, or is part of an offshore outsourced project, you’ll take away techniques and tools to help develop open communication, deal with cultural differences both within an organization and across continents specifically related to testing activities.
Agile Testing: Learning Journeys for the Whole Team - Janet G @ CMBAgileConf ...
Agile Testing: Learning Journeys for the Whole Team - Janet G @ CMBAgileConf ...ColomboCampsCommunity
When Agile Development first gained popularity, Agile meant collocated teams, including testers, programmers, analysts, and customers who were expected to perform many functions. As Agile methods have spread and expanded, many organizations with globally-distributed teams are facing challenges with their Agile deployment.
Janet shares her experiences and lessons learned that show how testing activities can help develop open communication, and share data and information within a team or across continents. These ideas can help create the common understanding for what the team is building so the team can work together – with fun.
Exploring Features and Stories for shared understanding workshop
90 minute workshop to explore tools like the 7 Product Dimensions to help build shared understanding of a feature or story. Given at European Testing Conference 2020
STARCANADA 2013 Keynote: Lightning Strikes the Keynotes
Throughout the years, Lightning Talks have been a popular part of the STAR conferences. If you’re not familiar with the concept, Lightning Talks consists of a series of five-minute talks by different speakers within one presentation period. Lightning Talks are the opportunity for speakers to deliver their single biggest bang-for-the-buck idea in a rapid-fire presentation. And now, lightning has struck the STAR keynotes. Some of the best-known experts in testing—Jon Bach, Michael Bolton, Fiona Charles, Janet Gregory, Paul Holland, Griffin Jones, Keith Klain, Gerard Meszaros, and Nate Oster—will step up to the podium and give you their best shot of lightning. Get ten keynote presentations for the price of one—and have some fun at the same time.
Framing Patterns
This document provides an overview of framing in decision making. It discusses how a frame acts as a limited description that filters what is relevant to a problem. Inappropriate frames can lead to poor decisions. The document then discusses different patterns and tools that can be used to properly frame a decision problem, such as establishing what is at stake, selecting the right size process, communicating the strategy arc, using issue raising as an icebreaker, employing the whine bottle technique, identifying hidden assumptions, and using a decision hierarchy. The overall intent is to provide a catalog of patterns and tools to help structure the framing phase of a decision process.
New model
I believe that our existing models of testing are not fit for purpose – they are inconsistent, controversial, partial, proprietary and stuck in the past. They are not going to support us in the rapidly emerging technologies and approaches. The certification schemes that should represent the interests and integrity of our profession don’t, and we are left with schemes that are popular, but have low value, lower esteem and attract harsh criticism. My goal in proposing the New Model is to stimulate new thinking in this area.
eurostarconferences.com
testhuddle.com
A New Model For Testing
I believe that our existing models of testing are not fit for purpose – they are inconsistent, controversial, partial, proprietary and stuck in the past. They are not going to support us in the rapidly emerging technologies and approaches. The certification schemes that should represent the interests and integrity of our profession don’t, and we are left with schemes that are popular, but have low value, lower esteem and attract harsh criticism. My goal in proposing the New Model is to stimulate new thinking in this area.
eurostarconferences.com
testhuddle.com
QPAM ATD 2022.pdf
This document presents the Quality Practices Assessment Model (QPAM), which was developed by Janet Gregory and Selena Delesie to help teams assess and improve the quality of their processes. The model evaluates teams across 10 quality aspects, including feedback loops, culture, testing practices, and code quality. It also categorizes teams into four dimensions based on their practices: Beginning, Unifying, Practicing, and Innovating. The document provides examples of questions that could be asked to facilitate a QPAM assessment and discusses visualizing the results using a radar chart. The goal of QPAM is to serve as a starting point for teams to identify areas for improvement in a method-agnostic way.
Atd advanced topicsworkshop
The document summarizes an advanced agile testing workshop hosted by Lisa Crispin. The workshop aims to be collaborative and help attendees solve testing problems through experiments and discussions on topics like impact mapping, testing quadrants, skills development, tool selection, technical debt, and test automation. Attendees will identify their biggest testing challenges, prioritize them, and brainstorm experiments to address high priority problems through techniques like impact mapping and story mapping. The workshop provides resources and examples to facilitate these discussions.
Do testers have to code... to be useful? Janet Gregory and Lisa Crispin plena...
This document discusses whether testers need to code to be useful on agile teams. It notes that while development teams already have coders, testers can add unique value through specialized testing skills like exploratory testing and expertise in areas like security, performance, and user experience testing. The document advocates that testers develop technical awareness of tools and concepts used by the team, but that coding skills are not absolutely required as long as testers have strong thinking and collaboration skills. Testers should focus on competencies over prescribed roles and find ways to add value through skills like eliciting examples and communicating effectively with all team members.
Janet Gregory - Agile testing challenges Knowit 2014
The document is a presentation by Janet Gregory from DragonFire Inc about agile testing. It discusses challenges with agile testing such as testers not being fully integrated into the team. It provides suggestions for overcoming these challenges, such as automating testing, having testers involved in planning, and emphasizing collaboration across the entire team. The presentation also covers topics like testing throughout development, defining what constitutes finished work, and balancing automation with exploratory testing.
Effective Testing Practices in an Agile Environment
This is a practitioner’s view of testing and testing practices within an iterative development environment. We will explore the challenges of testing within such an environment and ways to better integrate the QA professional into what is inherently a developer-centric methodology. If quality is paramount, then we ought to move testing to the front of the line and test early and often. Automation lies at the heart of agility and we will look at how test automation techniques and test-first design philosophy might be applied at multiple-levels to drive quality.
The Agile Tester’s Mindset
Janet Gregory presented on the mindset change needed for agile testers. She discussed how testers should focus on collaboration, communication, and adding value beyond just finding bugs. Testers need to adopt a mindset of being analytical, curious, and skeptical. Gregory also covered different levels of testing from iteration to release level and techniques like exploratory testing, using examples, and mind mapping. She emphasized the importance of imagination and adapting different testing tools to context.
Anton Muzhailo - Practical Test Process Improvement using ISTQB
Here are a few potential questions from the document:
- What is the true value of ISTQB certifications beyond just checking a box for management? How can the knowledge be applied practically?
- How can metrics be designed and used effectively to assess quality and test coverage in an agile environment? What are some examples of valid and invalid metrics?
- What artifacts or information are useful to include in a test plan even for agile teams using tools like JIRA? How can a test plan provide value beyond just additional paperwork?
- What techniques can be used to effectively estimate defect severity when multiple testers with different perspectives are involved? How can consistency be achieved?
- How can root cause analysis be applied
Do testers have to code... to be useful?
This document discusses whether testers need to code in agile environments. It notes that while development teams already have coders, testers need technical awareness to collaborate effectively. Testers add unique value through skills like exploratory testing rather than coding. Technical awareness helps communication, but coding ability is not required as long as a tester understands frameworks and terminology. Testers should focus on competencies over roles and find ways to add value through skills like specialized testing.
Testing in the Wild
This document discusses strategies for handling non-ideal testing situations when adopting agile practices. It addresses problems like lack of test automation, test data issues, legacy reporting needs, geographic distribution of teams, and separation of testers and programmers. The proposed solutions generally involve starting small, using technology to facilitate remote collaboration, targeting important information in reports, and developing relationships between team members.
Code mashadvancedtopicsworkshop
This document outlines an agenda and discussion topics for an advanced agile testing workshop. The workshop will use collaborative problem solving and various brainstorming techniques. Attendees will work in groups to identify testing problems, set goals, and generate experiments to tackle issues. Techniques that will be used include impact mapping, brainwriting, drawing, and discussing solutions if participants had "superpowers". The goal is for attendees to leave with concrete experiments to help address their biggest testing challenges.
Refactoring Test Collaboration
Presented at Agile Testing Days US 2018
https://agiletestingdays.us/session/refactoring-test-collaboration/
Collective ownership for testing starts with understanding testing. Rework your team dynamics to evolve past duplication and improve performance through whole team testing. Take home practical patterns for improving your team's collaboration on testing. Because teams who own testing have more confidence in the customer value of their results.
As the Pragmatic Programmers say, "refactoring is an activity that needs to be undertaken slowly, deliberately, and carefully," so how do we begin? In this session, we will experience the complex interactions of an agile team focused on demonstrating customer value by answering a series a questions:
Where do testers get their ideas?
How are you planning to accomplish this proposed testing, tester?
Why not automate all the things?
Who is going to do this manual testing and how does it work?
How do we know whether we're testing the right things?
Build your own list of TODOs from these various practical collaboration approaches and begin deduping your team's testing for a better first day back at the office.
The Mindset Change for the Agile Tester
On traditional projects, testers usually join the project after coding has started, or even later when coding is almost finished. Testers have no role in advising the project team early regarding quality issues but focus only on finding defects. They become accustomed to this style of working and adjust their mental processes accordingly. In agile, testers must collaborate closely with customers and programmers throughout the development lifecycle, where their focus changes from finding defects to preventing them. Janet Gregory shares ways to change the tester’s mindset from “How can I break the software?” to “How can I help deliver excellent software?”—a critical mental shift on agile projects. Another facet of the mind-set change is learning how to test early and incrementally. Janet uses interactive exercises and examples to help you understand how effective this mindset change is—and how you can apply it on your agile projects.
Digital Transformation, Testing and Automation
The Digital Transformation is real. It is having a profound effect on how business is done and the nature of the systems required to deliver productive customer experiences and consequent business benefits.
Key Takeaways:
- What is the Digital Transformation and how does it affect testing?
- Some key findings from a recent and an ancient survey
- How to achieve testing and automation success.
To view the webinar, visit - http://testhuddle.com/resource/digital-transformation-testing-and-automation/
Similar to Agile Testing in the Enterprise 2016 (20)
Agile Testing: Learning Journeys for the Whole Team - Janet G @ CMBAgileConf ...
Agile Testing: Learning Journeys for the Whole Team - Janet G @ CMBAgileConf ...
Exploring Features and Stories for shared understanding workshop
Exploring Features and Stories for shared understanding workshop
STARCANADA 2013 Keynote: Lightning Strikes the Keynotes
STARCANADA 2013 Keynote: Lightning Strikes the Keynotes
Do testers have to code... to be useful? Janet Gregory and Lisa Crispin plena...
Do testers have to code... to be useful? Janet Gregory and Lisa Crispin plena...
Janet Gregory - Agile testing challenges Knowit 2014
Janet Gregory - Agile testing challenges Knowit 2014
Effective Testing Practices in an Agile Environment
Effective Testing Practices in an Agile Environment
Anton Muzhailo - Practical Test Process Improvement using ISTQB
Anton Muzhailo - Practical Test Process Improvement using ISTQB
Recently uploaded
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
Enterprise Resource Planning System in Telangana
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/
What is Augmented Reality Image Tracking
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
原版定制美国纽约州立大学奥尔巴尼分校毕业证学位证书原版一模一样
原版一模一样【微信：741003700 】【美国纽约州立大学奥尔巴尼分校毕业证学位证书】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
https://2024.springio.net/sessions/automated-software-refactoring-with-openrewrite-and-generative-ai/
在线购买加拿大英属哥伦比亚大学毕业证本科学位证书原版一模一样
原版一模一样【微信：741003700 】【加拿大英属哥伦比亚大学毕业证本科学位证书】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
Hand Rolled Applicative User Validation Code Kata
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
socradar-q1-2024-aviation-industry-report.pdf
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
Cracking the code review at SpringIO 2024
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
Transform Your Communication with Cloud-Based IVR Solutions
Discover the power of Cloud-Based IVR Solutions to streamline communication processes. Embrace scalability and cost-efficiency while enhancing customer experiences with features like automated call routing and voice recognition. Accessible from anywhere, these solutions integrate seamlessly with existing systems, providing real-time analytics for continuous improvement. Revolutionize your communication strategy today with Cloud-Based IVR Solutions. Learn more at: https://thesmspoint.com/channel/cloud-telephony
Codeigniter VS Cakephp Which is Better for Web Development.pdf
When deliberating between CodeIgniter vs CakePHP for web development, consider their respective strengths and your project requirements. CodeIgniter, known for its simplicity and speed, offers a lightweight framework ideal for rapid development of small to medium-sized projects. It's praised for its straightforward configuration and extensive documentation, making it beginner-friendly. Conversely, CakePHP provides a more structured approach with built-in features like scaffolding, authentication, and ORM. It suits larger projects requiring robust security and scalability. Ultimately, the choice hinges on your project's scale, complexity, and your team's familiarity with the frameworks.
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-fusion-buddy-review
AI Fusion Buddy Review: Key Features
✅Create Stunning AI App Suite Fully Powered By Google's Latest AI technology, Gemini
✅Use Gemini to Build high-converting Converting Sales Video Scripts, ad copies, Trending Articles, blogs, etc.100% unique!
✅Create Ultra-HD graphics with a single keyword or phrase that commands 10x eyeballs!
✅Fully automated AI articles bulk generation!
✅Auto-post or schedule stunning AI content across all your accounts at once—WordPress, Facebook, LinkedIn, Blogger, and more.
✅With one keyword or URL, generate complete websites, landing pages, and more…
✅Automatically create & sell AI content, graphics, websites, landing pages, & all that gets you paid non-stop 24*7.
✅Pre-built High-Converting 100+ website Templates and 2000+ graphic templates logos, banners, and thumbnail images in Trending Niches.
✅Say goodbye to wasting time logging into multiple Chat GPT & AI Apps once & for all!
✅Save over $5000 per year and kick out dependency on third parties completely!
✅Brand New App: Not available anywhere else!
✅ Beginner-friendly!
✅ZERO upfront cost or any extra expenses
✅Risk-Free: 30-Day Money-Back Guarantee!
✅Commercial License included!
See My Other Reviews Article:
(1) AI Genie Review: https://sumonreview.com/ai-genie-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
#AIFusionBuddyReview,
#AIFusionBuddyFeatures,
#AIFusionBuddyPricing,
#AIFusionBuddyProsandCons,
#AIFusionBuddyTutorial,
#AIFusionBuddyUserExperience
#AIFusionBuddyforBeginners,
#AIFusionBuddyBenefits,
#AIFusionBuddyComparison,
#AIFusionBuddyInstallation,
#AIFusionBuddyRefundPolicy,
#AIFusionBuddyDemo,
#AIFusionBuddyMaintenanceFees,
#AIFusionBuddyNewbieFriendly,
#WhatIsAIFusionBuddy?,
#HowDoesAIFusionBuddyWorks
Utilocate provides Smarter, Better, Faster, Safer Locate Ticket Management
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
APIs for Browser Automation (MoT Meetup 2024)
APIs for Browser Automation:
Selenium, Cypress, Puppeteer, and Playwright. Ministry of Testing Athens. Meetup on the Beach. 30 May 2024.
Vitthal Shirke Java Microservices Resume.pdf
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
LORRAINE ANDREI_LEQUIGAN_HOW TO USE WHATSAPP.pptx
WhatsApp offers simple, reliable, and private messaging and calling services for free worldwide. With end-to-end encryption, your personal messages and calls are secure, ensuring only you and the recipient can access them. Enjoy voice and video calls to stay connected with loved ones or colleagues. Express yourself using stickers, GIFs, or by sharing moments on Status. WhatsApp Business enables global customer outreach, facilitating sales growth and relationship building through showcasing products and services. Stay connected effortlessly with group chats for planning outings with friends or staying updated on family conversations.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Recently uploaded (20)
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Transform Your Communication with Cloud-Based IVR Solutions
Transform Your Communication with Cloud-Based IVR Solutions
Codeigniter VS Cakephp Which is Better for Web Development.pdf
Codeigniter VS Cakephp Which is Better for Web Development.pdf
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
Utilocate provides Smarter, Better, Faster, Safer Locate Ticket Management
Utilocate provides Smarter, Better, Faster, Safer Locate Ticket Management
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Agile Testing in the Enterprise 2016
- 1. Agile Testing in the Enterprise Janet Gregory @janetgregoryca Janet Gregory, DragonFire Inc. Copyright 2016 Agile Testing Days, Potsdam 2016
- 2. Agile Testing; 2009 More Agile Testing: Oct 2014 Co-authored with Lisa Crispin Website: www.agiletester.com www.agiletester.ca DragonFire Inc. www.janetgregory.ca @janetgregoryca janet@agiletester.ca 2
- 3. Let’s learn a bit about your experiences - Less than 100 people - Larger than 1,000 employees - Larger than 5,000 - Different cities, same time zone (or 1 hr. apart) - Time zones more than 7 hrs difference - More than 3 remote teams - Others? 3
- 4. to share my experiences on how agile testing activities can span large teams… 4
- 5. Some of the challenges Plan for testing Key testing practices that work across teams 5 Sharing is caring
- 6. Large organizations that have enterprise applications and solutions @janetgregoryca
- 7. Small co-located teams: Agile’s sweet spot 7
- 8. Defined by its: ◦ Values, norms, assumptions ◦ Social system ◦ Visible artifacts Icons Rituals Vocabulary 8 @janetgregoryca
- 9. 9 How do we interact? Do you play the blame game? @janetgregoryca
- 10. • Bureaucracy • Reporting needs (real or imagined) • Orders handed down …. • Too many concurrent projects @janetgregoryca
- 11. • Organizational controls – regulatory, internal • Working with third parties • Involving customers in other locations • ERP system integration 11 @janetgregoryca
- 12. Other Testing Specific Issues Too many dependencies 12 Tester on more than one team
- 13. Some of the challenges Plan for testing Key testing practices that work across teams 13 Sharing is caring @janetgregoryca
- 14. Consider the feature Create testable stories Who tests what? 14 @janetgregoryca
- 15. ReleasePlanning Team A Planning Test Mind Map Team B Planning Team C Planning Team D Planning Release Test Matrix Release Test Planning / Approach
- 17. Lots of Stuff Shopping Release 1.5 DataIntegrity Look&Feel Calculations Currency Localization DevicesiPad DevicesiPhone BoundaryConditions Load/Performance Security Store customer information Add to shopping cart Calculate shipping costs Mobile iOs - view only Next feature Legend Good to Go Some testing; could use more Major issue No testing done Not applicable `
- 18. 18 Think in Levels of Detail
- 19. 19 Dependencies between teams Remove them before the iteration, but remember to test them @janetgregoryca
- 20. 20
- 22. 22
- 23. Each team responsible for delivering their feature -- completely Specialist teams report to the “owner” feature team. 23
- 24. Over-riding test strategy on how …. but • Understand who is testing what • What are the overlaps? • Where are the gaps? • Co-ordination between teams? • ASK: Who, when, how??? 24 @janetgregoryca
- 26. • Classes of tools • Involve teams in choosing tools • One size does not fit all ◦ But … be aware of too many tools for support or cross-training 26
- 27. • Same version control ◦ Understand the branching and merging approach • Same CI environment ◦ Use to visualize test results • Accessible & stable test environments ◦ Know what versions of applications are in each environment 27
- 28. Some of the challenges Plan for testing Key testing practices that work across teams 28 Sharing is caring @janetgregoryca
- 29. • What is the state of testability of your architecture? ◦ Can you simplify it for automation? • Regulatory ◦ simplest thing you can possibly do ◦ Consider NECESSARY artifacts – can you automate 29
- 30. • Power of 3 30 • Repeat verbal conversations in writing • Question • Draw pictures • Test ideas
- 31. • Aim for short feedback cycles • Remove dependencies early • Start with a test to remove assumptions 31 @janetgregoryca
- 32. We can use tests and examples for shared understanding and common language For example, create a function to add 2 numbers -2 + 1 = -1 2.0 + 1.050 = 3.050 2.0 + 1 = 3.0 2 + 1 = 3
- 33. @janetgregoryca
- 34. @janetgregoryca
- 35. Some of the challenges Plan for testing Key testing practices that work across teams 35 Sharing is caring @janetgregoryca
- 36. Sharing information, that is Transparency means less blame • No hiding • No secrets • No gaming the system The hard part is making it visible 36 @janetgregoryca
- 37. • Share dependencies • Same vision • Same goal • Accessible to all • Keep everyone “in the loop” 37 @janetgregoryca
- 39. 39
- 40. 40
- 42. 42 Final note: I’m not advocating distributed teams or out-sourcing but if you are faced with those problems, I hope you can use some of these ideas to help manage your agile testing. and Agile ≠ NO DOCUMENTATION Know your own context!
- 43. Agile Testing: A Practical Guide for Testers and Agile Teams More Agile Testing: Learning Journeys for the Whole Team By Janet Gregory and Lisa Crispin www.agiletester.ca www.agiletester.com Contact info www.janetgregory.ca Email: janet@agiletester.ca Twitter: janetgregoryca 43