Manual functional testing is a slow, tedious, and error prone process. As we continue to incrementally build software, the corresponding regression test suite continues to grow. Rarely is time allotted to consolidate and keep these test cases in sync with the product under development. If these test cases are used as the basis for automation, the resulting suite is composed of very granular tests that are often quite brittle in nature. Using a case study, Anand Bagmar describes how behavior-driven testing (BDT) can be applied to identify the right type of test cases for manual and automated regression testing. Learn how the BDT technique can be applied in your context and domain, regardless of the tools and technologies used in your project and organization.
Anand Bagmar - Behavior Driven Testing (BDT) in AgileAnand Bagmar
I delivered this talk in SiliconIndia's SoftTec 2012 on 14th July 2012. I introduce Behavior Driven Testing (BDT) with a couple of examples, the different ways of writing the tests in Imperative and Declarative style, the value proposition of BDT, and how BDT can help you build a very good safety net using Test Automation suite.
As more and more companies are moving to the Cloud, they want their latest, greatest software features to be available to their users as quickly as they are built. However there are several issues blocking them from moving ahead.
One key issue is the massive amount of time it takes for someone to certify that the new feature is indeed working as expected and also to assure that the rest of the features will continuing to work. In spite of this long waiting cycle, we still cannot assure that our software will not have any issues. In fact, many times our assumptions about the user's needs or behavior might itself be wrong. But this long testing cycle only helps us validate that our assumptions works as assumed.
How can we break out of this rut & get thin slices of our features in front of our users to validate our assumptions early?
Most software organizations today suffer from what I call, the "Inverted Testing Pyramid" problem. They spend maximum time and effort manually checking software. Some invest in automation, but mostly building slow, complex, fragile end-to-end GUI test. Very little effort is spent on building a solid foundation of unit & acceptance tests.
This over-investment in end-to-end tests is a slippery slope. Once you start on this path, you end up investing even more time & effort on testing which gives you diminishing returns.
In this session Naresh Jain will explain the key misconceptions that has lead to the inverted testing pyramid approach being massively adopted, main drawbacks of this approach and how to turn your organization around to get the right testing pyramid.
Test Driven Development via Agile TestingAnand Bagmar
The following topics are covered:
• Overview of Agile Testing
• The Test Pyramid
• Different flavors of TDD
o BDD – Behavior Driven Development
o ATDD – Acceptance Driven Development
o BDT – Behavior Driven Testing
• Difference between BDD and BDT
• Tools that support BDT
• The value proposition of BDT
In "vodQA - Testing and Beyond" held in March 2012 in ThoughtWorks Pune, Anand Bagmar spoke about - "What is Behavior Driven Testing (BDT)? How does it differ from Behavior Driven Development? What tools support this kind of testing? The value proposition BDT offers."
As a follow-up to that introduction to BDT, we conducted a Behavior Driven Testing (BDT) workshop in the ThoughtWorks Pune office. This workshop was the first in a series of vodQA Geek Nights.
For more information about the workshop, visit https://www.facebook.com/groups/vodqa/
The Test Automation Pyramid is a useful model to help us understand and discuss automated testing efforts. Generally speaking it is a good practice to have lots of unit tests, fewer component integration tests, fewer API tests, and even fewer UI tests.
Build the "right" regression suite using Behavior Driven Testing (BDT)Anand Bagmar
Behavior Driven Testing (BDT) is an evolved way of thinking about Testing. It helps in identifying the 'correct' scenarios, in form of user journeys, to build a good and effective (manual & automation) regression suite that validates the Business Goals.
Anand Bagmar - Behavior Driven Testing (BDT) in AgileAnand Bagmar
I delivered this talk in SiliconIndia's SoftTec 2012 on 14th July 2012. I introduce Behavior Driven Testing (BDT) with a couple of examples, the different ways of writing the tests in Imperative and Declarative style, the value proposition of BDT, and how BDT can help you build a very good safety net using Test Automation suite.
As more and more companies are moving to the Cloud, they want their latest, greatest software features to be available to their users as quickly as they are built. However there are several issues blocking them from moving ahead.
One key issue is the massive amount of time it takes for someone to certify that the new feature is indeed working as expected and also to assure that the rest of the features will continuing to work. In spite of this long waiting cycle, we still cannot assure that our software will not have any issues. In fact, many times our assumptions about the user's needs or behavior might itself be wrong. But this long testing cycle only helps us validate that our assumptions works as assumed.
How can we break out of this rut & get thin slices of our features in front of our users to validate our assumptions early?
Most software organizations today suffer from what I call, the "Inverted Testing Pyramid" problem. They spend maximum time and effort manually checking software. Some invest in automation, but mostly building slow, complex, fragile end-to-end GUI test. Very little effort is spent on building a solid foundation of unit & acceptance tests.
This over-investment in end-to-end tests is a slippery slope. Once you start on this path, you end up investing even more time & effort on testing which gives you diminishing returns.
In this session Naresh Jain will explain the key misconceptions that has lead to the inverted testing pyramid approach being massively adopted, main drawbacks of this approach and how to turn your organization around to get the right testing pyramid.
Test Driven Development via Agile TestingAnand Bagmar
The following topics are covered:
• Overview of Agile Testing
• The Test Pyramid
• Different flavors of TDD
o BDD – Behavior Driven Development
o ATDD – Acceptance Driven Development
o BDT – Behavior Driven Testing
• Difference between BDD and BDT
• Tools that support BDT
• The value proposition of BDT
In "vodQA - Testing and Beyond" held in March 2012 in ThoughtWorks Pune, Anand Bagmar spoke about - "What is Behavior Driven Testing (BDT)? How does it differ from Behavior Driven Development? What tools support this kind of testing? The value proposition BDT offers."
As a follow-up to that introduction to BDT, we conducted a Behavior Driven Testing (BDT) workshop in the ThoughtWorks Pune office. This workshop was the first in a series of vodQA Geek Nights.
For more information about the workshop, visit https://www.facebook.com/groups/vodqa/
The Test Automation Pyramid is a useful model to help us understand and discuss automated testing efforts. Generally speaking it is a good practice to have lots of unit tests, fewer component integration tests, fewer API tests, and even fewer UI tests.
Build the "right" regression suite using Behavior Driven Testing (BDT)Anand Bagmar
Behavior Driven Testing (BDT) is an evolved way of thinking about Testing. It helps in identifying the 'correct' scenarios, in form of user journeys, to build a good and effective (manual & automation) regression suite that validates the Business Goals.
Learn how you can use the Test Pyramid from Mike Cohn to guide how to scale your QA test automation while keeping it effective and fast. As your product and team scales it is really important to have a solid framework in place which allows your test automation to scale for the various layers of your product and your teams.
Behavior-Driven Development (BDD) is a set of software engineering practices designed to help teams build and deliver more valuable, higher quality software faster.
Baking In Quality: The Evolving Role of the Agile TesterTechWell
While more and more organizations are practicing agile development methodologies, many have not learned how to “bake in quality” throughout the process. As an agile tester, you are an integral part of the development team—working on requirements, design, implementation, writing automated tests, and testing However, are all team members working together as they should to ensure quality from day one through final delivery? Dena Laterza offers proven tips to help you and your team make the cultural shift to adopt and foster a “quality first” team standard. Gain an understanding of a tester's involvement in test-driven development and behavior-driven development. Take back new ideas on automating tests, working with stakeholders, and becoming a fully informed tester. Learn how to push testing back into development and maximize the value of testers on the team. Take back a plan to get your agile team working together—as a team.
Does your functional automation really add value?Anand Bagmar
We all know that automation is one of the key enablers for those on the CI-CD journey.
Most teams are:
• implementing automation
• talking about its benefits
• up-skilling themselves
• talking about tooling
• etc.
In my experience, unfortunately most of the functional automation that is built is:
• not optimal
• not fit-for-purpose
• does not run fast enough
• gives inconsistent feedback, hence unreliable
Hence, for the amount of effort invested in implementing automation, are you really getting the value from this activity?
In this talk, we will discuss these challenges and why it would lead to poor ROI of automation. More importantly, we will discuss the following techniques to make automation valuable:
• know the objective for the automation framework
• establish criteria for tests to be automated
• design your framework with proper abstraction layers
• develop using appropriate design patterns
Reaching for Your Quality Stretch Goals: Testing at Realtor.comKlaus Salchner
A/B Testing
If you are not familiar yet, an introduction to A/B testing and how you can leverage this approach to truly measure customer impact before and after a change. It's a practice highly leveraged in the e-commerce and cloud space to truly measure the impact of a change and be able to iterate through it till you see the desired outcome.
Where in your stack to invest in test automation
This short talk will explain in which layer to invest in test automation and the pros and cons. Too many teams still invest heavily in automated UI testing which then results in large test automation suites once the platform grows while still not being able to catch critical quality issues before they reach customers.
Testing for reliability, resilience and recovery
Your customer experience is also impacted by how reliable your application is. How do you test for reliability. But also how do you build and test for resilience, as guaranteed reliability is unachievable and the closer you get the costlier it becomes. Lastly how do you test for recovery, so once an outage or partial outage happened how to you recover, and how do you prepare for that recovery.
Lightning talk about Selenium WebDriver UI automation. Cross platform, cross browser. Code samples provided. Presented at YVR Testing meetup on May 4, 2016.
Tied to presentation by Klaus Salchner at http://www.slideshare.net/ksalchner/how-to-scale-your-test-automation
How to Add Test Automation to your Quality Assurance ToolbeltBrett Tramposh
SQA job postings are still in abundance, but it is rare to find one that does not include some form of test automation pedigree. Brett will present the topic and then lead the discussion as we explore the various paths to building your test automation acumen, and learn how to add this valuable skill-set to your resume. If you are already an SQA with test automation experience we encourage you to participate and bring your learning forward and into the discussion where we will compare and contrast Computer Science degrees, Code Camps, licensed automation tools such as HP UFT (QTP), test frameworks and scripting tools such as jMeter and SOAPUI. There is much to explore on this topic and we want everyone to leave with a few key areas they can start building on today.
Agile Methodology is not new. Many organisations / teams have already adopted Agile way of Software Development or are in the enablement journey for the same. What does this mean for Testing? There is no doubt that the Testing approach and mindset also needs to change to be in tune with the Agile Development methodology.
Learn what does it mean to Test on Agile Projects and how Test Automation approach needs to change for the team to be successful! Also learn why is Test Automation important, and how do we implement a good, robust, scalable and maintainable Test Automation framework!
Advanced Structures India was established with a motive to address the rising demand for better engineered products in India, particularly in Passenger, Commercial and Agricultural Vehicles segment
Through the webinar, she will give an introduction to the user story concept. How to create them? How they can help us build better products for our customers. Do's and Don'ts.
Specification by Example - Agile India 2015Ankur Sambhar
We all know the importance of validating a feature before committing to getting it built. Validating assumptions help in avoiding the most frustrating and common problem – building something that nobody wants. However, validation is easier said than done. Building the right feature before we think of building the feature right is the key.
Being Agile, we always try to leverage the quick feedback loop and adapt based on the end-user feedback. That’s good but it should not be used to validate the assumptions and that too after implementing a feature based on that assumption. It’s very expensive smile
A more powerful and productive technique is to leverage Specification-by-example in defining and discovering requirements collaboratively with end-user, even before start working on the feature.
This talk will focus on highlighting key aspects of effectively adopting SBE technique based on my own experience leveraging it successfully over and over again. It not only helps in grooming the feature requirement to tell a clear , simple and compelling story but it also helps in removing what is not needed.
Lean Entrepreneurship for Software ProfessionalsTechWell
Software teams are faced with the prospect of building a product, only to have unexpected shifts in customer demand, changes in the competitive landscape, or swings in the economic climate undermine their plans and turn their product into expensive waste. What is an entrepreneurially-minded software developer, designer, or tester to do? Thomas Vaniotis guides you toward a shift in thinking that is manifest in the Lean Startup and Lean UX movement. Learn to value information that comes from quickly exposing an idea to market pressures rather than considering the delivery of a particular feature as the goal. Identify wasteful activities in your product cycle and re-invest that energy by innovating around the build-measure-learn loop that drives value. Lean thinking and using meaningful production data to drive decisions will assist you—whether a tester, developer, product manager, or designer—in operating under the uncertain conditions of modern markets, regardless of your company’s age or size.
Emerging Product Owner Patterns in Large OrganizationsTechWell
Many organizations are actively searching for the perfect product owner—a unicorn who knows all about the product, anticipates the market, innovates, and improves the product’s quality and architecture, all while making and meeting commitments to the organization. That's a difficult if not impossible role to fill. So, how can we achieve these goals? Various enterprise patterns of scaling the product owner are emerging including the technical product owner, the proxy, the product owner team, the program team, the market manager, and the innovator. Tim Wise describes where each is applicable in large enterprises. Learn how to apply these approaches to both a service organization and a product development organization. Get a glimpse into the evolution that will influence product owner roles in large organizations as companies scale agile in the enterprise. Leave with knowledge of patterns that are emerging in large enterprises around the product owner.
Learn how you can use the Test Pyramid from Mike Cohn to guide how to scale your QA test automation while keeping it effective and fast. As your product and team scales it is really important to have a solid framework in place which allows your test automation to scale for the various layers of your product and your teams.
Behavior-Driven Development (BDD) is a set of software engineering practices designed to help teams build and deliver more valuable, higher quality software faster.
Baking In Quality: The Evolving Role of the Agile TesterTechWell
While more and more organizations are practicing agile development methodologies, many have not learned how to “bake in quality” throughout the process. As an agile tester, you are an integral part of the development team—working on requirements, design, implementation, writing automated tests, and testing However, are all team members working together as they should to ensure quality from day one through final delivery? Dena Laterza offers proven tips to help you and your team make the cultural shift to adopt and foster a “quality first” team standard. Gain an understanding of a tester's involvement in test-driven development and behavior-driven development. Take back new ideas on automating tests, working with stakeholders, and becoming a fully informed tester. Learn how to push testing back into development and maximize the value of testers on the team. Take back a plan to get your agile team working together—as a team.
Does your functional automation really add value?Anand Bagmar
We all know that automation is one of the key enablers for those on the CI-CD journey.
Most teams are:
• implementing automation
• talking about its benefits
• up-skilling themselves
• talking about tooling
• etc.
In my experience, unfortunately most of the functional automation that is built is:
• not optimal
• not fit-for-purpose
• does not run fast enough
• gives inconsistent feedback, hence unreliable
Hence, for the amount of effort invested in implementing automation, are you really getting the value from this activity?
In this talk, we will discuss these challenges and why it would lead to poor ROI of automation. More importantly, we will discuss the following techniques to make automation valuable:
• know the objective for the automation framework
• establish criteria for tests to be automated
• design your framework with proper abstraction layers
• develop using appropriate design patterns
Reaching for Your Quality Stretch Goals: Testing at Realtor.comKlaus Salchner
A/B Testing
If you are not familiar yet, an introduction to A/B testing and how you can leverage this approach to truly measure customer impact before and after a change. It's a practice highly leveraged in the e-commerce and cloud space to truly measure the impact of a change and be able to iterate through it till you see the desired outcome.
Where in your stack to invest in test automation
This short talk will explain in which layer to invest in test automation and the pros and cons. Too many teams still invest heavily in automated UI testing which then results in large test automation suites once the platform grows while still not being able to catch critical quality issues before they reach customers.
Testing for reliability, resilience and recovery
Your customer experience is also impacted by how reliable your application is. How do you test for reliability. But also how do you build and test for resilience, as guaranteed reliability is unachievable and the closer you get the costlier it becomes. Lastly how do you test for recovery, so once an outage or partial outage happened how to you recover, and how do you prepare for that recovery.
Lightning talk about Selenium WebDriver UI automation. Cross platform, cross browser. Code samples provided. Presented at YVR Testing meetup on May 4, 2016.
Tied to presentation by Klaus Salchner at http://www.slideshare.net/ksalchner/how-to-scale-your-test-automation
How to Add Test Automation to your Quality Assurance ToolbeltBrett Tramposh
SQA job postings are still in abundance, but it is rare to find one that does not include some form of test automation pedigree. Brett will present the topic and then lead the discussion as we explore the various paths to building your test automation acumen, and learn how to add this valuable skill-set to your resume. If you are already an SQA with test automation experience we encourage you to participate and bring your learning forward and into the discussion where we will compare and contrast Computer Science degrees, Code Camps, licensed automation tools such as HP UFT (QTP), test frameworks and scripting tools such as jMeter and SOAPUI. There is much to explore on this topic and we want everyone to leave with a few key areas they can start building on today.
Agile Methodology is not new. Many organisations / teams have already adopted Agile way of Software Development or are in the enablement journey for the same. What does this mean for Testing? There is no doubt that the Testing approach and mindset also needs to change to be in tune with the Agile Development methodology.
Learn what does it mean to Test on Agile Projects and how Test Automation approach needs to change for the team to be successful! Also learn why is Test Automation important, and how do we implement a good, robust, scalable and maintainable Test Automation framework!
Advanced Structures India was established with a motive to address the rising demand for better engineered products in India, particularly in Passenger, Commercial and Agricultural Vehicles segment
Through the webinar, she will give an introduction to the user story concept. How to create them? How they can help us build better products for our customers. Do's and Don'ts.
Specification by Example - Agile India 2015Ankur Sambhar
We all know the importance of validating a feature before committing to getting it built. Validating assumptions help in avoiding the most frustrating and common problem – building something that nobody wants. However, validation is easier said than done. Building the right feature before we think of building the feature right is the key.
Being Agile, we always try to leverage the quick feedback loop and adapt based on the end-user feedback. That’s good but it should not be used to validate the assumptions and that too after implementing a feature based on that assumption. It’s very expensive smile
A more powerful and productive technique is to leverage Specification-by-example in defining and discovering requirements collaboratively with end-user, even before start working on the feature.
This talk will focus on highlighting key aspects of effectively adopting SBE technique based on my own experience leveraging it successfully over and over again. It not only helps in grooming the feature requirement to tell a clear , simple and compelling story but it also helps in removing what is not needed.
Lean Entrepreneurship for Software ProfessionalsTechWell
Software teams are faced with the prospect of building a product, only to have unexpected shifts in customer demand, changes in the competitive landscape, or swings in the economic climate undermine their plans and turn their product into expensive waste. What is an entrepreneurially-minded software developer, designer, or tester to do? Thomas Vaniotis guides you toward a shift in thinking that is manifest in the Lean Startup and Lean UX movement. Learn to value information that comes from quickly exposing an idea to market pressures rather than considering the delivery of a particular feature as the goal. Identify wasteful activities in your product cycle and re-invest that energy by innovating around the build-measure-learn loop that drives value. Lean thinking and using meaningful production data to drive decisions will assist you—whether a tester, developer, product manager, or designer—in operating under the uncertain conditions of modern markets, regardless of your company’s age or size.
Emerging Product Owner Patterns in Large OrganizationsTechWell
Many organizations are actively searching for the perfect product owner—a unicorn who knows all about the product, anticipates the market, innovates, and improves the product’s quality and architecture, all while making and meeting commitments to the organization. That's a difficult if not impossible role to fill. So, how can we achieve these goals? Various enterprise patterns of scaling the product owner are emerging including the technical product owner, the proxy, the product owner team, the program team, the market manager, and the innovator. Tim Wise describes where each is applicable in large enterprises. Learn how to apply these approaches to both a service organization and a product development organization. Get a glimpse into the evolution that will influence product owner roles in large organizations as companies scale agile in the enterprise. Leave with knowledge of patterns that are emerging in large enterprises around the product owner.
Never underestimate the power of sharing the testing team’s achievements, lessons learned, challenges faced, roadblocks encountered, and the enriching solutions found. Jyothi Rangaiah says as testers we must be ready to nurture the needs of testing and testers in the organizations we serve. Only people, learning every day and questioning the norm, can and will move testing forward. Getting into this learning mode requires awareness of the need to improve. Jyothi discusses the importance of sharing the testing team’s everyday challenges and achievements with all involved. One person who cares for the quality of testing often can change the perception of testing in an organization. The internal corporate social networking site can be a good start to spread awareness and knowledge about testing. To test better, encourage and uphold the ways that are already beneficial. Network with the interested and the influential, and help each other understand the current state of affairs of testing.
Agile Adoption in Risk-Averse EnvironmentsTechWell
Adopting agile development methods in a conservative environment can be a daunting and time-consuming venture, facing resistance at all levels of the organization. You may wonder: Will this organization ever get with the times? Will our leaders ever change their way of thinking? Brian Duncan shares personal experiences and lessons learned in bringing an agile development mindset to two distinct organizations—a bottom-line product-driven software development organization, and the conservative, risk-averse Space Department at the Johns Hopkins Applied Physics Laboratory. Sharing the Good (what worked well), the Bad (what set us back), and the Ugly (what we had to abandon), Brian shows how to bring a slow-to-change organization into the forward-thinking agile methods of today. He presents practical approaches (adoption committees, grassroots techniques) and creative endeavors (free classes, an innovation lab) along with their impact on the organization. With persistence and a multifaceted approach, even risk-averse organizations can adopt agile.
Today, organizations are rapidly deploying mobile versions of their customer-facing and internal applications. With the prevalence of more agile-based approaches and the challenge of an ever-increasing diversity of devices and OS versions, testers are being asked to accomplish more testing in less time. Rachel Obstler shares how leading enterprises are improving the efficiency of their mobile testing using automation, and how they identify the right processes and tools for the job. Sharing some fascinating statistics from their recent mobile quality survey of more than 69,000 mobile app developers and QA organizations in the top US enterprises, Rachel dives into the challenges identified in the survey and shares five clear ways to improve your testing process: implementing a collaborative agile process, optimizing with a development tool that naturally facilitates testing, using a combination of real and emulated devices—and when to use them, and more.
Know any testers who have bugs opened more than a year ago and still sitting in their defect queue? More than two years ago? Three? The fact is that many software development efforts are focused on delivering new features and functionality, leaving workarounds in place for bugs released in prior versions of applications. Often these defects seem relatively minor—we all have some workarounds for customers—but these are still bugs and ultimately should be dealt with. If you are seeking effective methods to close out those bugs once and for all, Shaun Bradshaw shares his experience eradicating aging bugs—in a Bugfest! Shaun shows how to effectively use kanban techniques to bring visibility to a myriad of outstanding problems left over from previous releases as well as to order and prioritize the work to clear out the nastiest, most offensive defects—and ultimately exterminate those pesky bugs!
Accelerate Testing in Agile through a Shared Business Domain LanguageTechWell
In agile projects, when the cycle from ideas to production shortens from months to hours, each software development activity—including testing—is impacted. Reaching this level of agility in testing requires massive automation. But test execution is only one side of the coin. How do we design and maintain tests at the required speed and scale? Testing should start very early in the development process and be used as acceptance criteria by the project stakeholders. Early test design, using a business domain language to write tests, is an efficient solution to support rapid iterations and helps align the team on the definition of done. These principles are the basis of acceptance test-driven development practices. Laurent Py shows you how the use of business domain languages enables test refactoring and accelerates automation. Come and learn how you can leverage acceptance tests and key test refactoring techniques.
Using the Cloud to Load Test and Monitor Your ApplicationsTechWell
Load testing is often one of the most difficult testing efforts to set-up—in both time for the deployment and cost for the additional hardware needed. Using cloud-based software, you can transform this most difficult task to one of the easiest. Charles Sterling explains how load testing fits into the relatively new practice of DevOps. Then, by re-using the tests created in the load testing effort to monitor applications, the test team can help solve the challenges in measuring, monitoring, and diagnosing applications―not just in development and test but also into production. Chuck demonstrates web performance test creation, locally run load test creation, cloud executed load test to the cloud, application performance monitoring (APM), global system monitoring (GSM), and usage monitoring (UM) for near real-time customer input for your application.
Our Journey to Agile in the Microsoft Developer DivisionTechWell
This is the story about the Microsoft Developer Division and their two-year journey to agile—from shipping every three years to shipping every three weeks. In the old days, long stabilization phases were part of its DNA. Managers were rewarded for micromanagement. Commitments were made months in advance. Maintaining the appearance of meeting commitments was valued over transparency. Gregg Boer shares how this organization within Microsoft transitioned to one that values agile principles—controlling technical debt, enabling teams, eliminating bogus commitments, and rewarding transparency. When applying agile to such a large, traditional organization, the key to success is allowing autonomy at the team level, while ensuring alignment with the organization. Gregg shares successes as well as colossal failures. Learn how management sets direction while teams own their own backlog, how communication up and down can be transparent and healthy, and other lessons on their journey to agile.
Using DevOps to Improve Software Quality in the CloudTechWell
DevOps is gaining popularity as a way to quickly and successfully deploy new software. With all the emphasis on deployment, software quality can sometimes be overlooked. In order to understand how DevOps and software testing mesh, Glenn Buckholz demonstrates a fully implemented continuous integration/continuous delivery (CI/CD) stack. After describing the internals of how CI/CD works, Glenn identifies the touch points in the stack that are important for testing organizations. With the now accelerated ability to deliver software, the testing groups need to know how this technology works and what to do with it because swarms of manual testers will not be able to keep up. Glenn demonstrates where and how to use automated testing, how to collect and make sense of the massive amount of test results that can be generated from CI/CD, and how to usefully apply manual testing.
Don't Bulldoze a Vibrant Ecosystem for AgileTechWell
Software processes are commonly portrayed using machine metaphors in which consistency is highly prized. Frequently, organizations set up Centers of Excellence in a well-intentioned effort to create enterprise consistency. Steve Adolph reminds us that, in reality, software development takes place in a diverse ecosystem of corporate policies, competing interests, personal agendas, personality types, and a variety of formal and informal relationships. An aggressive top down imposition of practices is like sending a bulldozer through an ecosystem. This can create a prized consistency, but it also can destroy the environment’s productive vibrancy. It does not matter if the bulldozer says waterfall or agile on the side—it’s still a bulldozer. How do we live in harmony with our ecosystem? We can start by replacing machine metaphors with biological ones about leveraging and embracing diversity. Then use these metaphors to interpret two case studies of how organizations either bulldozed their ecosystem or learned to boost their productivity by living in harmony with it.
Going Agile? Three Conversations to Have Before You StartTechWell
All too often, companies adopt a mission to “go agile” before truly understanding what that entails. Business managers are quick to jump on the agile bandwagon, believing that going agile will magically make projects happen faster. Teams are getting certified in Scrum believing it is the silver bullet that will suddenly make everyone more productive. Inevitably, cracks begin to develop, and expectations are not met, leaving everyone questioning the value of going agile at all. Heather Fleming and Justin Riservato say there is a better way! The truth is that going agile will result in more productive teams and faster delivery of projects—but only if everyone can agree on the rules of the game. Learn why gaining consensus on the principles of agile is more important than implementing a specific process. Explore how having three key conversations—about saying no to deadlines, ensuring business partner engagement, and experimenting with process—up front can save you from an agile disaster.
As cloud computing becomes of strategic importance in the enterprise, part of the solution is no longer on-premise but in the cloud, adding a layer of complexity. Edwin Chan demystifies performance testing of cloud systems and applications by addressing the following key questions: Is performance testing of cloud systems fundamentally different from testing on-premises applications? What are the best practices for performance testing of both cloud and on-premises systems? Performance testing of cloud systems is essentially the same as that of its on-premises counterpart with the exception of the key consideration of network latency. After clearing common misconceptions, Edwin shares the hot topic best practices—adopting an agile/lean methodology, conducting early performance testing, and automating the injection of test data. Discuss the challenges the testing team faces in these days of disruptive and fast-paced technology changes. Take back and apply some of the best practices that fit your organization’s need.
As testers, we can feel overwhelmed by the sheer volume of things that require our attention. We are pressured to meet the demands of a fast-paced development environment while grappling with the extreme complexities inherent in today’s software. How can we remember everything while prioritizing our work in a way that allows us to test thoroughly and with confidence? Kirk Lee shares how the proper use of checklists provides a lightweight yet powerful solution. Kirk explains how checklists can prevent forgetfulness, assist in assessing what is really important, and most importantly, free our minds from the mundane so we can reach the deeper levels of thought required to find the nastiest bugs. Take back foundational checklists and learn how to adapt them to your specific circumstance through defect and root-cause analysis. Kirk shares checklists focusing on quality attributes, test types, heuristics; and functional, security, performance, automation, and mobile testing.
Mobile Applications Testing: From Concepts to PracticeTechWell
As applications for smartphones and tablets become incredibly popular, organizations encounter increasing pressure to quickly and successfully deliver testing for these devices. When faced with a mobile testing project, many testers find it tempting to apply the same methods and techniques used for desktop applications. Although some of these concepts transfer directly, testing mobile applications presents its own special challenges. Max Saperstone says if you follow the same practices and techniques as you have before, you will miss critical defects. Learn how to effectively test mobile applications, and how to add more structure and organization to generate effective test ideas to exploit the capabilities and weaknesses of mobile devices. Max shares first-hand experiences with testing mobile applications and discusses how to address various challenges. Work on real problems on your own device and learn firsthand how to be productive while testing mobile applications.
Applying Lean Startup Principles to Agile ProjectsTechWell
Warning! You can still build the wrong product using agile. In Eric Ries’ book The Lean Startup, he poses the question: What if we found ourselves building something that nobody wanted? In that case, what would it matter if we did it on time and on budget? We often assume the Product Owner is smart enough to define the right product. But what if we are wrong? Michael Hall shares lean startup principles and how they can be applied to ensure that the product we are building is righteous. Learn new agile concepts such as hypothesis-driven project vision, knowledge broker personas, learning maps, minimum learning product, experiment backlogs, experiment test iterations, validated learning, and pivot/persevere decisions. Case studies and Michael’s first-hand product experience emphasize the learning points. New and mature agilistas alike will leave the session armed with Lean Startup agile techniques that can be applied immediately on their agile projects.
Build the "right" regression suite using Behavior Driven Testing (BDT)Anand Bagmar
Slides from the workshop conducted in ThoughtWorks, vodQA Gurgaon on - "What is BDT, and how can you use this technique to identify the 'right' regression suite for your product"
Agile Testing Framework - The Art of Automated TestingDimitri Ponomareff
Once your organization has successfully implemented Agile methodologies, there are two major areas that will require improvements: Continuous Integration and Automated Testing.
This presentation illustrates why it's important to invest in an Automated Testing Framework (ATF) to reduce technical debt, increase quality and accelerate time to market.
Learn more at www.agiletestingframework.com.
The complete guide to BDD + Cucumber Best Practices and Anti-Patterns.Test Evolve
BDD and tools like Cucumber, when used correctly, should add significant value to your organisation’s project delivery, product quality and customer satisfaction.
…when used correctly…
And herein lies the problem. They are highly prone to unintentional misuse that quickly diminishes their value-add.
More often than not, the process and the tools are used poorly and in a manner far from the intention of the teams that built them.
In this webinar, we’ll take you through the complete guide of firmly accepted best practices to embrace and anti-patterns to avoid when starting to use these tools and processes in your organisation.
Quality Jam: BDD, TDD and ATDD for the EnterpriseQASymphony
During Quality Jam 2016 I had the privilege of presenting with one of QASymphony's earliest customers, Better Cloud, on how methodologies like BDD, TDD and ATDD scale for the enterprises. Adam Satterfield is the VP of Quality Assurance at Bettercloud and has been in QA for many years; he has taught me a lot about Behavior Driven Development, Test Driven Development, Acceptance Test Driven Development. In the session we share a new way of testing-- what Adam and I believe to be the next generation of testing development.
We know that there are several ways to do testing and we are just showing one new way to do it - If this session doesn't inspire action, hopefully it will at least give you and your team something to think about.
Let's explore what is agile testing, how agile testing is different than traditional testing. What practices team has to adopt to have parallel testing and how to create your own test automation framework. Test automation frameworks using cucumber, selenium, junit, nunit, rspec, coded UI etc.
Failure is an Option: Scaling Resilient Feature DeliveryOptimizely
Designing a perfect, failproof software delivery system is impossible. Failures will happen. What's more important is the speed and reliability of your recovery.
Shipping with feature flags helps you limit your risk in the first place and recover faster when the unexpected happens.
Today, with Optimizely Agent, companies that build their apps using service-oriented architectures can achieve production-scale faster with their feature delivery and experimentation platform.
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.
Continuous delivery requires more that DevOps. It also requires one to think differently about product design, development & testing, and the overall structure of the organization. This presentation will help you understand what it takes and why one would want to deliver value to your customers multiple times each day. #CIC
Jeff "Cheezy" Morgan Ardita Karaj
Automated verification is becoming increasingly important. Getting a product from idea to customer as fast as possible in a Continuous Delivery, or a Deployment pipeline is crucial in more businesses than ever before. But how do we get a product through that pipe line, with high quality? Kristian will talk about how automated verification can get you there.
Load and Performance Testing Services for Mobile Applications | Calidad InfotechCalidad Infotech
Validate the performance of a mobile application during high workloads. Performance testing allows product owners to measure the performance of the app.
Despite the belief that a shared context and collaboration drives quality, too often, software testers and quality professionals struggle to find their place within today's integrated agile teams. This session is a practitioner’s view of testing and testing practices within an iterative/incremental development environment. We will begin with a discussion of some of the challenges of testing within an agile environment and delve into the guiding principles of Agile Testing and key enabling practices. Agile Testing necessitates a change in mindset, and it is as much, if not more, about behavior, as it is about skills and tooling, all of which will be explored.
Continuous Performance Testing and Monitoring in Agile DevelopmentDynatrace
Continuous Performance Testing and Monitoring in Agile Development
Continuous Performance testing and monitoring is the best way to ensure application performance with quicker development cycles. Balancing agile and DevOps velocity with the need for ongoing performance testing and monitoring is essential. We call it Continuous Performance Validation.
In this webinar, we will show how you can get performance guidance and metrics throughout development, making sure apps perform well from inception to production and beyond.
In this webinar you will learn:
• How to automate performance testing and which tools you need to be successful
• How to use APM during load and performance testing
• How to create a continuous performance validation strategy from Dev to QA and Ops
• Ways teams can collaborate to ensure top application performance
Slides to my talk at NDC Oslo 2016: How to do a really good company wide product demo.
See how I tried to improve on the format of informing all people within the whole company about the latest product releases, the underlying user value and the KPIs each product can drive. It was an iterative process making use of PDCA, start from where you are and continuous learning principles.
Ben Walters - Creating Customer Value With Agile Testing - EuroSTAR 2011TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Creating Customer Value With Agile Testing by Ben Walters. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Similar to Build the Right Regression Suite with Behavior-Driven 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.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Build the Right Regression Suite with Behavior-Driven Testing
1. T14
Test Techniques
5/8/2014 1:30:00 PM
Build the Right Regression Suite
with Behavior-Driven Testing
Presented by:
Anand Bagmar
ThoughtWorks
Brought to you by:
340 Corporate Way, Suite 300, Orange Park, FL 32073
888-268-8770 ∙ 904-278-0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com
2. Anand Bagmar
ThoughtWorks
Anand Bagmar is a hands-on and result-oriented software quality evangelist with seventeen
years in the IT field. Passionate about shipping quality products, Anand specializes in building
automated testing tools, infrastructure, and frameworks. He writes testing-related blogs and has
built open-source tools related to software testing-WAAT (Web Analytics Automation Testing
Framework), TaaS (for automating integration testing in disparate systems), and TTA (Test
Trend Analyzer). Anand is the lead organizer for vodQA, the popular testing conference in India.
Follow him on Twitter @BagmarAnand, email him at abagmar@gmail.com, or read his Essence
of Testing blog.
3. Building
the
“right”
regression
suite
using
Behavior
Driven
Tes5ng
(BDT)
Anand
Bagmar
So#ware
Quality
Evangelist
Principal
Consultant,
ThoughtWorks
4. • “Succeeding
with
Agile”
–
Mike
Cohn
• MarCn
Fowler
–
Test
Pyramid
– hFp://marCnfowler.com/bliki/TestPyramid.html
The
Test
Pyramid
5. Func%onal
Tests
(GUI)
• Developers
&
/
QA
team
Web
Service
Tests
• Developers
&
/
QA
team
Integra%on
tests
• Developers
Component
tests
• Developers
Unit
Tests
• Developers
Test
AutomaCon
Pyramid
Manual
/
Exploratory
TesCng
Product
under
test
Ideal
Test
Pyramid
Business-‐
facing
Tests
Technology-‐
facing
Tests
• Cost
• Effort
• Time
8. Func%onal
Tests
(GUI)
• Developers
&
/
QA
team
Web
Service
Tests
• Developers
&
/
QA
team
Integra%on
tests
• Developers
Component
tests
• Developers
Unit
Tests
• Developers
Manual
/
Exploratory
TesCng
Test
Ice-‐cream
cone
Business-‐
facing
Tests
Technology-‐
facing
Tests
Test
Pyramid
–
AnC
PaFern
Product
under
test
9. Func%onal
Tests
(GUI)
• Developers
&
/
QA
team
Web
Service
Tests
• Developers
&
/
QA
team
Integra%on
tests
• Developers
Component
tests
• Developers
Unit
Tests
• Developers
Manual
/
Exploratory
TesCng
Product
under
test
Ideal
Test
Pyramid
Business-‐
facing
Tests
Technology-‐
facing
Tests
IdenCfy
the
right
type
of
tests
that
sit
on
top
of
the
Test
Pyramid
10. Case
Study
• MulCple,
long
running
projects
• Legacy
applicaCons
• Integrated
11. • Limited
AutomaCon
• Long
regression
cycle
• Huge
cost
of
fixing
defects
TesCng
Challenges
12. • No
visibility
into
what
is
tested
• Outdated
• BriFle
• LiFle
/
less
value
• Expensive
• Maintenance
nightmare
As
a
result
13. Biggest
problem
• Trust
deficit
on
the
team
– In
exisCng
AutomaCon
– In
manual
tesCng
• Finger
poinCng
/
blame
game
14.
15.
16. • Remove
the
ambiguity
• Same
visibility
for
all
17. EvoluCon
of
Test
Frameworks
Behavior
Driven
Development
(BDD)
OpCmized
scripts
Record
&
Playback
Core
Framework
21. The
Big
Picture
• How
is
this
funcConality
going
to
be
used
by
the
end-‐user?
• What
is
their
thought
process
going
to
be
when
using
this
product?
• What
is
the
“core-‐business-‐value”
I
am
delivering
to
the
end-‐user?
22. Func%onal
Tests
(GUI)
• Developers
&
/
QA
team
Web
Service
Tests
• Developers
&
/
QA
team
Integra%on
tests
• Developers
Component
tests
• Developers
Unit
Tests
• Developers
Manual
/
Exploratory
TesCng
Product
under
test
Ideal
Test
Pyramid
Business-‐
facing
Tests
Technology-‐
facing
Tests
IdenCfy
the
right
type
of
tests
that
sit
on
top
of
the
Test
Pyramid
23. Expected
Func%onality:
The
customer
should
be
able
to
withdraw
money
from
his
account
via
an
ATM
machine
An
example
24. Given
the
account
has
balance
of
INR
5000
When
the
customer
requests
INR
1000
Then
the
account
is
debited
by
INR
1000
BDD
Example:
25. Given
the
account
is
in
credit
And
the
dispenser
contains
cash
When
the
customer
requests
cash
Then
ensure
the
account
is
debited
And
ensure
cash
is
dispensed
And
ensure
the
card
is
returned
BDT
Example:
26. New
Expected
Func%onality:
The
customer
should
be
able
to
withdraw
money
from
his
account
only
if
his
card
is
valid
27. Given
the
account
is
in
credit
And
the
card
is
valid
And
the
dispenser
contains
cash
When
the
customer
requests
cash
Then
ensure
the
account
is
debited
And
ensure
cash
is
dispensed
And
ensure
the
card
is
returned
BDT
Example
-‐
updated:
29. • Write
user
flows
based
on
personas,
and
how
they
use
the
business
funcConality,
or,
• Write
business
flows,
and
how
different
user
personas
can
use
that
30. Another
example
For
Indigo
Airlines
website
–
• Guest
User
is
able
to
search
for
a
flight
for
a
single
traveller
• Ability
to
specify
contact
informaCon
for
person
booking
the
flight
32. ImperaCve
style
Given
I
am
a
guest
user
on
the
Indigo
home
page
And
I
select
“round”
trip
opCon
And
I
select
“Pune”
from
the
origin
dropdown
And
I
select
“Bangalore”
from
the
desCnaCon
drop
down
And
I
select
departure
date
as
“5
December
2013”
And
I
select
returning
date
as
“25
December
2013”
When
I
click
on
Search
Then
I
should
see
the
search
results
page
And
I
should
see
at
least
1
opCon
for
my
criteria
...
33. …
When
I
select
the
“first”
opCon
Then
I
am
on
the
Contact
InformaCon
page
When
I
enter
first
name
as
“foo”
And
I
enter
last
name
as
“bar”
…
…
And
I
click
the
“Select
and
Con%nue”
buFon
Then
I
should
be
on
the
next
page
34. Given
I
am
a
guest
user
When
I
search
for
flight
opCons
for
a
“one-‐way”
trip
for
“1”
“Adult”
from
“Delhi”
to
“Bangalore”
And
I
select
the
“first”
flight
And
I
enter
“valid”
contact
details
for
“traveller1”
Then
I
am
able
to
Save
and
ConCnue
DeclaraCve
style
36. DO
NOT
AUTOMATE
• Low
Value,
High
Cost
• Manual
Regression!
2nd
candidate
for
automa%on
• High
Value,
High
Cost
Automate
ONLY
if
you
have
%me
• Low
Value,
Low
Cost
• ?
Manual
Regression?
1st
candidate
for
automa%on
• High
Value,
Low
Cost
Cost
Value
37. Func%onal
Tests
(GUI)
• Developers
&
/
QA
team
Web
Service
Tests
• Developers
&
/
QA
team
Integra%on
tests
• Developers
Component
tests
• Developers
Unit
Tests
• Developers
BDT
helps
iden5fy
the
“right”
type
of
regression
tests!
Manual
/
Exploratory
TesCng
Product
under
test
Ideal
Test
Pyramid
42. Who
is
doing
the
acCon?
What
is
the
business
funcConality?
AcCons
and
verificaCons
happen
implicitly
Depicts
a
user
flow
Given
auc%oneer
creates
a
sale
And
5
items
are
added
to
the
sale
When
auc%oneer
starts
the
sale
And
auc%oneer
sets
a
starCng
bid
of
5000
And
buyer_1
bids
And
buyer_2
bids
Then
auc%oneer
Sells
the
item
And
buyer_2
wins
the
item
43. Final
state
Tests
running
on
Hudson
/
Jenkins
Since
1st
test
was
automated
Feature
files
33
Scenarios
65
Smoke
tests
execuCon
Cme
15
minutes
Regression
tests
execuCon
Cme
45
minutes
Test
case
repository
(manual
+
automated)
Cucumber
.feature
files
with
appropriate
tagging
Project
Management
tool
Mingle
44. ?
Incrementally
build
User
Flows
Regress
required
Product
Business
Value
Tests
in-‐sync
EffecCve
Tests
Remove
ambiguity
Understand
new
funcConality
Living
DocumentaCon
Onboarding
