Most of the people think that quality in software development is limited to manual testing on the latest stage before releasing a product. That might be true 20 years ago in the industrial era. But current world is much more dynamic than before. Time to market became the most crucial metric nowadays. Releasing code to production need to be done faster and faster. How to maintain quality on a sufficient level in this fast paced environment? How to find a time to work on quality improvements? Those are two main questions I want to answer during this talk. Do not expect a silver bullet or even receipt to success. But definitely expect a lot of information about continuous delivery/deployment/improvements with a case studies and lessons we learned at Spotify.
Spotify Engineering Culture:
https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/
https://labs.spotify.com/2014/09/20/spotify-engineering-culture-part-2/
Scaling Agile @ Spotify
http://blog.crisp.se/2012/11/14/henrikkniberg/scaling-agile-at-spotify
Scaled Agile @ Spotify
http://vimeo.com/111131934
Agile Testing – embedding testing into agile software development lifecycle Kari Kakkonen
My presentation on Agile Testing, including a tuning concept and a case study of agile testing choices in a project, held 16 of June, 2014 at a customer internal seminar.
"Experiences Of Test Automation At Spotify" with Kristian KarlTEST Huddle
View webinar: http://www.eurostarconferences.com/community/member/webinar-archive/webinar-87-experiences-of-test-automation-at-spotify-
At Spotify, we want the manual testing effort to be focused as much as possible at feature testing, less on regression tests. But we still have to do regression. So, we tried to automate a big chunk of that. Regression tests are run on our Desktop, Android, iOS and WebPlayer clients, and also some backend services.
I will share with you how far we have come. What techniques, tools and methodologies we have tried. What experiences has been good, and what has been not that good.
In this session, we would discuss what "Agile Testing" is, what are the well known methods and models of Agile Testing and what to expect on the future of Agile Testing.
The document discusses QA best practices in an Agile development environment. It describes key aspects of Agile like iterative delivery, self-organizing teams, and rapid feedback. It addresses challenges of fitting QA into short iterations and questions around testing approaches. The document advocates for testing to be collaborative, automated, and continuous throughout development. It provides recommendations for QA roles in activities like planning, stand-ups, retrospectives and acceptance testing. Overall it promotes testing practices in Agile that focus on early feedback, automation, and involvement of QA throughout the development process.
Role Of Qa And Testing In Agile 1225221397167302 8a34sharm
The document discusses the role of QA and testing in agile software development, describing key differences between traditional and agile testing approaches and outlining agile testing practices like test-driven development, continuous integration, regression testing, and exploratory testing. It also covers the role of testers in agile projects and provides an example of how one company, GlobalLogic, implements agile testing through a unique Velocity method and platform.
How Spotify Does Test Automation - Kristian KarlSmartBear
Kristian Karl's (@kristiankarl) presentation from MeetUI 2013, SoapUI's first user conference, in Stockholm, Sweden. Kristian is a test manager at Spotify.
Most of the people think that quality in software development is limited to manual testing on the latest stage before releasing a product. That might be true 20 years ago in the industrial era. But current world is much more dynamic than before. Time to market became the most crucial metric nowadays. Releasing code to production need to be done faster and faster. How to maintain quality on a sufficient level in this fast paced environment? How to find a time to work on quality improvements? Those are two main questions I want to answer during this talk. Do not expect a silver bullet or even receipt to success. But definitely expect a lot of information about continuous delivery/deployment/improvements with a case studies and lessons we learned at Spotify.
Spotify Engineering Culture:
https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/
https://labs.spotify.com/2014/09/20/spotify-engineering-culture-part-2/
Scaling Agile @ Spotify
http://blog.crisp.se/2012/11/14/henrikkniberg/scaling-agile-at-spotify
Scaled Agile @ Spotify
http://vimeo.com/111131934
Agile Testing – embedding testing into agile software development lifecycle Kari Kakkonen
My presentation on Agile Testing, including a tuning concept and a case study of agile testing choices in a project, held 16 of June, 2014 at a customer internal seminar.
"Experiences Of Test Automation At Spotify" with Kristian KarlTEST Huddle
View webinar: http://www.eurostarconferences.com/community/member/webinar-archive/webinar-87-experiences-of-test-automation-at-spotify-
At Spotify, we want the manual testing effort to be focused as much as possible at feature testing, less on regression tests. But we still have to do regression. So, we tried to automate a big chunk of that. Regression tests are run on our Desktop, Android, iOS and WebPlayer clients, and also some backend services.
I will share with you how far we have come. What techniques, tools and methodologies we have tried. What experiences has been good, and what has been not that good.
In this session, we would discuss what "Agile Testing" is, what are the well known methods and models of Agile Testing and what to expect on the future of Agile Testing.
The document discusses QA best practices in an Agile development environment. It describes key aspects of Agile like iterative delivery, self-organizing teams, and rapid feedback. It addresses challenges of fitting QA into short iterations and questions around testing approaches. The document advocates for testing to be collaborative, automated, and continuous throughout development. It provides recommendations for QA roles in activities like planning, stand-ups, retrospectives and acceptance testing. Overall it promotes testing practices in Agile that focus on early feedback, automation, and involvement of QA throughout the development process.
Role Of Qa And Testing In Agile 1225221397167302 8a34sharm
The document discusses the role of QA and testing in agile software development, describing key differences between traditional and agile testing approaches and outlining agile testing practices like test-driven development, continuous integration, regression testing, and exploratory testing. It also covers the role of testers in agile projects and provides an example of how one company, GlobalLogic, implements agile testing through a unique Velocity method and platform.
How Spotify Does Test Automation - Kristian KarlSmartBear
Kristian Karl's (@kristiankarl) presentation from MeetUI 2013, SoapUI's first user conference, in Stockholm, Sweden. Kristian is a test manager at Spotify.
Agile Testing - presentation for Agile User Groupsuwalki24.pl
The document discusses agile testing principles and processes. It compares agile testing to waterfall testing and outlines some key differences. It also addresses topics like continuous integration, test automation, managing test cases and issues, and transitioning from waterfall to agile. Pseudo-agile projects are described as those that claim to use agile but lack key elements like automation, continuous integration, or involvement of testers throughout the process.
The document provides an overview of agile scrum testing methodology. It describes agile testing as testing practices that follow the agile manifesto and treat development as the customer of testing. It then outlines the key aspects of scrum testing including product backlogs, sprints, daily standup meetings, sprint planning and retrospectives. It also discusses the proposed scrum testing process of identifying test scenarios, writing test cases per sprint, delayed execution, and inclusion of defects in the product backlog.
Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.
Cypress is an end-to-end testing framework that focuses on doing testing well through features like time travel debugging, real-time reloads, and automatic waiting. It works on any frontend framework and tests are written in JavaScript alone. Cypress provides an all-in-one solution for developers and QA engineers to set up testing, write Cucumber tests, run and debug tests from a dashboard or command line, and generate reports including screenshots, videos, and JUnit files.
Agile Testing: A pragmatic overview and new entry in Intelliware’s Agile Methodology Series.
What you’ll learn in this presentation:
Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment.
The presentation covers:
- Why do we use Agile testing?
- What Agile testing isn’t
- What Agile testing is: unit testing and test-driven development (TDD)
- High-level properties of good tests
- Testing in different languages
- Test suites and code coverage
- Using mock objects to help isolate units
- Beyond unit testing
Agile testing principles and practices - Anil KaradeIndicThreads
Traditional test processes are not adaptive to extensive changes in software. Agile process emphasizes on ability to adapt to changing business needs, customer collaboration, integrated teams and frequent delivery of business values. Agile is an umbrella term that describes a variety of methods including XP and Scrum.
The talk will discuss pitfalls of the traditional testing process. Traditional testing process happens very late in the SDLC Where as Agile process focuses on test-first approach. The talk will explain benefits of going agile. Principles and practices of agile process will be discussed and agile methodologies Scrum and Extreme Programming will be discussed in detail. Purpose of Scrum, its effectiveness, timings and managing the scrum will be discussed. Some of the practices for XP like Pair Programming, Test Driven Development will be discussed. The Talk will also cover the QA role in agile world. The talk will cover the implementation issues while shifting from traditional to agile process. Talk will also include an interactive game for illustration of concepts.
Introducing QA Into an Agile EnvironmentJoseph Beale
This document discusses introducing quality assurance (QA) processes into an agile development environment. It describes some common challenges that can arise when development and testing are not well integrated, such as business stakeholders finding bugs late in the process. The author advocates for making QA practices and results visible and incorporating QA personnel into agile ceremonies like planning and demos. With collaboration, commitment to quality, and clear communication, the QA team was able to gain trust and find bugs earlier. Their approach evolved to take on more types of testing, and they worked with business to define different testing levels and work testing around releases.
This document provides an overview of agile testing. It discusses what agile testing is, common agile testing strategies and stages, principles of agile testing, advantages such as reduced time and money and regular feedback, challenges like compressed testing cycles and minimal time for planning, and concludes that communication between teams is key to agile testing success. The agile testing life cycle involves four stages: iteration 0 for initial setup, construction iterations for ongoing testing, release for deployment, and production for maintenance. Principles include testing moving the project forward, testing as a continuous activity, everyone on the team participating in testing, and reducing feedback loops.
The document discusses the "test pyramid" concept for balancing test suites from unit to end-to-end tests. It provides examples of different types of tests including unit tests, integration tests, UI/end-to-end tests. It also discusses challenges with different types of tests and strategies for addressing those challenges including dependency injection, mocks, and tools like Cucumber, Robolectric, and Pacto. The document seeks feedback on testing approaches and provides additional resources on testing best practices.
Cypress is a testing tool that allows for fast, easy, and reliable testing of anything that runs in a browser. It differs from other tools in that it does not use Selenium, focuses on end-to-end testing, works on any front-end framework, uses only JavaScript for tests, and runs much faster than other options. Cypress tests the application as a real user would and allows debugging of test flows. It also supports plugins, common commands and assertions, and has a similar syntax to unit testing frameworks.
At AWS re:Invent, we have launched support for blue/green deployments for services hosted using AWS Fargate and Amazon Elastic Container Service (Amazon ECS). Blue/green deployments help you minimize downtime during application updates. They allow you to launch a new version of your application alongside the old version and test the new version before you reroute traffic to it. You can also monitor the deployment process and, if there is an issue, quickly roll back.
In this workshop, you will create a new service in AWS Fargate that uses AWS CodeDeploy to manage the deployments, testing, and traffic cutover for you.
Agile Testing: The Role Of The Agile TesterDeclan Whelan
This presentation provides an overview of the role of testers on agile teams.
In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value.
Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.
Test Automation Frameworks: Assumptions, Concepts & ToolsAmit Rawat
The document discusses factors to consider when selecting a test automation framework. It describes how there are many options for frameworks available and outlines important criteria to evaluate, such as flexibility, ability to support different applications and interfaces, tool and language independence, parallel execution, and design patterns. The presentation provides examples of different types of frameworks and discusses strategies for building frameworks that can scale and evolve with changing needs.
Organisations turn to Agile and DevOps to improve customer experience by maximising the speed of delivery without sacrificing quality. As the champions of quality, testers achieve this goal through continuous testing. Test Automation plays a major role in continuous testing; it is the backbone of the continuous test process. To achieve continuous testing, automation must be applied at every stage of the development process. Developing a smart automation strategy and using the right tools is critical in achieving continuous testing since test scripts must be scalable and easy to maintain.
From http://wiki.directi.com/x/AgAa - This is a 24 slide internal presentation covering virtues of Automated Testing vs Manual Testing. Inkeeping with our agile adoption this presentation covers various advantages (11 to be specific) obtained in using TDD and Automated Testing as opposed to Manual Testing
Cypress vs Selenium WebDriver: Better, Or Just Different? -- by Gil TayarApplitools
** Full webinar recording: https://youtu.be/D7vxFuwnUio **
Watch Sr. Architect Gil Tayar's special hands-on session, where he explains & demonstrates how Selenium and Cypress differ.
The session covers the following topics:
* How and why do frontend developers write tests
*Selenium architecture
*Cypress architecture
*Live Demo of Cypress - including how to write a Cypress test, and how it’s used
*How Cypress deals with flakiness
*Cypress and backdoors to development
*Visual Testing using Cypress
This is a presentation given at the Hangzhou Scrum Forum 2009, sponsored by Perficient, China. The topic is how to incorporate automated functional testing into an agile project, and also some best practices, tips, and warnings.
www.perficient.com
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.
Keynote: Testing and Quality in the Scaled Agile Framework for Lean Enterpris...Derk-Jan de Grood
This document summarizes a keynote presentation on testing and quality in the Scaled Agile Framework (SAFe) given by Mette Bruhn-Pedersen and Derk-Jan de Grood. It discusses how SAFe addresses testing and quality, but that more guidance could be provided, especially around roles. It also provides suggestions for defining a quality strategy and embedding quality practices at each level of the framework, from the team to portfolio levels. The presentation emphasizes building quality in from the start and establishing a chief quality officer role.
Developing a test automation strategy by Brian BayerQA or the Highway
The document discusses developing a test automation strategy and considerations for regression testing, automation, and frameworks. It addresses why regression testing is important, factors for the automation strategy like business needs and ROI, and frameworks to consider like Cucumber, Robot Framework, and Spock. The strategy determines test maintenance and fits within the organization, development process, and technology stacks.
A confused tester in agile world finalversionAshish Kumar
This document discusses challenges faced by testers in agile environments. It begins with a story of a confused tester and presents several case studies of different organizations' approaches to testing in agile projects. It identifies common challenges such as changing requirements, lack of information, testing pace, and skills. A survey found that test automation, risk tracking, and cross-functional teams are commonly implemented agile practices. The document concludes with principles of testing being a continuous responsibility of the whole team.
Lesley Wallace presents on challenges with testing within a Scrum sprint and provides solutions. She asks the audience questions about their testing practices. Wallace explains that everyone on the team is responsible for quality and testing. To test within a sprint, stories must have decreased scope and testing must only focus on the story's scope. If more time is needed for regression testing, a "hardening sprint" can be added before release. Automation helps with testing and there are tools for all budgets.
Agile Testing - presentation for Agile User Groupsuwalki24.pl
The document discusses agile testing principles and processes. It compares agile testing to waterfall testing and outlines some key differences. It also addresses topics like continuous integration, test automation, managing test cases and issues, and transitioning from waterfall to agile. Pseudo-agile projects are described as those that claim to use agile but lack key elements like automation, continuous integration, or involvement of testers throughout the process.
The document provides an overview of agile scrum testing methodology. It describes agile testing as testing practices that follow the agile manifesto and treat development as the customer of testing. It then outlines the key aspects of scrum testing including product backlogs, sprints, daily standup meetings, sprint planning and retrospectives. It also discusses the proposed scrum testing process of identifying test scenarios, writing test cases per sprint, delayed execution, and inclusion of defects in the product backlog.
Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.
Cypress is an end-to-end testing framework that focuses on doing testing well through features like time travel debugging, real-time reloads, and automatic waiting. It works on any frontend framework and tests are written in JavaScript alone. Cypress provides an all-in-one solution for developers and QA engineers to set up testing, write Cucumber tests, run and debug tests from a dashboard or command line, and generate reports including screenshots, videos, and JUnit files.
Agile Testing: A pragmatic overview and new entry in Intelliware’s Agile Methodology Series.
What you’ll learn in this presentation:
Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment.
The presentation covers:
- Why do we use Agile testing?
- What Agile testing isn’t
- What Agile testing is: unit testing and test-driven development (TDD)
- High-level properties of good tests
- Testing in different languages
- Test suites and code coverage
- Using mock objects to help isolate units
- Beyond unit testing
Agile testing principles and practices - Anil KaradeIndicThreads
Traditional test processes are not adaptive to extensive changes in software. Agile process emphasizes on ability to adapt to changing business needs, customer collaboration, integrated teams and frequent delivery of business values. Agile is an umbrella term that describes a variety of methods including XP and Scrum.
The talk will discuss pitfalls of the traditional testing process. Traditional testing process happens very late in the SDLC Where as Agile process focuses on test-first approach. The talk will explain benefits of going agile. Principles and practices of agile process will be discussed and agile methodologies Scrum and Extreme Programming will be discussed in detail. Purpose of Scrum, its effectiveness, timings and managing the scrum will be discussed. Some of the practices for XP like Pair Programming, Test Driven Development will be discussed. The Talk will also cover the QA role in agile world. The talk will cover the implementation issues while shifting from traditional to agile process. Talk will also include an interactive game for illustration of concepts.
Introducing QA Into an Agile EnvironmentJoseph Beale
This document discusses introducing quality assurance (QA) processes into an agile development environment. It describes some common challenges that can arise when development and testing are not well integrated, such as business stakeholders finding bugs late in the process. The author advocates for making QA practices and results visible and incorporating QA personnel into agile ceremonies like planning and demos. With collaboration, commitment to quality, and clear communication, the QA team was able to gain trust and find bugs earlier. Their approach evolved to take on more types of testing, and they worked with business to define different testing levels and work testing around releases.
This document provides an overview of agile testing. It discusses what agile testing is, common agile testing strategies and stages, principles of agile testing, advantages such as reduced time and money and regular feedback, challenges like compressed testing cycles and minimal time for planning, and concludes that communication between teams is key to agile testing success. The agile testing life cycle involves four stages: iteration 0 for initial setup, construction iterations for ongoing testing, release for deployment, and production for maintenance. Principles include testing moving the project forward, testing as a continuous activity, everyone on the team participating in testing, and reducing feedback loops.
The document discusses the "test pyramid" concept for balancing test suites from unit to end-to-end tests. It provides examples of different types of tests including unit tests, integration tests, UI/end-to-end tests. It also discusses challenges with different types of tests and strategies for addressing those challenges including dependency injection, mocks, and tools like Cucumber, Robolectric, and Pacto. The document seeks feedback on testing approaches and provides additional resources on testing best practices.
Cypress is a testing tool that allows for fast, easy, and reliable testing of anything that runs in a browser. It differs from other tools in that it does not use Selenium, focuses on end-to-end testing, works on any front-end framework, uses only JavaScript for tests, and runs much faster than other options. Cypress tests the application as a real user would and allows debugging of test flows. It also supports plugins, common commands and assertions, and has a similar syntax to unit testing frameworks.
At AWS re:Invent, we have launched support for blue/green deployments for services hosted using AWS Fargate and Amazon Elastic Container Service (Amazon ECS). Blue/green deployments help you minimize downtime during application updates. They allow you to launch a new version of your application alongside the old version and test the new version before you reroute traffic to it. You can also monitor the deployment process and, if there is an issue, quickly roll back.
In this workshop, you will create a new service in AWS Fargate that uses AWS CodeDeploy to manage the deployments, testing, and traffic cutover for you.
Agile Testing: The Role Of The Agile TesterDeclan Whelan
This presentation provides an overview of the role of testers on agile teams.
In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value.
Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.
Test Automation Frameworks: Assumptions, Concepts & ToolsAmit Rawat
The document discusses factors to consider when selecting a test automation framework. It describes how there are many options for frameworks available and outlines important criteria to evaluate, such as flexibility, ability to support different applications and interfaces, tool and language independence, parallel execution, and design patterns. The presentation provides examples of different types of frameworks and discusses strategies for building frameworks that can scale and evolve with changing needs.
Organisations turn to Agile and DevOps to improve customer experience by maximising the speed of delivery without sacrificing quality. As the champions of quality, testers achieve this goal through continuous testing. Test Automation plays a major role in continuous testing; it is the backbone of the continuous test process. To achieve continuous testing, automation must be applied at every stage of the development process. Developing a smart automation strategy and using the right tools is critical in achieving continuous testing since test scripts must be scalable and easy to maintain.
From http://wiki.directi.com/x/AgAa - This is a 24 slide internal presentation covering virtues of Automated Testing vs Manual Testing. Inkeeping with our agile adoption this presentation covers various advantages (11 to be specific) obtained in using TDD and Automated Testing as opposed to Manual Testing
Cypress vs Selenium WebDriver: Better, Or Just Different? -- by Gil TayarApplitools
** Full webinar recording: https://youtu.be/D7vxFuwnUio **
Watch Sr. Architect Gil Tayar's special hands-on session, where he explains & demonstrates how Selenium and Cypress differ.
The session covers the following topics:
* How and why do frontend developers write tests
*Selenium architecture
*Cypress architecture
*Live Demo of Cypress - including how to write a Cypress test, and how it’s used
*How Cypress deals with flakiness
*Cypress and backdoors to development
*Visual Testing using Cypress
This is a presentation given at the Hangzhou Scrum Forum 2009, sponsored by Perficient, China. The topic is how to incorporate automated functional testing into an agile project, and also some best practices, tips, and warnings.
www.perficient.com
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.
Keynote: Testing and Quality in the Scaled Agile Framework for Lean Enterpris...Derk-Jan de Grood
This document summarizes a keynote presentation on testing and quality in the Scaled Agile Framework (SAFe) given by Mette Bruhn-Pedersen and Derk-Jan de Grood. It discusses how SAFe addresses testing and quality, but that more guidance could be provided, especially around roles. It also provides suggestions for defining a quality strategy and embedding quality practices at each level of the framework, from the team to portfolio levels. The presentation emphasizes building quality in from the start and establishing a chief quality officer role.
Developing a test automation strategy by Brian BayerQA or the Highway
The document discusses developing a test automation strategy and considerations for regression testing, automation, and frameworks. It addresses why regression testing is important, factors for the automation strategy like business needs and ROI, and frameworks to consider like Cucumber, Robot Framework, and Spock. The strategy determines test maintenance and fits within the organization, development process, and technology stacks.
A confused tester in agile world finalversionAshish Kumar
This document discusses challenges faced by testers in agile environments. It begins with a story of a confused tester and presents several case studies of different organizations' approaches to testing in agile projects. It identifies common challenges such as changing requirements, lack of information, testing pace, and skills. A survey found that test automation, risk tracking, and cross-functional teams are commonly implemented agile practices. The document concludes with principles of testing being a continuous responsibility of the whole team.
Lesley Wallace presents on challenges with testing within a Scrum sprint and provides solutions. She asks the audience questions about their testing practices. Wallace explains that everyone on the team is responsible for quality and testing. To test within a sprint, stories must have decreased scope and testing must only focus on the story's scope. If more time is needed for regression testing, a "hardening sprint" can be added before release. Automation helps with testing and there are tools for all budgets.
Quality Assurance: What is it and what are the Business Benefits?Sparkhound Inc.
This is a Beginner/Intermediate -evel presentation. Sparky Lyle Hutson discusses some of the basics about what QA is capable of - both for waterfall and agile methodology. He discusses building a test matrix and its effectiveness with multiple checkpoints throughout a given testing session, as well as simple QA tricks.
The document discusses quality assurance and the role of quality analysts. It defines quality assurance as ensuring an expected level of quality throughout the development lifecycle. Quality analysts, or QAs, test applications to find issues early and ensure minimal risks. The document outlines when QAs become involved in waterfall and agile development methods, and highlights some benefits of investing in quality assurance like mitigating risks and catching bugs early.
The document discusses quality assurance and the role of quality analysts. It defines quality assurance as ensuring an expected level of quality throughout the development lifecycle. Quality analysts, or QAs, test applications to find issues early and ensure minimal risks. The document outlines when QAs become involved in waterfall and agile development methods, and highlights some benefits of investing in quality assurance like mitigating risks and catching bugs early.
SOASTA Webinar: Process Compression For Mobile App Dev 120612SOASTA
The webinar discusses continuous integration and automation for mobile development and testing. It presents tools from Atlassian, Zephyr, and SOASTA that can help automate the mobile development and testing process. Continuous integration with Bamboo can help developers integrate code changes more frequently and fail builds faster to catch bugs earlier. Zephyr provides test management to centralize test assets and provide visibility. SOASTA offers tools for test automation, real user monitoring, and performance/load testing to help achieve test completion with quality. Together these tools can help speed up the mobile development process through continuous integration, test automation, and visibility into the testing process.
This document discusses the "You Build It, You Run It" (YBYR) approach where developers are responsible for the full software release cycle from defining requirements to monitoring in production. The approach aims to speed up feature delivery through faster recovery from failures and more frequent releases. While it provides benefits like fewer production failures, adopting YBYR requires cultural change and depends on context, with no single solution. Frameworks and coaching are important to implement the approach successfully over time without making things worse initially.
The document discusses various "mini-waterfalls" that can emerge in Scrum teams through defined roles like analysts, developers, and testers working sequentially rather than collaboratively. Some examples provided include analysts completing work before passing it to developers or testing only occurring at the end after development is finished. This siloed work can reduce understanding, flexibility, speed, and quality. The document suggests empowering cross-functional teams and automating work to avoid these anti-patterns. It prompts readers to examine their own teams for similar issues and ways to continuously improve.
The document discusses issues that can arise from siloed roles in Scrum teams, such as developers, testers, and Scrum Masters acting as separate functions. This leads to reduced understanding between roles, bottlenecks when resources are unavailable, and an overall lack of team accountability. The document suggests that defining roles rigidly can cement separations and inhibit collaboration, flexibility, and process improvement. It argues teams should avoid "mini-waterfalls" between roles and instead strive for full cross-functionality, shared understanding of requirements, collective responsibility, and empowerment of self-organizing teams.
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
Agile Transformation: People, Process and Tools to Make Your Transformation S...QASymphony
Many companies are currently going through Agile Transformation or thinking about making the transition to agile. While moving to agile can create great opportunity for organizations, the journey to get there can be highly challenging. If you don’t have the right people, process and tools in place, the true benefits of agile may not be recognized. In this webinar, Andrew Stickland, Head of Client Services, for Clearvision and Kevin Dunne, VP of Business Development and Strategy for QASymphony will discuss the best practices for making the agile transformation. In this webinar, we will try to answer the following questions:
- Who are the people I need in place?
- What are the core processes that I need to change?
- What tools do I need?
View the On-Demand webinar here: http://pi.qasymphony.com/agile-transformation-best-practices-webinar-lp060?utm_source=slideshare&utm_medium=slideshare&utm_campaign=Agile%20Transformation%20Webinar
This document discusses various iterative software development models, including the spiral model, win-win spiral model, and cleanroom methodology. The spiral model is risk-driven and involves iterating through phases of planning, risk assessment, engineering, and evaluation. The win-win spiral model seeks to reconcile stakeholder objectives through negotiation. Cleanroom methodology emphasizes technical reviews, incremental development, and testing to reduce defects. Alternative models like hacking are also discussed for low-risk or disposable projects. Overall, the iterative models attempt to address limitations of the traditional waterfall model by incorporating feedback loops, prototyping, and incremental delivery.
What to Do—Develop Your Own Automation or Use Crowdsourced Testing?TechWell
Modern software products tend to have a rich UI that supports many user workflows, all of which need to be covered in testing. Agile organizations quickly discover that manual end-to-end testing neither supports their velocity nor provides respectable regression coverage. A common progression is to move from fully manual testing to record/replay, then to Selenium IDE style tests, then to automation based on Selenium WebDriver, perhaps with a BDD overlay. Daria Mehra has practiced this approach and shares her experience. She compares the Selenium style of automation to an alternative—crowdsourced test execution— which provides all the benefits of test automation, including continuous integration. This approach allows non-coders to express test cases in natural language, avoids the dependency on UI implementation, adds a “human eye” advantage, and provides the ability to massively parallelize tests for fast execution. Learn the pros and cons of end-to-end, UI-based test automation via Selenium compared to crowdsourcing. Find out how you can assess the suitability of these testing approaches for your needs.
SOASTA Webinar: Process Compression For Mobile App Dev 120612SOASTA
1. The webinar discussed continuous integration and automation practices for mobile development and testing. It focused on how to automate testing to keep up with the pace and scale of mobile development.
2. Speakers from Atlassian, Zephyr, and SOASTA discussed how tools like Bamboo and CloudTest can help automate builds, testing, and monitoring to fail faster and achieve continuous delivery of mobile apps.
3. The webinar emphasized that manual testing cannot keep up with the pace of mobile development and highlighted principles of continuous integration like building and testing code frequently and leveraging automation.
How to manoeuvre as test/QA responsible in agile teams to get the "right" pro...SQALab
Knud Hangaard presented on agile development at Saxo Bank and how testers can maneuver to achieve the right quality. He discussed how Saxo Bank uses Scrum, Kanban and Prince2 methodologies in development. Testers focus on risk-based testing and time-boxed cycles. Key lessons included having clear and flexible processes, effective communication, and adopting a risk-focused mindset to test the highest priority areas first.
The document discusses various aspects of automating software testing. It suggests automating the detection of flaky tests, determining the severity of test failures, converting tests to more isolated unit tests, and using usage data to determine what to test next. It emphasizes that while automation can improve testing efficiency, human oversight is still needed, and code reviews serve as the link between automated and manual processes.
Comprehensive Validation with Laravel 4Kirk Bushell
Taking basic validation rules to a more manageable, readable state by implementing architectural solutions that make our validation requirements beautiful.
[DevSecOps Live] DevSecOps: Challenges and OpportunitiesMohammed A. Imran
In this Practical DevSecOps's DevSecOps Live online meetup, you’ll learn DevSecOps Challenges and Opportunities.
Join Mohan Yelnadu, head of application security at Prudential Insurance on his DevSecOps Journey.
He will cover DevSecOps challenges he has faced and how he converted them into opportunities.
He will cover the following as part of the session.
DevSecOps Challenges.
DevSecOps Opportunities.
Converting Challenges into Opportunities.
Quick wins and lessons learned.
… and more useful takeaways!
'Stakeholder Engagement Shortcuts': Ilan Goldstein @ Colombo Agile Conference...ColomboCampsCommunity
Change is difficult, and the reality is that in many organisations, an agile adoption means considerable change. Kickstarting a new initiative such as Scrum requires support from your senior stakeholders. This presentation outlines some powerful shortcuts to help engage with your stakeholder community to ensure that Scrum is given the best opportunity to flourish!
Similar to So we're going no-QA - how do we get the devs to do enough testing? (20)
May Marketo Masterclass, London MUG May 22 2024.pdfAdele Miller
Can't make Adobe Summit in Vegas? No sweat because the EMEA Marketo Engage Champions are coming to London to share their Summit sessions, insights and more!
This is a MUG with a twist you don't want to miss.
Transform Your Communication with Cloud-Based IVR SolutionsTheSMSPoint
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
Graspan: A Big Data System for Big Code AnalysisAftab Hussain
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j
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.
E-commerce Development Services- Hornet DynamicsHornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
A Study of Variable-Role-based Feature Enrichment in Neural Models of CodeAftab Hussain
Understanding variable roles in code has been found to be helpful by students
in learning programming -- could variable roles help deep neural models in
performing coding tasks? We do an exploratory study.
- These are slides of the talk given at InteNSE'23: The 1st International Workshop on Interpretability and Robustness in Neural Software Engineering, co-located with the 45th International Conference on Software Engineering, ICSE 2023, Melbourne Australia
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
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.
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.
Hand Rolled Applicative User ValidationCode KataPhilip Schwarz
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.
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.
Revolutionizing Visual Effects Mastering AI Face Swaps.pdfUndress Baby
The quest for the best AI face swap solution is marked by an amalgamation of technological prowess and artistic finesse, where cutting-edge algorithms seamlessly replace faces in images or videos with striking realism. Leveraging advanced deep learning techniques, the best AI face swap tools meticulously analyze facial features, lighting conditions, and expressions to execute flawless transformations, ensuring natural-looking results that blur the line between reality and illusion, captivating users with their ingenuity and sophistication.
Web:- https://undressbaby.com/
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/
3. AGILE CAMBRIDGE 2016 - “DON’T GO
CHASING WATERFALLS”
3
• Scrum has only 3 roles, PO, SM and developers
• No BA, no QA, no DBA, no other (dedicated) roles – only “T-shaped
people”
• These other roles are common in scrum teams, particularly (manual) QA
• They cause a waterfall…
5. WHY IS THIS SO BAD? (JUST BECAUSE IT
ISN’T “SCRUM”)
5
Silos
Efficiency
Over-the-wall Thinking
Undue power
of sign-off
Unnecessary delays
(while bugs are triaged)
Stifles Innovation
Just not agile!
Risk
Blocks improvement
Not failing early
6. Is this the real resource
requirement, every
hour, of every day of
every sprint?
33%
17%
50%
EFFICIENCY?
6
• Is this really how the work is split
every hour of every day of every
sprint?
7. AGILE CAMBRIDGE 2016 - “DON’T GO
CHASING WATERFALLS”
7
• Do certain people really have a “testing gene” that makes them better at
testing than developers?
• If testers find a bug that customers will never find, do we care? Particularly if
that delays release and stops us getting early feedback?
• Are a couple of QAs going to find (actual, customer impacting) bugs as
quickly as (say) hundreds on a beta program?
• Are dedicated testers going to be able to understand the complexities of the
codebase, and the best way to use testing frameworks?
8. AGILE CAMBRIDGE 2016 - “DON’T GO
CHASING WATERFALLS”
8
• Spotify DIBBs (Data-Insight-Belief-Bet) philosophy -
https://www.infoq.com/news/2016/07/spotify-good-at-failing
speed of iteration
beats
quality of iteration
9. AGILE CAMBRIDGE 2016 - “DON’T GO
CHASING WATERFALLS”
9
• Case study based on 3 teams in Sky
• Not having dedicated QAs increased speed of delivery and improved
quality (fewer bugs/rollbacks, improved customer reviews)
• Bugs spotted earlier, so faster fail
11. HOW DO WE GET THE DEVS TO DO
ENOUGH TESTING?
11
12. WHAT IS “ENOUGH” TESTING? WHAT ARE WE
TRYING TO ACHIEVE?
12
Deliver the
most value
Stability
“Zero” (acceptable
level of) defects
Quickest possible
feedback Speed of delivery
and rollback
Maintainability
Quality Security
13. WHAT IS “ENOUGH” TESTING? HOW DO WE
ACHIEVE IT?
13
• Many other strategies to improve quality apart from testing…
• Code reviews, walkthroughs
• Design patterns, include proved code
• Pair programming
• Coding standards, linting, etc
• Beta groups
• A/B and multivariate testing
21. RECRUITING TO ROLES
21
• Who would test your app the most realistically?
a) Something with expert knowledge of app testing theory?
b) Someone with initimate knowledge of your products and how the app is
used in the real world?
25. 25
• Aside: An example of where manual testing is damaging -
https://www.linkedin.com/pulse/manual-testing-always-necessary-fact-
sometimes-bit-dangerous-wells
Confi
g
Objec
t
Endpoint 1
Endpoint 2
30. 30
• Team of 8 with 1 tester
• Replace tester with dev
• We get nearly a whole extra person
• We only have to do 1/8 of the testing
each
DO THE MATHS
33. THINGS TO AVOID
33
• Rotating the QA role
• Allowing developers to refuse to test
• The “dev in test” role
• The phrase “dev-complete”
• “We’ll release, then come back and write tests later…”
34. IF THE PO IS ALSO CAUSING A WATERFALL,
WHY NOT GET RID OF THAT ROLE AS WELL?
34
PO
Dev
QA
35. IF THE PO IS ALSO CAUSING A WATERFALL,
WHY NOT GET RID OF THAT ROLE AS WELL?
35
PO
Dev
Deliver
Team
Note: This doesn’t just apply to Scrum! Scrum and agile are *not* the same thing!
So I gave this talk, and got mobbed by angry testers. However, of more interest to me was the question on the next slide, which was asked by Scrum Masters, Pos, etc. etc.
From the original scrum guide – in terms of breakfast, chickens are involved, pigs are committed. Make your teams into pigs (as it were )
You wouldn’t let someone else pack your parachute! Same with software – don’t rely on other teams (integration, e2e, etc.) to do your testing – make it perfect before it leaves the team…
Once you have headcount for “a tester” or “a QA” or any other role such as “front-end developer”, that defines salary ranges, job specs, etc. etc. Only recruit T-shaped people, and don’t define roles apart from “developer” or “engineer”
The case given was software that flies planes, I do *not* actually want humans testing that!
Make it competitive between team members, but keep it light-hearted!
The PO should be embedded in the team and work in collaboration with the team. The team as a whole make the decisions…