Main Talk v1.1
•Download as PPTX, PDF•
1 like•297 views
Pokémon GO faced several quality issues after its initial release such as app freezing, server overload causing scaling problems, inaccurate GPS, and device fragmentation affecting the ability to catch Pokémon. The document discusses lessons learned around testing and quality from these issues, including the need for a balanced testing approach with different types of testing like functionality, performance, compatibility, and usability testing. It also emphasizes that quality is multifaceted and requires continuously adding and improving features while focusing on the core idea.
Report
Share
Report
Share
Recommended
Using real customer data to drive Testing
This document discusses using real customer data and artificial intelligence to improve software testing. Traditional testing is time-consuming and misses defects because test cases are manually defined and do not adapt. A new approach called Digital Experience Optimization uses AI to automatically generate test cases based on real user journeys and behaviors. This continuous and adaptive testing approach finds more issues while requiring less effort over time compared to traditional structured testing.
Morph your mindset for Continuous Delivery, Agile Roots 2014
This document outlines an agenda and content for a workshop on continuous integration, continuous delivery, and overcoming obstacles. The workshop includes presentations on key concepts, exercises for participants to collaborate in different roles and provide feedback, and discussions on challenges and experiments to try back at work. The goal is to help participants shift their mindset and learn techniques through interactive exercises to enable continuous delivery of software.
Andrew rusling 21 experiments to increase velocity
The document discusses theories and principles for increasing productivity and throughput (velocity). It presents queuing theory and the theory of constraints, explaining how to reduce utilization, batch size, and item size to improve flow based on queuing theory. It then provides 21 experiments teams can try based on these theories, such as reducing work in progress limits, splitting up work into smaller batches and items, and improving the identified constraint area.
AutomationTesting_HOW_
Automation testing tools can speed up test execution, improve test coverage and quality. Capture-based tools use image capturing and absolute positioning to emulate user actions through simple scripts, while DOM-based tools use object positioning and scripting languages to flexibly create large test sets. Both approaches have tradeoffs around ease of use, maintainability and testability that must be considered for a given project.
How to perform usability testing to a car?
This document discusses how to plan and conduct usability testing for a product. It recommends defining performance criteria for tasks and using usability testing from early concepts through final release to get hands-on experience. Usability testing provides feedback, guidance, and clear recommendations to improve the product and offers a high return on investment.
Android application development part2
Android software development is the process by which new applications are created for devices running the Android operating system. Google states that, "Android apps can be written using Kotlin, Java, and C++ languages" using the Android software development kit, while using other languages is also possible.
Continuous delivery 101
Continuous delivery is an approach to software development where code changes are automatically tested, built, and prepared for deployment to production. It aims to ensure software is always in a releasable state. Automation, testing, pull requests, feature flags, and monitoring are key enablers to achieving continuous delivery. Continuous delivery allows for more frequent releases and improves productivity by getting feedback earlier.
Hiep le - xp should be dead! here is why.
This slide was presented as at Global Scrum Gathering 2017. Extreme Programing (XP) is 20 years old. It discuss psychological and technological reasons why Extreme Programming should be considered "dead" and should become a normal regular software development approach.
Recommended
Using real customer data to drive Testing
This document discusses using real customer data and artificial intelligence to improve software testing. Traditional testing is time-consuming and misses defects because test cases are manually defined and do not adapt. A new approach called Digital Experience Optimization uses AI to automatically generate test cases based on real user journeys and behaviors. This continuous and adaptive testing approach finds more issues while requiring less effort over time compared to traditional structured testing.
Morph your mindset for Continuous Delivery, Agile Roots 2014
This document outlines an agenda and content for a workshop on continuous integration, continuous delivery, and overcoming obstacles. The workshop includes presentations on key concepts, exercises for participants to collaborate in different roles and provide feedback, and discussions on challenges and experiments to try back at work. The goal is to help participants shift their mindset and learn techniques through interactive exercises to enable continuous delivery of software.
Andrew rusling 21 experiments to increase velocity
The document discusses theories and principles for increasing productivity and throughput (velocity). It presents queuing theory and the theory of constraints, explaining how to reduce utilization, batch size, and item size to improve flow based on queuing theory. It then provides 21 experiments teams can try based on these theories, such as reducing work in progress limits, splitting up work into smaller batches and items, and improving the identified constraint area.
AutomationTesting_HOW_
Automation testing tools can speed up test execution, improve test coverage and quality. Capture-based tools use image capturing and absolute positioning to emulate user actions through simple scripts, while DOM-based tools use object positioning and scripting languages to flexibly create large test sets. Both approaches have tradeoffs around ease of use, maintainability and testability that must be considered for a given project.
How to perform usability testing to a car?
This document discusses how to plan and conduct usability testing for a product. It recommends defining performance criteria for tasks and using usability testing from early concepts through final release to get hands-on experience. Usability testing provides feedback, guidance, and clear recommendations to improve the product and offers a high return on investment.
Android application development part2
Android software development is the process by which new applications are created for devices running the Android operating system. Google states that, "Android apps can be written using Kotlin, Java, and C++ languages" using the Android software development kit, while using other languages is also possible.
Continuous delivery 101
Continuous delivery is an approach to software development where code changes are automatically tested, built, and prepared for deployment to production. It aims to ensure software is always in a releasable state. Automation, testing, pull requests, feature flags, and monitoring are key enablers to achieving continuous delivery. Continuous delivery allows for more frequent releases and improves productivity by getting feedback earlier.
Hiep le - xp should be dead! here is why.
This slide was presented as at Global Scrum Gathering 2017. Extreme Programing (XP) is 20 years old. It discuss psychological and technological reasons why Extreme Programming should be considered "dead" and should become a normal regular software development approach.
[Webinar] Introducing Feature Management
Launching a new feature is a risky proposition. Even the most well designed and researched features can initially tank your applications' performance and business metrics. Rolling back a poor performing feature can be time consuming and costly. However, it doesn't have to be. Implementing feature management and experimentation into your development lifecycle can help your team reduce risk when launching new features. Feature management isn't just for developers. Product managers can attend this webinar to discover how implementing feature management and experimentation can help prove impact across the product cycle.
Attend this webinar to learn:
- Best practices for launching products with velocity and quality using feature management
- Guidelines for limiting your blast radius when rolling out new or redesigned features
- How using experimentation and feature management in tandem enable you to iterate faster and ship better performing products
Scrum Plus Extreme Programming (XP) for Hyper Productivity
If you want to go fast with Scrum, then your best option is to compliment it with Extreme Programming (XP). Inside is an activity that you can run your team and management through to prove and sell the concept.
Kanban and Iterationless Working
This document discusses iterationless working using Kanban principles from Lean. It describes how iterations can introduce waste like overproduction, waiting, and defects. Kanban advocates for continuous flow by pulling work through stages like implementation, testing, acceptance and delivery. The first attempt at iterationless working revealed issues around unclear work items, lack of deployment after acceptance, an unwieldy backlog and minimal estimation. After a retrospective, improvements were made for the second iterationless approach.
Advanced Cross-Browser Visual Testing with Applitools Eyes and HP LeanFT
Slides presented at the joint Applitools / HP webinar on July 16th, 2015
http://testautomation.applitools.com/post/123025212447/webinar-advanced-cross-browser-testing-with
When & How to Successfully use Test Automation for Mobile Applications
A free webinar produced by the Technology Association of Oregon's Quality Assurance Forum Group. Presented by Trent Peterson, CEO and Co-Founder of Portland-based AppThwack, providing fast automated mobile device testing services for Android, iPhone, iPad, and mobile web apps. The recording to the webinar can be accessed here: http://youtu.be/r9Vm6ssSEU8
Extreme Programming Deployed
This document discusses the principles and practices of Extreme Programming (XP), an agile software development process. It describes XP as an intense, test-centric programming process focused on projects with high rates of change. Key practices include pair programming, test-driven development, planning with user stories and tasks, doing the simplest thing that could work, and refactoring code aggressively. Problems may include short-term "hill-climbing" solutions and risks of fundamental design errors. The document provides additional resources on XP and notes that the day's session will involve practicing XP techniques through pair programming.
2013 09-11 java zone - extreme programming live
The document summarizes an "Extreme Programming" talk given by Johannes Brodwall. The talk demonstrates test-driven development and pair programming. It discusses the benefits of these practices, such as producing higher quality code through simplicity, communication, and feedback. It encourages programmers to practice deliberately, both at work and at home, in order to continuously improve. The conclusion emphasizes freeing the mind and practicing programming as an art.
Adam carmi
This document discusses automating visual software testing. It begins by explaining that visual testing is used to verify a graphical user interface appears correctly. It then discusses why visual testing should be automated, such as because the test matrix is too large to cover manually across different browsers, devices, resolutions, etc. It also notes that mobile app quality is critical so testing needs to be thorough. The document outlines how visual testing works by taking screenshots, comparing them to baselines, and reporting differences. It provides examples of tools that can be used for visual testing and discusses how tests can be integrated into development pipelines from the code level through production.
Waterfalls for Agile in a bag
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.
Waterfalls for agile cambridge
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.
Quick intro to scrum agile
The document discusses Agile and Scrum frameworks for software development. It defines key aspects of Scrum including roles like Product Owner and Scrum Master, ceremonies like sprint planning and daily standups, and artifacts like product and sprint backlogs. Scrum was designed to address uncertainties in specifications and changing requirements by having self-organizing cross-functional teams work in short sprints to deliver working software.
Cat v12
CAT TestRunner is test preparation software that provides over 6,000 practice questions in verbal, quantitative, and analytical reasoning to help students prepare for the CAT exam. It offers unlimited model tests that can be taken subject-wise, chapter-wise, or topic-wise. After each test, it displays the user's strong and weak areas and allows reviewing questions by type. The software simulates the computer-based exam experience and provides detailed reports on performance to help users identify and focus on weak areas for improvement over time. It is priced at Rs. 499 and works on PCs meeting minimum system requirements.
Ash_Winter-DEWT7_V1
This document discusses the author's experience consulting with various organizations to improve their testing capabilities. The author found that reviewing testing independently did not address root causes and that organizations often wanted quick fixes rather than systemic changes. The author eventually realized they needed to take a more holistic systems-thinking approach and focus on root causes rather than superficial solutions. They decided to focus more on systems thinking and become nomadic in their work.
Ash_Winter-Forgotten-ility_V1
The document discusses various topics related to software testing including testability, logging, environments, and feedback. It provides tips such as getting to know operations pain points, logging what matters without bloat, understanding past code intent, and focusing more on test flow and feedback rather than number of environments or testability. The document ends with inviting questions.
Ash Winter - What is testing?
This document discusses different perspectives on what testing is and provides the author's axioms about testing. The author believes that testing is a team-based activity where they help enable testing rather than doing most of the testing themselves. They view testing as a human, intellectual activity involving thinking, learning, sharing ideas. Complete testing is seen as impossible due to logical limitations and infinite possibilities, so balance and variation are important. Testing is considered a performance where the value is in applying it, not just thinking about it. Tools can assist testing but not replace it. Context is also important, as what works in one situation may not work in another.
Ash_Winter_Tested_to_Death
The document discusses how too much testing can trap a team and product in a "death spiral". It describes a scenario where a team assembled to build a product but their testing strategy became ineffective and led to slower development and frustrated teams. The document then provides tips on how to avoid this, such as making sure unit tests actually test units, writing tests first, keeping dependencies loose, and evolving one's testing strategy so that testing serves the team rather than the other way around. It emphasizes that the goal is learning rather than failure.
Ash_Winter_Testing_Mobile_Apocalypse_Online
The document discusses testing in a mobile context. It begins with a poll about mobile device and testing experience. It then tells a story about realizing the need to test mobile applications. Mobile testing was behind the curve, with early experts, dodgy tools, and outsourcing common issues. However, mobile presents an opportunity for testing as the same principles of testing still apply. The document lists several "axioms" or truths of testing that still hold for mobile, such as testing being a human activity and oracles being fallible. It argues that complete testing is impossible given device fragmentation, but test cases do not equal testing. Testing mobile is a performance in itself. The document concludes that bugs cost businesses and mobile is probably the
Bullseye or The Testing Wheel
One of my recent endeavours has been to create a "career model" for the testers within my organisation. I sat in my office at home and designed "the testing wheel". I wanted it to be simple, inclusive and offer questions but few answers.
Careers are long and winding. My own career has not been a linear progression, so building a linear model seemed wrong to me. But, this brought me into conflict with the ideas of others.
My experience report will show the highs and lows of this model after introducing it into the wild. People still tried to measure and rank with it, got mad people got when I refused to answer the questions it posed. Finally how it spread and entered battle with wider organisations career models.
Turbo Mindmapping Your App
This document provides instructions for collaboratively mindmapping an application using the online tool mindmup.com. Participants are instructed to get into groups of three, with one person creating a real-time collaborative mindmap session for their application and inviting the other two participants. They are then instructed to collaboratively map out the functions, forms, fields, views, integrations, and other aspects of the application to document its functionality and coverage for testing purposes.
NWEWT_Slides_Ash_Winter_04_2016
This document discusses regression testing for a project to stabilize and upgrade the underlying technology of a system while maintaining normal service. It raises questions about how to test that nothing has changed when everything is changing, and whether changes to responsiveness and capacity would still be noticeable to customers. The regression testing involved risk modeling sessions with stakeholders to understand the system, exploring the system to determine what to test, and testing from the user interface down to the unit level. The results showed some issues were found and fixed, while other changes like increased speed and capacity were noticed by customers, raising questions about how to prevent customers noticing any differences after changes. It concludes that taking broad statements literally can be problematic, and that preventing all changes from being noticed may be
Teams and monoliths - Matthew Skelton - Velocity EU 2016
How to break apart a monolithic system safely without destroying your team - talk at Velocity Eu Amsterdam on 7 Nov 2016
You'll learn some team-first heuristics to use when decomposing large or monolithic software into smaller pieces.
http://conferences.oreilly.com/velocity/devops-web-performance-eu/public/schedule/detail/52879
QA For Indies / Tiberiu Cristea (tinyBuild)
Are you an aspiring indie developer? If you're looking forward to creating a smash indie title, you have to seriously consider QA. As an essential part of the game development lifecycle, QA is something you simply cannot do without.
Follow me as I’ll explain what proper QA can do for your game, and your organization. I’ll describe processes, good practices, testing tools, console requirements, types and techniques of testing which you might decide to employ.
More Related Content
What's hot
[Webinar] Introducing Feature Management
Launching a new feature is a risky proposition. Even the most well designed and researched features can initially tank your applications' performance and business metrics. Rolling back a poor performing feature can be time consuming and costly. However, it doesn't have to be. Implementing feature management and experimentation into your development lifecycle can help your team reduce risk when launching new features. Feature management isn't just for developers. Product managers can attend this webinar to discover how implementing feature management and experimentation can help prove impact across the product cycle.
Attend this webinar to learn:
- Best practices for launching products with velocity and quality using feature management
- Guidelines for limiting your blast radius when rolling out new or redesigned features
- How using experimentation and feature management in tandem enable you to iterate faster and ship better performing products
Scrum Plus Extreme Programming (XP) for Hyper Productivity
If you want to go fast with Scrum, then your best option is to compliment it with Extreme Programming (XP). Inside is an activity that you can run your team and management through to prove and sell the concept.
Kanban and Iterationless Working
This document discusses iterationless working using Kanban principles from Lean. It describes how iterations can introduce waste like overproduction, waiting, and defects. Kanban advocates for continuous flow by pulling work through stages like implementation, testing, acceptance and delivery. The first attempt at iterationless working revealed issues around unclear work items, lack of deployment after acceptance, an unwieldy backlog and minimal estimation. After a retrospective, improvements were made for the second iterationless approach.
Advanced Cross-Browser Visual Testing with Applitools Eyes and HP LeanFT
Slides presented at the joint Applitools / HP webinar on July 16th, 2015
http://testautomation.applitools.com/post/123025212447/webinar-advanced-cross-browser-testing-with
When & How to Successfully use Test Automation for Mobile Applications
A free webinar produced by the Technology Association of Oregon's Quality Assurance Forum Group. Presented by Trent Peterson, CEO and Co-Founder of Portland-based AppThwack, providing fast automated mobile device testing services for Android, iPhone, iPad, and mobile web apps. The recording to the webinar can be accessed here: http://youtu.be/r9Vm6ssSEU8
Extreme Programming Deployed
This document discusses the principles and practices of Extreme Programming (XP), an agile software development process. It describes XP as an intense, test-centric programming process focused on projects with high rates of change. Key practices include pair programming, test-driven development, planning with user stories and tasks, doing the simplest thing that could work, and refactoring code aggressively. Problems may include short-term "hill-climbing" solutions and risks of fundamental design errors. The document provides additional resources on XP and notes that the day's session will involve practicing XP techniques through pair programming.
2013 09-11 java zone - extreme programming live
The document summarizes an "Extreme Programming" talk given by Johannes Brodwall. The talk demonstrates test-driven development and pair programming. It discusses the benefits of these practices, such as producing higher quality code through simplicity, communication, and feedback. It encourages programmers to practice deliberately, both at work and at home, in order to continuously improve. The conclusion emphasizes freeing the mind and practicing programming as an art.
Adam carmi
This document discusses automating visual software testing. It begins by explaining that visual testing is used to verify a graphical user interface appears correctly. It then discusses why visual testing should be automated, such as because the test matrix is too large to cover manually across different browsers, devices, resolutions, etc. It also notes that mobile app quality is critical so testing needs to be thorough. The document outlines how visual testing works by taking screenshots, comparing them to baselines, and reporting differences. It provides examples of tools that can be used for visual testing and discusses how tests can be integrated into development pipelines from the code level through production.
Waterfalls for Agile in a bag
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.
Waterfalls for agile cambridge
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.
Quick intro to scrum agile
The document discusses Agile and Scrum frameworks for software development. It defines key aspects of Scrum including roles like Product Owner and Scrum Master, ceremonies like sprint planning and daily standups, and artifacts like product and sprint backlogs. Scrum was designed to address uncertainties in specifications and changing requirements by having self-organizing cross-functional teams work in short sprints to deliver working software.
Cat v12
CAT TestRunner is test preparation software that provides over 6,000 practice questions in verbal, quantitative, and analytical reasoning to help students prepare for the CAT exam. It offers unlimited model tests that can be taken subject-wise, chapter-wise, or topic-wise. After each test, it displays the user's strong and weak areas and allows reviewing questions by type. The software simulates the computer-based exam experience and provides detailed reports on performance to help users identify and focus on weak areas for improvement over time. It is priced at Rs. 499 and works on PCs meeting minimum system requirements.
What's hot (12)
Scrum Plus Extreme Programming (XP) for Hyper Productivity
Scrum Plus Extreme Programming (XP) for Hyper Productivity
Advanced Cross-Browser Visual Testing with Applitools Eyes and HP LeanFT
Advanced Cross-Browser Visual Testing with Applitools Eyes and HP LeanFT
When & How to Successfully use Test Automation for Mobile Applications
When & How to Successfully use Test Automation for Mobile Applications
Viewers also liked
Ash_Winter-DEWT7_V1
This document discusses the author's experience consulting with various organizations to improve their testing capabilities. The author found that reviewing testing independently did not address root causes and that organizations often wanted quick fixes rather than systemic changes. The author eventually realized they needed to take a more holistic systems-thinking approach and focus on root causes rather than superficial solutions. They decided to focus more on systems thinking and become nomadic in their work.
Ash_Winter-Forgotten-ility_V1
The document discusses various topics related to software testing including testability, logging, environments, and feedback. It provides tips such as getting to know operations pain points, logging what matters without bloat, understanding past code intent, and focusing more on test flow and feedback rather than number of environments or testability. The document ends with inviting questions.
Ash Winter - What is testing?
This document discusses different perspectives on what testing is and provides the author's axioms about testing. The author believes that testing is a team-based activity where they help enable testing rather than doing most of the testing themselves. They view testing as a human, intellectual activity involving thinking, learning, sharing ideas. Complete testing is seen as impossible due to logical limitations and infinite possibilities, so balance and variation are important. Testing is considered a performance where the value is in applying it, not just thinking about it. Tools can assist testing but not replace it. Context is also important, as what works in one situation may not work in another.
Ash_Winter_Tested_to_Death
The document discusses how too much testing can trap a team and product in a "death spiral". It describes a scenario where a team assembled to build a product but their testing strategy became ineffective and led to slower development and frustrated teams. The document then provides tips on how to avoid this, such as making sure unit tests actually test units, writing tests first, keeping dependencies loose, and evolving one's testing strategy so that testing serves the team rather than the other way around. It emphasizes that the goal is learning rather than failure.
Ash_Winter_Testing_Mobile_Apocalypse_Online
The document discusses testing in a mobile context. It begins with a poll about mobile device and testing experience. It then tells a story about realizing the need to test mobile applications. Mobile testing was behind the curve, with early experts, dodgy tools, and outsourcing common issues. However, mobile presents an opportunity for testing as the same principles of testing still apply. The document lists several "axioms" or truths of testing that still hold for mobile, such as testing being a human activity and oracles being fallible. It argues that complete testing is impossible given device fragmentation, but test cases do not equal testing. Testing mobile is a performance in itself. The document concludes that bugs cost businesses and mobile is probably the
Bullseye or The Testing Wheel
One of my recent endeavours has been to create a "career model" for the testers within my organisation. I sat in my office at home and designed "the testing wheel". I wanted it to be simple, inclusive and offer questions but few answers.
Careers are long and winding. My own career has not been a linear progression, so building a linear model seemed wrong to me. But, this brought me into conflict with the ideas of others.
My experience report will show the highs and lows of this model after introducing it into the wild. People still tried to measure and rank with it, got mad people got when I refused to answer the questions it posed. Finally how it spread and entered battle with wider organisations career models.
Turbo Mindmapping Your App
This document provides instructions for collaboratively mindmapping an application using the online tool mindmup.com. Participants are instructed to get into groups of three, with one person creating a real-time collaborative mindmap session for their application and inviting the other two participants. They are then instructed to collaboratively map out the functions, forms, fields, views, integrations, and other aspects of the application to document its functionality and coverage for testing purposes.
NWEWT_Slides_Ash_Winter_04_2016
This document discusses regression testing for a project to stabilize and upgrade the underlying technology of a system while maintaining normal service. It raises questions about how to test that nothing has changed when everything is changing, and whether changes to responsiveness and capacity would still be noticeable to customers. The regression testing involved risk modeling sessions with stakeholders to understand the system, exploring the system to determine what to test, and testing from the user interface down to the unit level. The results showed some issues were found and fixed, while other changes like increased speed and capacity were noticed by customers, raising questions about how to prevent customers noticing any differences after changes. It concludes that taking broad statements literally can be problematic, and that preventing all changes from being noticed may be
Teams and monoliths - Matthew Skelton - Velocity EU 2016
How to break apart a monolithic system safely without destroying your team - talk at Velocity Eu Amsterdam on 7 Nov 2016
You'll learn some team-first heuristics to use when decomposing large or monolithic software into smaller pieces.
http://conferences.oreilly.com/velocity/devops-web-performance-eu/public/schedule/detail/52879
Viewers also liked (9)
Teams and monoliths - Matthew Skelton - Velocity EU 2016
Teams and monoliths - Matthew Skelton - Velocity EU 2016
Similar to Main Talk v1.1
QA For Indies / Tiberiu Cristea (tinyBuild)
Are you an aspiring indie developer? If you're looking forward to creating a smash indie title, you have to seriously consider QA. As an essential part of the game development lifecycle, QA is something you simply cannot do without.
Follow me as I’ll explain what proper QA can do for your game, and your organization. I’ll describe processes, good practices, testing tools, console requirements, types and techniques of testing which you might decide to employ.
Bob Galen : Great sprint reviews
Mile High Agile 2016 conference is posting materials from our speakers so attendees can familiarize themselves and deepen their research and understanding.
First Speaker : Bob Galen
Getting By Without "QA"
Tilt does not currently employ any quality engineers. How can we deliver quality software? Over the last year the organization has gone from terrifying deploys (followed by
Software testing and quality assurance
Why use Specflow (Gherkin) and Selenium ?
Unit tests, functional tests, integration tests, acceptance tests ...
A Startup Story - Geekcamp Presentation
This document summarizes the development timeline and approach of Gameplan, a startup building a sports tournament platform. It describes key milestones from April to September including the first public demo, free preview launch, and beta launches. It then discusses the company's working philosophy of top-down development, just-in-time building, and feedback loops. Pair programming is used when possible. The document emphasizes common sense over buzzwords and having user traction, profits, and happiness over great code alone. It advocates testing assumptions through failure and success and provides tips on dry testing a product and not taking advice too literally.
Hacker News Meetup April 2014
How Songkick's technology team does continuous delivery and uses experiments to develop our products.
22-AnOverviewOfScrum.pptx
Scrum is an agile process that focuses on delivering the highest priority features in short iterations called sprints. During a sprint, a self-organizing team works on user stories from the product backlog and meets daily to track progress. At the end of a sprint, working software is demoed to stakeholders. Scrum uses roles like product owner, ScrumMaster, and team as well as artifacts like product backlog, sprint backlog, and burn down charts to help deliver value quickly.
How will I Survive a DevOps Transformation?
If you’ve shifted left and right so many times, I imagine it’s hard to remember where you started from? The direction of shift was always within a Test Managers gift, but wasn’t obvious. It’s time to shift towards testability.
Ash Winter, Principal Test Engineer at Sky Betting & Gaming covers the following:
⦁ examples of the benefits of an enhanced testability focus
⦁ how focusing on testability can keep Test Managers relevant in changing times
⦁ introduction of a holistic model of testability to expand thinking
⦁ brainstorming – how can test leaders contribute to a testability culture?
Ash said:
“I believe that testability and organisational success are linked. Testable systems are easier to support and maintain. Being able to observe and control systems is a unifying force across disciplines. Why would one not wish to focus on such benefits?"
TestBoss is an award winning invitation-only networking event for leaders in Test Management, hosted by IT recruitment specialist Corecom Consulting.
Android Developer Skills, Techniques, and Patterns
Ancestry is a large company that provides family history and DNA testing services. It has over 1 billion records in its databases and over 3 million subscribers. As an Android developer at Ancestry, a typical day involves collaborating with teammates to work on user stories, addressing bugs, learning new skills, and ensuring code quality. Developers focus on testing, code reviews, following best practices, and balancing individual and team work. The goal is to build high quality features while continuously improving skills.
Is Scrum the Best Choice for you?
This document discusses whether Scrum is the best choice for a company called YOYO. It introduces Scrum and its roles, artifacts, and events. For YOYO, the author suggests using Kanban instead of strictly following Scrum, as Kanban allows for transparency and continuous process improvement through inspection and adaptation, which aligns with Scrum theory. The author's overall suggestion is to think about your own context and continuously improve, and that Scrum may not always be the best choice.
Invite the tester to the party
This slide deck was used at the Global Scrum Gathering in Prague in 2015. The deck provides inspiration on:
* How to make the tester part of the Development Team
* How to eliminate the need for "Quality Control"
* Foster collaboration within the team.
Anotherpm an example of agile survival
This document summarizes an Agile consultant's experience helping a large company survive by implementing Agile practices. It describes some initial problems like long releases, outsourcing issues, and lack of responsibility. It then discusses how the company tried different Agile techniques over the year, such as fast lane releases, multi-product ownership, and having multiple product owners. While some experiments like the architect's sandbox caused issues, overall tweaking Scrum practices and focusing on interactions helped achieve good results in a challenging environment.
Team wide testing
This document discusses implementing team wide testing to improve quality and reduce bugs. It describes current problems like developers feeling pressure to deliver code quickly without proper testing. This leads to bugs found later by testers, wasting time on rework. The team analyzed root causes like lack of test automation and testers. They decided to break down silos between developers and testers. The new process involves test-driven development, continuous testing, and demos at quality gates. While not all user stories were completed, the delivered stories had no bugs found by clients, showing the new process improved quality.
Introduction to Agile & Scrum
This document provides an overview of an introduction workshop on Agile and Scrum. The workshop covers topics such as the history and principles of Agile, an introduction to Scrum frameworks and roles, and exercises on writing user stories and estimating story points. Participants will learn about Agile and Scrum methodologies, how to write and evaluate user stories, and techniques for relative estimation like planning poker. The goal is for participants to understand key Agile and Scrum concepts and practices and be able to apply them.
Scrum is good - but kanban is better
Scrum is a great way to start practising Agile. But it's not perfect. Are you struggling to get stories tested within the sprint? I sprint planning taking hours and making everyone miserable? These are the slides from the session I presented at Agile Cymru 2016, describing the experience of one team that moved from Scrum to Kanban.
Effective Code Review (Or How To Alienate Your Coworkers)
In this talk, the architects of Perforce Swarm will guide you through the process of starting and updating a code review. They will also share some of their secrets for performing effective reviews. Learn how to start and update code reviews using Swarm, best practices for performing effective review, and the benefits of pre-commit automated testing and deployment.
Evaluation question 6
The document discusses various technologies used to construct a film project and what was learned from using each technology. The main technologies discussed and their advantages and disadvantages included the Apple iMac for providing software like Final Cut Express and GarageBand, the Apple iPhone for research and photos, a Canon camera for filming footage, Final Cut Express for editing, GarageBand for sounds, YouTube for research, Blogger for sharing work, and PowerPoint for presenting. The overall experience provided learning about using technologies for filmmaking and their capabilities as well as limitations.
Notes from sqa days 17.pptx
1. Have a list of stories before sprint planning and break each story into tasks no more than 2 days long. This ensures everyone is on the same page during planning and tasks are easy to track.
2. Do small "demos" of test results to teammates, gathering feedback to improve testing. This spreads knowledge and increases quality and fun.
3. Continue tracking progress and checking improvements during retrospectives to increase productivity, quality and happiness.
4. Consider microservices architecture to clean the automation framework and decrease test time by reducing pre-conditions.
Creating change from within - Agile Practitioners 2012
Faced with management that do not care about "being agile" what can a single developer do? Quite a lot!
Every developer has the power to improve the organization he works in in small iterative steps – and I can show you how.
If you want to make the change and don't know where to start – look no further, in this session I'll share my experience and show a few tips and tricks I learnt. As well as discuss the do and don'ts that can make all the.
- How to be agile developer in a waterfall company.
- Influencing people without formal authority.
- Using the right practices that makes the difference
- How to avoid alienating people
- Discovering your allies
- Know when to fight and when to "retreat" and cut your losses
- Making a change without disrupting the daily routine
- What being an agile evangelist is all about
iOS Scroll Performance
This presentation by Kyle Sherman, LinkedIn iOS Developer for the SlideShare iOS app, goes over fixing issues with jittery scroll performance in iOS applications. The presentation goes over the basics of using Instruments to measure and fix problems, tips for using Instruments, and a concrete example from the new LinkedIn iOS flagship application.
Similar to Main Talk v1.1 (20)
Android Developer Skills, Techniques, and Patterns
Android Developer Skills, Techniques, and Patterns
Effective Code Review (Or How To Alienate Your Coworkers)
Effective Code Review (Or How To Alienate Your Coworkers)
Creating change from within - Agile Practitioners 2012
Creating change from within - Agile Practitioners 2012
More from Ash Winter
Testability Advocacy Canvas
A coaching aid for those who want to help others achieve greater testability within their development team and wider organisation. Additionally can be used to track your own journey.
Testability Sales Pitch
Testability can make our testing lives so much better. But we need to sell it to those who can pay for the changes needed. Find out what they need (delivery, flow, stability, resilience), how it can be measured the use the handy examples below!
Architectural Testability Workshop for Test Academy Barcelona
Workshop delivered at Test Academy Barcelona on 30th January 2020. Including the Team Test for Testability, Testability Tactics, Testing Smells and the CODS Model.
Testability Squad Health Check
Based on the Spotify Squad Health Check and the 10 P's of Testability model by Robert Meaney, a means of seeing how your testable your products are.
Testability is Everyone's Responsibility
Testability is a first class concern for all disciplines within software development. There, I said it. No hedging, no nebulous phrasing, maybes or it depends.
Too often we labour under systems that are hard to test, manifesting themselves with frantic searches for more testers, lengthy acceptance test runs, fearful testing for regressions with a hopeful release at the end. Worst of all, it usually ends up with a project manager sat on the testers desk asking 'when will testing be done.' It's never done, it can only stop, just so you know.
Throughout my career, often the testability of a system has been deemed to be the testers concern. If something was hard to test, then it was the testers problem. However, the causes of low testability effect the activities of all disciplines, whether it be speed of feedback to developers or flow of value generating features for product managers.
During the talk, we will cover:
* How testability is a key advantage in building systems of ever increasing complexity.
* Why it's important for developers and operational stakeholders to build inherently testable systems.
* What testers can do to be catalysts for testability improvements.
The activity of testing is rarely the bottleneck, how testable your system is is your problem. Poor testability cannot be remedied by one discipline alone. It's for all of us to care about.
Testers Guide to the Illusions of Unit Testing
One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. Being able to influence this type of testing in a positive manner is a skill that testers will need to get to grips with, as more companies start to embrace a model of lone testers in cross functional teams. The shift of focus from primarily the testing that testers do, to the testing that the team does, is a key shift in thinking and behaviour.
To facilitate this shift, I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers and help us realise what other layers of testing can cover most effectively. The last point is pertinent here, as knowing and guiding unit testing brings the role of integration, acceptance and exploratory testing into sharp focus.
This is a topic that has always intrigued me, having predominantly worked as a single tester on a team for the last five or so years. I reached out to the community with the question “What do testers believe about unit testing?” and received a lot of engagement. The good users of Twitter added another 50 or so illusions that testers might have about this layer of testing. I figured that based on that level of engagement, maybe this would make an interesting talk! It wasn’t only testers who responded too, suggesting that there might be some shared illusions about unit testing that are cross disciplinary.
The list alone is interesting but now I would like to share my analysis of it with you, focusing on:
* Recurring themes within the list and how to address them as a tester or developer.
* Particular illusions to look out for with examples from my recent past.
* A guide for developers to engage with testers on unit testing, and testers with developers.
10 P's of Testability
Lightning talk based on the 10 P's of Testability by Robert Meaney, talk designed by Ash Winter. Make your testing life better by embrace testability as a team.
The Wheel of Testing
One of my recent endeavours has been to create a "career model" for the testers within my organisation. I sat in my office at home and designed "the testing wheel". I wanted it to be simple, inclusive and offer questions but no answers.
Careers are long and winding. My own career has not been a linear progression, so building a linear model seemed wrong to me. But, this brought me into conflict with the ideas of others.
My experience report will show the highs and lows of this model after introducing it into the wild. People still tried to measure and rank with it, got mad people got when I refused to answer the questions it posed. Finally how it spread and entered battle with wider organisations career models.
Making testability our mission
This is a call to action. On our cross functional teams and during our devops transformations we talk about how testing is for the whole team. Quality is everyone's responsibility. How much are we really doing to make this happen? Often we are working on systems that are hard to test for many reasons, but if we simply do more testing, write more automation we are neglecting what should be our main mission, advocating for increasing levels of testability, to truly get everyone involved in testing. We all have stories about how something is difficult to test, often never being tested or certainly left with the tester to figure it out. It doesn't have to be this way.
During my talk, I want to introduce a set of principles for testability engineering. A new way to approach our work as testers. These principles will tackle how we make our systems more observable, controllable, how we share knowledge across teams and improve the testability of our dependencies. I believe it is time to create a new focus on testability, as it affects everything we do, what our teams do and beyond into how value is delivered for customers.
I want you to take away from the talk:
* Why a focus on testability can multiply your effectiveness as a tester
* What the principles of testability engineering are and how to advocate for them
* How you can make iterative changes to what you do in order to embrace testability
New technology and complexity is rendering many software development techniques and paradigms obsolete at an increasing rate. We already exist in a space where an infinite number of tests of an array of different types can be performed. A new mission is needed, one that leverages the varied talents of all kinds of testers and culminates in a new focus on the exponential benefits that testability brings.
A Testers Guide to the Myths, Legends and Tales of Unit Testing
One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. Being able to influence this type of testing in a positive manner is a skill that testers will need to get to grips with, as more companies start to embrace a model of lone testers in cross functional teams. The shift of focus from primarily the testing that testers do, to the testing that the team does, is a key shift in thinking and behaviour.
To facilitate this shift, I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers, and help us realise what other layers of testing can cover most effectively. The last point is pertinent here, as knowing and guiding unit testing brings the role of integration, acceptance and exploratory testing into sharp focus.
Testing Below the Application
This document discusses testing infrastructure components that lie beneath applications. It defines infrastructure as the building blocks applications depend on, like hardware, virtualization, containers, and software. The author argues that testers should care about infrastructure testing because infrastructure problems are often found at the wrong level, and the product as a whole is symbiotic between applications and infrastructure. Various testing principles, examples, tactics, and tools are provided for both human/deterministic and machine/deterministic testing of infrastructure, as well as human/random and machine/random approaches.
Shift Testability
The document discusses the importance of testability in software development. It argues that focusing on testability, rather than just features, can lead to important benefits like reduced time to start testing, lower unplanned downtimes, and increased ability to observe and understand the entire system. The document advocates for approaches like enabling faster branching to devices for testing, more automation, and greater collaboration between development and operations teams to improve testability.
Part of the Pipeline
Nobody /really/ likes change, its human nature. Testers have a special relationship with changing tools and techniques, they change and we tend to flounder a little and end up very nervous about our place in the new world. Continuous delivery is one such circumstance, I see and speak to many testers really struggling. However, with a significant shift in outlook and a chunk of personal development, testers can excel in environments such as these. It’s time to start to get out in front of a changing world, rather than always battling to catch up.
I want to share my experience of adding value as a tester in a continuous delivery environment, what new technologies and techniques I've learned, using your Production environment as an oracle, advocating testability and most crucially, not overestimating what our testing can achieve. Testing is not the only form of feedback, it’s time to let go of some the aspects of testing we cling to.
Continuous delivery adds richness and variety to our role as testers. To me, it is a facilitator for the autonomy and respect that testers have craved for a long time, so let’s get involved...
Scroll Based Testing Strategy
No one paying attention to your test strategy? Its too long. More crucially, it has no scrolls. Here's a template for the agile testing quadrants, but with scrolls for extra unforgettability.
Coaching Model for Unrecognised Internal Models
This document proposes a coaching model to help testers recognize the testing models they already use intuitively and help them improve. The model focuses on using questioning rather than providing answers to guide testers to higher levels of thinking based on Bloom's Taxonomy. By getting testers to apply models through practice and reflection, and by iterating the model over time based on emergent needs, the coaching model aims to improve testing skills through collaborative learning.
Critical Thinking for Consultants-External
Critical thinking is important for testers as it helps them challenge assumptions, gather evidence to prove or disprove assumptions, and ask questions to improve their understanding. It is important for testers to think like a "Thinking Tester" by challenging beliefs, trying new things without fear of failure, seeing testing as an experiment to gather insights, and improving the product and project. When gathering data through questions, testers should understand stakeholders, consider different perspectives, and make it a collaborative and fun process. When analyzing data, testers should look at issues from different angles, understand limitations and biases, and determine root causes and risks. As consultants, testers need to apply critical thinking carefully and avoid antagonizing clients, while still facilitating
Ash Versus Consulting V1 - External
The document provides tips and advice for consulting based on the presenter's experience. Some of the key points covered include:
1) Consulting deals with human behavior and the variety that comes from people having different needs. Effective consulting requires questioning norms and focusing on root causes rather than symptoms.
2) As an agent working for clients, consultants have little direct power and must rely on building relationships and expertise. It is important to understand the different types of clients and their interests in advice.
3) A consultant's testing skills are more important than domain knowledge. Filling knowledge gaps for clients and adapting to their needs helps expand one's role.
More from Ash Winter (17)
Architectural Testability Workshop for Test Academy Barcelona
Architectural Testability Workshop for Test Academy Barcelona
A Testers Guide to the Myths, Legends and Tales of Unit Testing
A Testers Guide to the Myths, Legends and Tales of Unit Testing
Main Talk v1.1
- 1. What Pokémon GO has taught us about testing & quality…
- 2. Intro What team are you?
- 3. A Brief History Niantic former Google Subsidiary
- 6. Then it went a tiny bit wrong…
- 7. App Freezing • App had to be rebooted • Lost Pokemon and items
- 8. No Crashes Rule • Crash and you burn • Or not • Kept on playing
- 9. Scaling Problems • Servers became overloaded • Bots spamming servers
- 10. Keep On Keeping On • Hitting new markets over scalability • Timing is a quality criteria
- 11. Poorly Designed Features •Removal of 3 paw prints •Battery saver mode
- 12. Features != Quality •Focus on your core idea •Do few things well
- 14. Quality is composite • Wider system • Remove & add • Compelling idea
- 15. GPS Weirdness • GPS inaccurate • Unusable on some LG phones
- 16. Can’t Catch ‘Em All • Device fragmentation • A/B testing effective • Very gradual release
- 17. Quality Continuum • Quality is on a multi dimensional continuum • Great brand & idea provides elasticity
- 18. Workshop Time… • What did this product teach us about testing? • Everyone has an opinion! • What would you have done differently?
- 19. Testing is about having a balanced approach…
- 20. So lets build one… • HT to Dan North for his very useful ‘Testing Corners’
- 21. In the Blue Corner!
- 22. Types of testing and test ideas that (mostly) fit
- 24. Get Ready… • Groups! Peeps you don’t know if you can. • Post Its, Pens, Paper! • 15-20 mins • Reflect…
- 25. Go!