Testers developers think differently
•
1 like•441 views
The document discusses differences in how testers and developers think and approach their work. It notes that testers focus on what can go wrong with a system based on empirical observation, are comfortable with tedium and conflicts, and report problems, while developers focus on theoretical design and how the system can work, automate tedium, and aim to understand problems rather than just report them. The document emphasizes that quality is a team effort and stresses the importance of partnership between testers and developers with a good attitude.
Report
Share
Report
Share
Recommended
Test driven development
This document discusses Test Driven Development (TDD). TDD helps create clean, simple code designs with low coupling between components. Writing tests first allows developing code with confidence as tests accumulate. It helps avoid technical debt by refactoring code as needed. TDD produces documentation in the form of executable tests and enables continuous integration and delivery. The TDD process follows the "Red-Green-Refactor" mantra of writing a failing test first, then code to pass the test, and refactoring code as needed. Tests should be written to be fast, independent, repeatable, self-validating, and timely. Tools and coding dojos can help practice and improve TDD skills.
[HCMC STC Jan 2015] Creating a Better Testing Future
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Lee Copeland
The IEEE 829 Test Documentation standard is thirty years old this year. Boris Beizer’s first book on software testing also turned thirty. Testing Computer Software, the best selling book on software testing, is twenty-five. During the last three decades, hardware platforms have evolved from mainframes to minis to desktops to laptops to tablets to smartphones. Development paradigms have shifted from waterfall to agile. Consumers expect more functionality, demand higher quality, and are less loyal to brands. The world has changed dramatically and testing must change to match it. Testing processes that helped us succeed in the past may prevent our success in the future. Lee Copeland shares his insights into the future of testing, sharing his Do’s and Don’ts in the areas of technology, organization, test processes, test plans, and automation. Join Lee for a thought provoking look at creating a better testing future.
Design talk
This document discusses design challenges for cybersecurity products. It notes that many security products are designed by engineers and focus more on technical functionality than user experience. This can lead to products with inconvenient or confusing interfaces. The document advocates for giving design equal priority to technical aspects in security products. It provides examples of how poor user experience, like generating too many alerts or making multi-factor authentication annoying, can reduce security by causing users to disable protections. The document concludes that great design can differentiate enterprise security products and actually make the online world safer by enabling usability of security mechanisms.
ExumaTech Dev Process
Over the past couple of years we've migrated from a traditional, waterfall development process to more of an iterative one. At the same time we've moved from structured to object oriented programming languages. These are big transitions and we are proud to say that we've released our first .NET product built on an object oriented framework.
We have recently adopted the Lean Start-up Process first introduced by Eric Ries. This is a presentation I gave at our customer advisory board meeting that was adapted from Eric's presentation found here:
http://www.slideshare.net/startuplessonslearned/eric-ries-lean-startup-presentation-for-web-20-expo-april-1-2009-a-disciplined-approach-to-imagining-designing-and-building-new-products
Find us at http://exumatech.com or @ExumaTech
Agile Testing 20021015
This document discusses agile testing and its principles. It defines agile testing as testing practices that follow the agile manifesto and treat development as the customer of testing. The key principles of agile testing are that individuals and interactions are valued over processes, working software is valued over documentation, and responding to change is valued over following a plan. It also discusses specific agile development methodologies like extreme programming and the role of testing in agile projects.
Kung fu Programming
The document discusses principles for agile programming based on lessons from Kung Fu Panda. It recommends frequently testing code through a variety of automated tests. Programmers should integrate code daily and follow common coding standards and conventions as a team. Pair programming and collaboration are emphasized to reduce bugs and spread knowledge. Simplicity and shipping working code each sprint are priorities over unnecessary features. Finding a balance with occasional refactoring is important for maintaining focus.
Will Robots Replace Testers?
This talk suggests how we might make sense of the tools landscape of the near future, where the pressure to modernise processes and automate is greatest, and what a new test process supported by tools might look like.
Takeaways:
- We need to take machine learning in testing seriously, but it won’t be taking our jobs just yet
- We don’t need more test automation tools; today we need tools that capture tester knowledge
- Tools that that learn and think can’t work for testers until we solve the knowledge capture challenge.
View On-Demand Webinar: https://youtu.be/EzyUdJFuzlE
[Mush Honda] Software Testers From Good to Great
Typical software testers focus on learning ‘Hard’ skills associated with the responsibilities of their role. However, these skills allow them to become a "Dependable" or "Knowledgeable" tester, rather than a "Great" tester. What are the skills necessary to take you to the next level within your ladder of testing career, to become someone known as "Great" tester? This presentation will identify some of the key skills that can take you to the next level and provides an easy-to-follow roadmap on mastering those skills.
Recommended
Test driven development
This document discusses Test Driven Development (TDD). TDD helps create clean, simple code designs with low coupling between components. Writing tests first allows developing code with confidence as tests accumulate. It helps avoid technical debt by refactoring code as needed. TDD produces documentation in the form of executable tests and enables continuous integration and delivery. The TDD process follows the "Red-Green-Refactor" mantra of writing a failing test first, then code to pass the test, and refactoring code as needed. Tests should be written to be fast, independent, repeatable, self-validating, and timely. Tools and coding dojos can help practice and improve TDD skills.
[HCMC STC Jan 2015] Creating a Better Testing Future
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Lee Copeland
The IEEE 829 Test Documentation standard is thirty years old this year. Boris Beizer’s first book on software testing also turned thirty. Testing Computer Software, the best selling book on software testing, is twenty-five. During the last three decades, hardware platforms have evolved from mainframes to minis to desktops to laptops to tablets to smartphones. Development paradigms have shifted from waterfall to agile. Consumers expect more functionality, demand higher quality, and are less loyal to brands. The world has changed dramatically and testing must change to match it. Testing processes that helped us succeed in the past may prevent our success in the future. Lee Copeland shares his insights into the future of testing, sharing his Do’s and Don’ts in the areas of technology, organization, test processes, test plans, and automation. Join Lee for a thought provoking look at creating a better testing future.
Design talk
This document discusses design challenges for cybersecurity products. It notes that many security products are designed by engineers and focus more on technical functionality than user experience. This can lead to products with inconvenient or confusing interfaces. The document advocates for giving design equal priority to technical aspects in security products. It provides examples of how poor user experience, like generating too many alerts or making multi-factor authentication annoying, can reduce security by causing users to disable protections. The document concludes that great design can differentiate enterprise security products and actually make the online world safer by enabling usability of security mechanisms.
ExumaTech Dev Process
Over the past couple of years we've migrated from a traditional, waterfall development process to more of an iterative one. At the same time we've moved from structured to object oriented programming languages. These are big transitions and we are proud to say that we've released our first .NET product built on an object oriented framework.
We have recently adopted the Lean Start-up Process first introduced by Eric Ries. This is a presentation I gave at our customer advisory board meeting that was adapted from Eric's presentation found here:
http://www.slideshare.net/startuplessonslearned/eric-ries-lean-startup-presentation-for-web-20-expo-april-1-2009-a-disciplined-approach-to-imagining-designing-and-building-new-products
Find us at http://exumatech.com or @ExumaTech
Agile Testing 20021015
This document discusses agile testing and its principles. It defines agile testing as testing practices that follow the agile manifesto and treat development as the customer of testing. The key principles of agile testing are that individuals and interactions are valued over processes, working software is valued over documentation, and responding to change is valued over following a plan. It also discusses specific agile development methodologies like extreme programming and the role of testing in agile projects.
Kung fu Programming
The document discusses principles for agile programming based on lessons from Kung Fu Panda. It recommends frequently testing code through a variety of automated tests. Programmers should integrate code daily and follow common coding standards and conventions as a team. Pair programming and collaboration are emphasized to reduce bugs and spread knowledge. Simplicity and shipping working code each sprint are priorities over unnecessary features. Finding a balance with occasional refactoring is important for maintaining focus.
Will Robots Replace Testers?
This talk suggests how we might make sense of the tools landscape of the near future, where the pressure to modernise processes and automate is greatest, and what a new test process supported by tools might look like.
Takeaways:
- We need to take machine learning in testing seriously, but it won’t be taking our jobs just yet
- We don’t need more test automation tools; today we need tools that capture tester knowledge
- Tools that that learn and think can’t work for testers until we solve the knowledge capture challenge.
View On-Demand Webinar: https://youtu.be/EzyUdJFuzlE
[Mush Honda] Software Testers From Good to Great
Typical software testers focus on learning ‘Hard’ skills associated with the responsibilities of their role. However, these skills allow them to become a "Dependable" or "Knowledgeable" tester, rather than a "Great" tester. What are the skills necessary to take you to the next level within your ladder of testing career, to become someone known as "Great" tester? This presentation will identify some of the key skills that can take you to the next level and provides an easy-to-follow roadmap on mastering those skills.
Agile Testing in the Enterprise 2016
The document discusses challenges with agile testing in large enterprises and across distributed teams. It outlines some of the common challenges such as bureaucracy, multiple concurrent projects, and dependencies between teams. The document then provides several key testing practices that can work across teams, such as coordinating test planning, creating a shared test matrix, and using examples and tests to develop a common language. It emphasizes the importance of transparency between teams by sharing information and dependencies to reduce blame and ensure everyone understands the shared goals.
Continuous Deployment Through Technical Excellence
This document discusses continuous deployment and what is required to achieve it. Continuous deployment means code is always deployed to production. It requires version control, build/deploy pipelines, infrastructure as code, frequent and safe code updates, separation of rollout and activation, and good observability. Achieving it also requires changes to testing, coding, organization, planning, and learning practices. The document recommends starting with improving deployment frequency metrics and removing impediments through small experiments. It emphasizes improving incrementally based on what teams are passionate about or experiencing pain with.
Test driven development using Junit and MockIto
This document discusses test-driven development (TDD) using JUnit. It explains the philosophy of TDD, which is to write tests before writing code by beginning with the test in mind. The TDD process is then outlined as writing a test, running it and seeing it fail, stubbing the routine, running it again and seeing it fail, writing the code, and running it to see it pass. JUnit is introduced as a tool for TDD in Java that uses annotations to identify test methods. Mocking is also briefly discussed as allowing for better and faster testing by integrating different systems and simplifying designs to find bugs faster. Finally, the document suggests looking at a live example of how TDD can improve code
Software quality
Apresentação sobre qualidade de software, mostrando alguns dos fatores que a influenciam, tipos de testes, além de abordagens para torná-la uma das prioridades da equipe.
Markus Clermont - Surviving in an Agile Environment - Google - SoftTest Ireland
Visit www.softtest.ie and join our mailing list to hear about upcoming Irish Software Testing Events.
'The Real Agile Testing Quadrants' with Michael Bolton
EuroSTAR Conferences, with the support of ISA Software Skillnet, Irish Software Innovation Network and SoftTest, were delighted to bring you a half-day software testing masterclass with Michael Bolton
In this session, Michael Bolton (who has extensive experience as a tester, as a programmer, and as a project manager) explained the role of skilled software testers, and why you might not want to think of testing as "quality assurance".
He present ideas about the relationship between management and testers, and about the service that testers really provide: making quality assurance possible by lighting the way of the project. For those of you who who attended this event, we really hope it was of use to you in your testing careers.
www.eurostarconferences.com
Testing is a team problem
This document summarizes Janet Gregory's work promoting agile testing practices. It notes that she has been involved with agile teams since 2000 and has authored books and online courses on agile testing. The document discusses how testing should be a shared responsibility of the whole team. It emphasizes that testing provides feedback to improve quality, not just find bugs, and explains practices like examples, acceptance test-driven development, and exploratory testing that involve the whole team in testing activities.
Help Me, I got a team of junior testers!
The document provides guidance for managing a team of junior testers. It discusses challenges such as lack of skills and experience in junior testers. It recommends setting clear expectations, providing frequent communication and feedback, ensuring knowledge sharing, and protecting the team to help them succeed. Patience and structure are important, as is repeating key messages, to help junior testers learn and improve. The goal is for the team to work cooperatively toward a common objective.
Build a great Technical Team
The document discusses how to build a great technical team by focusing on people, practices, and tools. It emphasizes choosing the right people and teaching them technical practices through deliberate practice and experiments. It also stresses continuously improving through shortening feedback cycles, learning from failures, and using retrospectives to refine practices.
Dont be a tool
The document discusses various methods and tools for designing systems and prototypes quickly, including:
1. Agile and lean methodologies that emphasize iterative design, minimum viable products, and customer feedback.
2. Design sprints, which are 5-day events to solve problems through research, solution generation, prototyping, and user testing.
3. The importance of design systems to create reusable components and quickly build high-fidelity prototypes.
4. Different types of design and prototyping tools that can help implement the above methods, including graphic tools, prototyping tools, and tools to record user testing sessions.
A Rapid Introduction to Rapid Software Testing
You're under tight time pressure and have barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Michael Bolton introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and "minds-on" exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Michael to see how rapid testing focuses on both the mind set and skill set of the individual tester who uses tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.
Become a Quality Enabler
Instead of being just another cost center for a customer where you develop what you're told, how can you become proactive by understanding the business requirement and truly being a Quality Enabler? Xian Tharindra shares some great insights on this
A Rapid Introduction to Rapid Software Testing
This document provides a summary of a presentation on Rapid Software Testing. The presentation was given by Michael Bolton of DevelopSense and covered the methodology and mindset of rapid software testing. It emphasizes testing software expertly under uncertainty and time pressure. The presentation defines rapid testing as testing more quickly and less expensively while still achieving excellent results. It compares rapid testing to other approaches like exhaustive, ponderous, and slapdash testing. The presentation also discusses principles of rapid testing, how to recognize problems quickly using heuristics, and testing rapidly to fulfill the mission of testing.
Key Success Factors for Agile Testing 2016
Success factors and practices from the books "Agile Testing" and "More Agile Testing" by Janet Gregory and Lisa Crispin
An Introduction to XP and Agile
This document provides an introduction to eXtreme Programming (XP) and agile software development methods. It discusses some common problems with traditional software development approaches such as taking too long, costing too much, and requiring too many people. XP and agile aim to address these problems through principles like rapid delivery of working software in short iterations, frequent feedback, simplicity, respect, and flexibility. The document outlines XP practices like user stories, pair programming, test-driven development, and daily standups that embody these principles. It concludes by noting that agile methods have evolved over decades to become more effective approaches to software development.
Behavior Driven Development—A Guide to Agile Practices by Josh Eastman
The document discusses Behavior Driven Development (BDD) and how it can help increase quality and prepare an organization for increased business demands. It describes BDD as an industry practice where the whole team collaborates on system testing and definition of done. BDD promotes requirements using examples, collaboration between roles, finding defects earlier and more often through automation, and keeping technical debt low.
Test-Driven Development
Test-driven development (TDD) is a software development process that relies on the repetition of a short development cycle of requirements, design, and coding. It promotes writing tests before writing code (test-first design) and helps improve code quality by reducing defects. The TDD cycle involves writing an automated test, running the test and seeing it fail, writing the minimum amount of code to pass the test, and refactoring the code as needed. TDD brings benefits like clarifying requirements, adding executable documentation, and detecting errors early. Acceptance TDD involves automating acceptance tests to define and validate requirements. It helps establish a definition of done and improves team collaboration.
Product Agility: 3 fundamentals from the trenches
There is no silver bullet for Product and Business Agility.
On this talk you will know which are the fundamentals and some of the initiatives in place in the OutSystems Engineering Journey to better responding rapidly and flexibly to ours customers demands.
Test Strategy-The real silver bullet in testing by Matthew Eakin
This document provides an overview of creating a testing strategy. It begins with explaining why a testing strategy is important, as testing accounts for a large portion of IT budgets. It then discusses the key questions a testing strategy should answer: what to test, where to test, when to test, how to test, and who will test.
The document outlines a process for creating a testing strategy, including assessing the current state, defining a future vision, and creating a roadmap to get from the current to future state. It provides examples of what to include under each section of the strategy, such as system architecture under "what to test" and test environments under "where to test". Overall, the document provides guidance on developing a
Treinamento TDD
This document discusses test-driven development (TDD) and different types of software testing. It covers the usual TDD workflow of building code and apps, then testing manually. Over time, as changes become painful, testing is integrated earlier in the process. The document discusses unit testing, the test pyramid with more unit tests than other types of tests, and using TDD to influence class design in object-oriented systems. It provides examples of the Jasmine testing framework and recommends mocking roles rather than objects to isolate dependencies when testing.
Why every Tester should also aspire to be a Developer on his project!-Sandee...
This document discusses why testers should also aspire to be developers on their projects. It notes that software development lifecycles have changed with paradigms like TDD, BDD, ATDD, and Agile requiring more multi-skilled team members. Testing is an intellectual process like coding and analysis. Understanding code helps testers take a business perspective and catch bugs earliest in development which is cheapest. Testers should own test coverage by finding untested code and having developers write tests. While testers' role is to find bugs and ensure quality, quality should be everyone's goal. Testers can better fulfill their role by understanding code more through pairing with developers, writing code, reviewing code, and helping drill
How to detect smelly acceptance tests - Agile Dev Practices
The document discusses smelly acceptance tests and how to improve them. It notes that acceptance tests should describe features from a non-technical perspective, define acceptance criteria before development, and be understandable by everyone. Smelly tests are those that are not explicit, observable, realistic scenarios related to user stories, or instantly observed. The document provides examples of good and bad tests and encourages writing tests at different layers of abstraction, from business workflow to technical, to keep teams aligned.
More Related Content
What's hot
Agile Testing in the Enterprise 2016
The document discusses challenges with agile testing in large enterprises and across distributed teams. It outlines some of the common challenges such as bureaucracy, multiple concurrent projects, and dependencies between teams. The document then provides several key testing practices that can work across teams, such as coordinating test planning, creating a shared test matrix, and using examples and tests to develop a common language. It emphasizes the importance of transparency between teams by sharing information and dependencies to reduce blame and ensure everyone understands the shared goals.
Continuous Deployment Through Technical Excellence
This document discusses continuous deployment and what is required to achieve it. Continuous deployment means code is always deployed to production. It requires version control, build/deploy pipelines, infrastructure as code, frequent and safe code updates, separation of rollout and activation, and good observability. Achieving it also requires changes to testing, coding, organization, planning, and learning practices. The document recommends starting with improving deployment frequency metrics and removing impediments through small experiments. It emphasizes improving incrementally based on what teams are passionate about or experiencing pain with.
Test driven development using Junit and MockIto
This document discusses test-driven development (TDD) using JUnit. It explains the philosophy of TDD, which is to write tests before writing code by beginning with the test in mind. The TDD process is then outlined as writing a test, running it and seeing it fail, stubbing the routine, running it again and seeing it fail, writing the code, and running it to see it pass. JUnit is introduced as a tool for TDD in Java that uses annotations to identify test methods. Mocking is also briefly discussed as allowing for better and faster testing by integrating different systems and simplifying designs to find bugs faster. Finally, the document suggests looking at a live example of how TDD can improve code
Software quality
Apresentação sobre qualidade de software, mostrando alguns dos fatores que a influenciam, tipos de testes, além de abordagens para torná-la uma das prioridades da equipe.
Markus Clermont - Surviving in an Agile Environment - Google - SoftTest Ireland
Visit www.softtest.ie and join our mailing list to hear about upcoming Irish Software Testing Events.
'The Real Agile Testing Quadrants' with Michael Bolton
EuroSTAR Conferences, with the support of ISA Software Skillnet, Irish Software Innovation Network and SoftTest, were delighted to bring you a half-day software testing masterclass with Michael Bolton
In this session, Michael Bolton (who has extensive experience as a tester, as a programmer, and as a project manager) explained the role of skilled software testers, and why you might not want to think of testing as "quality assurance".
He present ideas about the relationship between management and testers, and about the service that testers really provide: making quality assurance possible by lighting the way of the project. For those of you who who attended this event, we really hope it was of use to you in your testing careers.
www.eurostarconferences.com
Testing is a team problem
This document summarizes Janet Gregory's work promoting agile testing practices. It notes that she has been involved with agile teams since 2000 and has authored books and online courses on agile testing. The document discusses how testing should be a shared responsibility of the whole team. It emphasizes that testing provides feedback to improve quality, not just find bugs, and explains practices like examples, acceptance test-driven development, and exploratory testing that involve the whole team in testing activities.
Help Me, I got a team of junior testers!
The document provides guidance for managing a team of junior testers. It discusses challenges such as lack of skills and experience in junior testers. It recommends setting clear expectations, providing frequent communication and feedback, ensuring knowledge sharing, and protecting the team to help them succeed. Patience and structure are important, as is repeating key messages, to help junior testers learn and improve. The goal is for the team to work cooperatively toward a common objective.
Build a great Technical Team
The document discusses how to build a great technical team by focusing on people, practices, and tools. It emphasizes choosing the right people and teaching them technical practices through deliberate practice and experiments. It also stresses continuously improving through shortening feedback cycles, learning from failures, and using retrospectives to refine practices.
Dont be a tool
The document discusses various methods and tools for designing systems and prototypes quickly, including:
1. Agile and lean methodologies that emphasize iterative design, minimum viable products, and customer feedback.
2. Design sprints, which are 5-day events to solve problems through research, solution generation, prototyping, and user testing.
3. The importance of design systems to create reusable components and quickly build high-fidelity prototypes.
4. Different types of design and prototyping tools that can help implement the above methods, including graphic tools, prototyping tools, and tools to record user testing sessions.
A Rapid Introduction to Rapid Software Testing
You're under tight time pressure and have barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Michael Bolton introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and "minds-on" exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Michael to see how rapid testing focuses on both the mind set and skill set of the individual tester who uses tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.
Become a Quality Enabler
Instead of being just another cost center for a customer where you develop what you're told, how can you become proactive by understanding the business requirement and truly being a Quality Enabler? Xian Tharindra shares some great insights on this
A Rapid Introduction to Rapid Software Testing
This document provides a summary of a presentation on Rapid Software Testing. The presentation was given by Michael Bolton of DevelopSense and covered the methodology and mindset of rapid software testing. It emphasizes testing software expertly under uncertainty and time pressure. The presentation defines rapid testing as testing more quickly and less expensively while still achieving excellent results. It compares rapid testing to other approaches like exhaustive, ponderous, and slapdash testing. The presentation also discusses principles of rapid testing, how to recognize problems quickly using heuristics, and testing rapidly to fulfill the mission of testing.
Key Success Factors for Agile Testing 2016
Success factors and practices from the books "Agile Testing" and "More Agile Testing" by Janet Gregory and Lisa Crispin
An Introduction to XP and Agile
This document provides an introduction to eXtreme Programming (XP) and agile software development methods. It discusses some common problems with traditional software development approaches such as taking too long, costing too much, and requiring too many people. XP and agile aim to address these problems through principles like rapid delivery of working software in short iterations, frequent feedback, simplicity, respect, and flexibility. The document outlines XP practices like user stories, pair programming, test-driven development, and daily standups that embody these principles. It concludes by noting that agile methods have evolved over decades to become more effective approaches to software development.
Behavior Driven Development—A Guide to Agile Practices by Josh Eastman
The document discusses Behavior Driven Development (BDD) and how it can help increase quality and prepare an organization for increased business demands. It describes BDD as an industry practice where the whole team collaborates on system testing and definition of done. BDD promotes requirements using examples, collaboration between roles, finding defects earlier and more often through automation, and keeping technical debt low.
Test-Driven Development
Test-driven development (TDD) is a software development process that relies on the repetition of a short development cycle of requirements, design, and coding. It promotes writing tests before writing code (test-first design) and helps improve code quality by reducing defects. The TDD cycle involves writing an automated test, running the test and seeing it fail, writing the minimum amount of code to pass the test, and refactoring the code as needed. TDD brings benefits like clarifying requirements, adding executable documentation, and detecting errors early. Acceptance TDD involves automating acceptance tests to define and validate requirements. It helps establish a definition of done and improves team collaboration.
Product Agility: 3 fundamentals from the trenches
There is no silver bullet for Product and Business Agility.
On this talk you will know which are the fundamentals and some of the initiatives in place in the OutSystems Engineering Journey to better responding rapidly and flexibly to ours customers demands.
Test Strategy-The real silver bullet in testing by Matthew Eakin
This document provides an overview of creating a testing strategy. It begins with explaining why a testing strategy is important, as testing accounts for a large portion of IT budgets. It then discusses the key questions a testing strategy should answer: what to test, where to test, when to test, how to test, and who will test.
The document outlines a process for creating a testing strategy, including assessing the current state, defining a future vision, and creating a roadmap to get from the current to future state. It provides examples of what to include under each section of the strategy, such as system architecture under "what to test" and test environments under "where to test". Overall, the document provides guidance on developing a
Treinamento TDD
This document discusses test-driven development (TDD) and different types of software testing. It covers the usual TDD workflow of building code and apps, then testing manually. Over time, as changes become painful, testing is integrated earlier in the process. The document discusses unit testing, the test pyramid with more unit tests than other types of tests, and using TDD to influence class design in object-oriented systems. It provides examples of the Jasmine testing framework and recommends mocking roles rather than objects to isolate dependencies when testing.
What's hot (20)
Continuous Deployment Through Technical Excellence
Continuous Deployment Through Technical Excellence
Markus Clermont - Surviving in an Agile Environment - Google - SoftTest Ireland
Markus Clermont - Surviving in an Agile Environment - Google - SoftTest Ireland
'The Real Agile Testing Quadrants' with Michael Bolton
'The Real Agile Testing Quadrants' with Michael Bolton
Behavior Driven Development—A Guide to Agile Practices by Josh Eastman
Behavior Driven Development—A Guide to Agile Practices by Josh Eastman
Test Strategy-The real silver bullet in testing by Matthew Eakin
Test Strategy-The real silver bullet in testing by Matthew Eakin
Viewers also liked
Why every Tester should also aspire to be a Developer on his project!-Sandee...
This document discusses why testers should also aspire to be developers on their projects. It notes that software development lifecycles have changed with paradigms like TDD, BDD, ATDD, and Agile requiring more multi-skilled team members. Testing is an intellectual process like coding and analysis. Understanding code helps testers take a business perspective and catch bugs earliest in development which is cheapest. Testers should own test coverage by finding untested code and having developers write tests. While testers' role is to find bugs and ensure quality, quality should be everyone's goal. Testers can better fulfill their role by understanding code more through pairing with developers, writing code, reviewing code, and helping drill
How to detect smelly acceptance tests - Agile Dev Practices
The document discusses smelly acceptance tests and how to improve them. It notes that acceptance tests should describe features from a non-technical perspective, define acceptance criteria before development, and be understandable by everyone. Smelly tests are those that are not explicit, observable, realistic scenarios related to user stories, or instantly observed. The document provides examples of good and bad tests and encourages writing tests at different layers of abstraction, from business workflow to technical, to keep teams aligned.
Improving developer tester collaboration with microsoft visual studio 2010
A presentation I gave at the VS 2010 launch on the new features of VS2010 that improve developer/tester collaboration
Tester vs. Developer
This presentation describes the relationship between a software tester and a software developer and how it relates for delivering a high quality outcome.
Tester vs Developer
Remind tester and developer that their ultimate goal is to maximize the value of the product and that happens only through great teamwork.
The Manager's Dilemma
This lightning talk describes how to deal with and maybe overcome the manager's dilemma of being left behind in an agile or lean transformation.
Become Software Tester or Developer
This is the slide deck that Director of Delivery of KMS presented at Can Tho University on Saturday, September 28th, 2013.
Tester career path
This document discusses career paths for testing engineers. It begins by describing a typical interview where the candidate's lack of technical skills is apparent. It then discusses a tester's concerns about their career progression and perceptions of testers. The document outlines stories of individuals who grew their careers in testing over long periods of time, taking on roles such as test automation engineer and testing director. It provides advice on making good career choices by gaining experience in one's current role and waiting for opportunities, rather than changing roles frequently or due to money alone. Specific career paths are suggested such as build master, release engineer, and testing management. The document emphasizes that experience over time strengthens one's position and makes them competitive for career growth.
Viewers also liked (8)
Why every Tester should also aspire to be a Developer on his project!-Sandee...
Why every Tester should also aspire to be a Developer on his project!-Sandee...
How to detect smelly acceptance tests - Agile Dev Practices
How to detect smelly acceptance tests - Agile Dev Practices
Improving developer tester collaboration with microsoft visual studio 2010
Improving developer tester collaboration with microsoft visual studio 2010
Similar to Testers developers think differently
Dare to Explore: Discover ET!
Gain a deeper understanding of what Exploratory Testing (ET) is, the essential elements of the practice with practical tips and techniques, and finally, ideas for integrating ET into the cadence of an agile process
How to successfully grow a code review culture
As a team grows, code ownership is distributed. Code review becomes increasingly important to support the maintainability of complex codebases. An effective code base is on that can be worked on collaboratively by a team.
In this talk we'll discuss how to introduce a successful code review culture to your development team that will foster the idea of shared ownership. This in turn will result in a happy and healthy code base.
https://webexpo.net/prague2016/talk/how-to-successfully-grow-a-code-review-culture/
5 myths and realities
The document discusses 5 myths about software testing and what it takes to become a great tester. The myths are that software testing does not require passion, challenge, programming skills, analysis, or offer career growth opportunities. However, software testing requires broad technical skills, deep domain knowledge, problem solving abilities, programming, analytical reasoning, and innovative thinking. Becoming a great tester also requires soft skills, the right attitude, passion for technology, and a willingness to continually learn and adapt to changes. The document provides a roadmap for testers to define career plans, leverage social abilities, and remain determined and innovative to succeed in software testing roles.
Leading Change from the Quality team
Change is hard. Most change efforts fail. Often, to improve software quality we need to influence how other teams do their jobs. This presentation shows a 4 step method to effectively lead change, illustrated by 2 examples.
I Don't Code, Am I No Longer Useful
This document discusses the changing role of testers in software development. As more testing becomes automated through programming, some question whether non-coding testers are still useful. However, the document notes there are many non-coding tasks in software development. It provides examples of non-programming work testers can do, such as working with product management to select features and clarify requirements, learning the system thoroughly to focus testing, and helping the team deliver value through non-coding improvements. The conclusion is that while testing may involve more programming, there are still needed roles for non-coding specialists to provide quality and domain expertise. Diversity of skills and perspectives remains important for software teams.
Agile Development MethodologiesThree CommunitiesProjec.docx
Agile Development Methodologies
Three Communities
Project stakeholders (Customers)
Development organization management
Developers
The Agile Manifesto
Indivduals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
The Agile Principles
1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agilel processes harness change for the customer’s competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of monthsm with a preference for the shorter time scale.
From the Agile Alliance: www.agilealliance.com
More Agile Principles
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to, and within a development team is face-to-face conversation.
Still more Agile Principles
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development.
9. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
10. Continuous attention to technical excellence and good design enhances agility.
Even more Agile Principles
11. Simplicity – the art of maximizing the amount of work not done – is essential.
12. The best architectures, requirements, and designs emerge from self-organizing teams.
13. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Major Agile Methodologies
Scrum
Extreme Programming
Version of the Unified Process
Evo
Crystal family of methodologies
Scrum
Single team of three to nine
Multiple teams each with three to nine members each.
Representatives from teams meet daily.
Common project room
Daily stand-up meeting
Iteration Is thirty calendar days
Emphasis on empirical rather than defined process.
May be easily combined with other methodologies to provide greater specification of specific activities.
The Scrum Lifecycle
Lifecycle has four phases:
Pre-game
Planning
Staging
The Game
Development
Release
Development may iterate, typically 3 to 8 times.
Called sprints lasting one month each
Scrum Planning
Purpose:
Establish vision
Set expectations
Secure funding and other needed resources
Activities
Write vision
Develop budget
Form initial Product Backlog
Estimate items
Exploratory design and prototypes
Scrum Staging
Purpose:
Identify more requirements
Prioritize for first iteration
Activities
Planning
Exploratory design and prototypes
Scrum Development
Purpose:.
Extreme Programming (XP): Revisted
In his recent book, Clean Agile, Robert C "Uncle Bob" Martin chooses Extreme Programming (XP) for the basis of his explanation of Agile because "of all the Agile processes, XP is the best defined, the most complete, and the least muddled."
So why is it that in my professional life I only hear us speaking about Agile in terms of Scrum, Sprints, and possibly Kanban? Often I mention XP and people are not sure what I mean. Am I sure myself?
Coined in 1999 by Kent Beck and Ward Cunningham, XP has been with us for twenty years, but may of its practices have been with us for much longer. Many of them will be familar to you, but did you know they came from XP?
This talk aims to take us back to what XP is, how it fits in the Agile world, how it sits alongside other methodologies, and why, like Uncle Bob, I believe it is the best defined methodology, and what we should all be talking about.
The talk is based on a heavily refactored talk that Mike gave previously at Agile on the Beach conference, updated for 2020.
Given at Ox:Agile Meetup on February 11th 2020: https://www.meetup.com/OXAGILE/events/nxrdmrybcdbpb/
Adopting innovation
How can you adopt innovation at your company ? Why should you bother ? How can you do it ? What matters and why ?
Here I share my learning from starting and running a startup and building data science products in thomson reuters and other organizations
TDD in Agile
The document discusses test driven development (TDD) in an agile environment. It covers topics like the agile manifesto, evolutionary design, TDD steps and philosophy, myths about TDD, test qualities, benefits and costs of TDD, plugins and language support. The author shares their experience with TDD, noting that it improved code quality and refactoring while requiring support from leads to be effective long-term. Acceptance TDD is recommended to ensure shared understanding of what is being built.
5myths_realitiesandbecominggreattesters
The document discusses 5 common myths about software testing and what it takes to become a great tester. The myths are that testing does not require passion, challenge, programming, analysis, or offer career growth. However, testing requires passion for technology, deep domain knowledge, analytical and problem-solving skills, programming, innovative thinking, and offers career growth through roles like test lead or manager. Becoming a great tester requires skills like communication, determination, passion, innovation, and teamwork as well as defining a career plan and turning motivation into habit.
5 Myths and Realities
The document discusses 5 common myths about software testing and what it takes to become a great tester. The myths are that testing does not require passion, challenge, programming, analysis, or offer career growth. However, testing requires technical skills, passion, problem-solving abilities, and programming. Becoming a great tester also requires skills like determination, innovation, teamwork, and lifelong learning. Testing careers can grow into technical leadership roles through skills like automation and Agile practices. Vietnam is highlighted as a growing destination for software testing jobs.
Agile testing
1. Agile testing follows the agile manifesto which values individuals, interactions, working software, and responding to change over processes, tools, documentation, and following a plan.
2. Context-driven testing principles state that the value of practices depends on their context, there are no best practices, people are most important, projects unfold unpredictably, and good testing requires judgment.
3. Agile methodologies like XP emphasize test-first programming, pair programming, short iterations, refactoring, user stories, and acceptance testing. Testers provide information to the team and find ways to set goals rather than focus on mistakes.
Lean UX
The document discusses the foundations of Lean UX which include design thinking, agile software development, and the Lean Startup method. It emphasizes that Lean UX teams should be cross-functional, small, co-located, and focus on outcomes rather than outputs. The principles of Lean UX are to remove waste, conduct continuous discovery with customers, embrace failure for learning, and get team members out of the office to engage with users.
Executable Specifications with FitNesse and Selenium
This document discusses using executable specifications with FitNesse and Selenium to minimize miscommunications between business and development teams. It introduces Dawn Cannan and describes the Test Automation Pyramid. Key points covered include defining examples as tests to get everyone on the same page early, preventing bugs, and challenges of test automation in the browser like locating elements and synchronization. The FitNesse framework is presented as a way to define Selenium tests in a wiki accessible to all team members.
The Un-researched Persona
This document discusses the importance of user research in developing effective personas for software projects. It provides examples of personas created both with and without research to highlight the benefits of research. Personas developed without research for a content management system lacked defining details and motivations. In contrast, personas created for a competitive product were improved through domain research, strengthening requirements and relationships with users. The document advocates spending time on research and sharing personas to realize benefits like a shared understanding, building empathy, and defining the right requirements to save development effort.
Lean Startup 301
Aubrey Smith, Sparked Advisory
In this training, we will build on the foundation established in Lean Startup 101 and 201 by delving into examples and cases of the Lean Startup concepts in action. Attendees of Lean Startup 301 will be exposed to cutting edge work from thought leaders and experts using Lean Startup in practice today — at startups and within the enterprise. Participation in this session is essential: You will be asked to help design an MVP and experiment to test critical Leap of Faith Assumption(s) in groups and will be encourage to share experiences. The session is designed to allow attendees to stretch their skills and to push one-another to ‘learn by doing’. The session will also include:
Sample cases and live interviews with practitioners highlighting the application of core concepts;
Exercises designed to bring the concepts to life and challenge participants to deepen their skills;
Discussion of advanced topics such organizational culture and governance as well as industry-specific concepts such as using Lean Startup in heavily regulated markets.
Thanks to Lean Startup Co.’s law firm, Orrick, for being the sponsor for this track.
Building Delightful Products: A Customer-Centric Approach to Product Strategy...
In this presentation, Carbonite's User Experience Director, Christine Perfetti, will share proven techniques for quickly exploring new design approaches based on solid customer data. She will share approaches for gathering customer insights, generating new product concepts, and evaluating designs.
Code review
This document discusses how to improve software quality through code reviews. It begins by stating the goals of code review, such as improving code quality, sharing knowledge, and educating developers. It then discusses classification of code reviews from less to more formal. The document outlines some best practices for code reviews, including having a reviewer and author, choosing reviewers strategically, and driving the review in different ways. It provides answers to common questions about organizing effective code reviews and leaves with tips, such as tracking reviewers, using checklists, and ensuring comfortable conditions for all.
Tackling the Fallacy of Agile
The document discusses agile fluency and its stages of development for teams. It describes the four stages of agile fluency - one-star, two-star, three-star, and four-star - and the benefits, investments, metrics, and time needed to achieve each stage. One-star focuses on team success and business value. Two-star is about delivering working software frequently. Three-star optimizes for delivering the most business value. Four-star aligns the team with organizational goals. The path through these stages of agile fluency allows teams to continuously improve.
Speed design studio version4.6
Speed Design Studio is a variant of Will Evan’s Design Studio Process and was designed collaboratively by Jabe Bloom and Will Evan’s at TLCLabs
Speed Design Studio was modified from the original based on insights from Cognitive Edge methods and is focused on extremely rapid iterations in an attempt to emerge team level understandings of design problems and solution language.
Due to efforts applied to tighten cycle times, Speed Design Studio can be taught in a 1-2 hr workshop.
Similar to Testers developers think differently (20)
Agile Development MethodologiesThree CommunitiesProjec.docx
Agile Development MethodologiesThree CommunitiesProjec.docx
Executable Specifications with FitNesse and Selenium
Executable Specifications with FitNesse and Selenium
Building Delightful Products: A Customer-Centric Approach to Product Strategy...
Building Delightful Products: A Customer-Centric Approach to Product Strategy...
Recently uploaded
Jemison, MacLaughlin, and Majumder "Broadening Pathways for Editors and Authors"
Jemison, MacLaughlin, and Majumder "Broadening Pathways for Editors and Authors"National Information Standards Organization (NISO)
This presentation was provided by Racquel Jemison, Ph.D., Christina MacLaughlin, Ph.D., and Paulomi Majumder. Ph.D., all of the American Chemical Society, for the second session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session Two: 'Expanding Pathways to Publishing Careers,' was held June 13, 2024.Temple of Asclepius in Thrace. Excavation results
The temple and the sanctuary around were dedicated to Asklepios Zmidrenus. This name has been known since 1875 when an inscription dedicated to him was discovered in Rome. The inscription is dated in 227 AD and was left by soldiers originating from the city of Philippopolis (modern Plovdiv).
Wound healing PPT
This document provides an overview of wound healing, its functions, stages, mechanisms, factors affecting it, and complications.
A wound is a break in the integrity of the skin or tissues, which may be associated with disruption of the structure and function.
Healing is the body’s response to injury in an attempt to restore normal structure and functions.
Healing can occur in two ways: Regeneration and Repair
There are 4 phases of wound healing: hemostasis, inflammation, proliferation, and remodeling. This document also describes the mechanism of wound healing. Factors that affect healing include infection, uncontrolled diabetes, poor nutrition, age, anemia, the presence of foreign bodies, etc.
Complications of wound healing like infection, hyperpigmentation of scar, contractures, and keloid formation.
Gender and Mental Health - Counselling and Family Therapy Applications and In...
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
Leveraging Generative AI to Drive Nonprofit Innovation
In this webinar, participants learned how to utilize Generative AI to streamline operations and elevate member engagement. Amazon Web Service experts provided a customer specific use cases and dived into low/no-code tools that are quick and easy to deploy through Amazon Web Service (AWS.)
BÀI TẬP BỔ TRỢ TIẾNG ANH LỚP 9 CẢ NĂM - GLOBAL SUCCESS - NĂM HỌC 2024-2025 - ...
BÀI TẬP BỔ TRỢ TIẾNG ANH LỚP 9 CẢ NĂM - GLOBAL SUCCESS - NĂM HỌC 2024-2025 - ...Nguyen Thanh Tu Collection
https://app.box.com/s/tacvl9ekroe9hqupdnjruiypvm9rdaneBeyond Degrees - Empowering the Workforce in the Context of Skills-First.pptx
Iván Bornacelly, Policy Analyst at the OECD Centre for Skills, OECD, presents at the webinar 'Tackling job market gaps with a skills-first approach' on 12 June 2024
skeleton System.pdf (skeleton system wow)
🔥🔥🔥🔥🔥🔥🔥🔥🔥
إضغ بين إيديكم من أقوى الملازم التي صممتها
ملزمة تشريح الجهاز الهيكلي (نظري 3)
💀💀💀💀💀💀💀💀💀💀
تتميز هذهِ الملزمة بعِدة مُميزات :
1- مُترجمة ترجمة تُناسب جميع المستويات
2- تحتوي على 78 رسم توضيحي لكل كلمة موجودة بالملزمة (لكل كلمة !!!!)
#فهم_ماكو_درخ
3- دقة الكتابة والصور عالية جداً جداً جداً
4- هُنالك بعض المعلومات تم توضيحها بشكل تفصيلي جداً (تُعتبر لدى الطالب أو الطالبة بإنها معلومات مُبهمة ومع ذلك تم توضيح هذهِ المعلومات المُبهمة بشكل تفصيلي جداً
5- الملزمة تشرح نفسها ب نفسها بس تكلك تعال اقراني
6- تحتوي الملزمة في اول سلايد على خارطة تتضمن جميع تفرُعات معلومات الجهاز الهيكلي المذكورة في هذهِ الملزمة
واخيراً هذهِ الملزمة حلالٌ عليكم وإتمنى منكم إن تدعولي بالخير والصحة والعافية فقط
كل التوفيق زملائي وزميلاتي ، زميلكم محمد الذهبي 💊💊
🔥🔥🔥🔥🔥🔥🔥🔥🔥
Pengantar Penggunaan Flutter - Dart programming language1.pptx
Pengantar Penggunaan Flutter - Dart programming language1.pptx
مصحف القراءات العشر أعد أحرف الخلاف سمير بسيوني.pdf
مصحف أحرف الخلاف للقراء العشرةأعد أحرف الخلاف بالتلوين وصلا سمير بسيوني غفر الله له
Level 3 NCEA - NZ: A Nation In the Making 1872 - 1900 SML.ppt
The History of NZ 1870-1900.
Making of a Nation.
From the NZ Wars to Liberals,
Richard Seddon, George Grey,
Social Laboratory, New Zealand,
Confiscations, Kotahitanga, Kingitanga, Parliament, Suffrage, Repudiation, Economic Change, Agriculture, Gold Mining, Timber, Flax, Sheep, Dairying,
Mule event processing models | MuleSoft Mysore Meetup #47
Mule event processing models | MuleSoft Mysore Meetup #47
Event Link:- https://meetups.mulesoft.com/events/details/mulesoft-mysore-presents-mule-event-processing-models/
Agenda
● What is event processing in MuleSoft?
● Types of event processing models in Mule 4
● Distinction between the reactive, parallel, blocking & non-blocking processing
For Upcoming Meetups Join Mysore Meetup Group - https://meetups.mulesoft.com/mysore/YouTube:- youtube.com/@mulesoftmysore
Mysore WhatsApp group:- https://chat.whatsapp.com/EhqtHtCC75vCAX7gaO842N
Speaker:-
Shivani Yasaswi - https://www.linkedin.com/in/shivaniyasaswi/
Organizers:-
Shubham Chaurasia - https://www.linkedin.com/in/shubhamchaurasia1/
Giridhar Meka - https://www.linkedin.com/in/giridharmeka
Priya Shaw - https://www.linkedin.com/in/priya-shaw
Andreas Schleicher presents PISA 2022 Volume III - Creative Thinking - 18 Jun...
Andreas Schleicher, Director of Education and Skills at the OECD presents at the launch of PISA 2022 Volume III - Creative Minds, Creative Schools on 18 June 2024.
Recently uploaded (20)
Jemison, MacLaughlin, and Majumder "Broadening Pathways for Editors and Authors"
Jemison, MacLaughlin, and Majumder "Broadening Pathways for Editors and Authors"
Gender and Mental Health - Counselling and Family Therapy Applications and In...
Gender and Mental Health - Counselling and Family Therapy Applications and In...
Leveraging Generative AI to Drive Nonprofit Innovation
Leveraging Generative AI to Drive Nonprofit Innovation
BÀI TẬP BỔ TRỢ TIẾNG ANH LỚP 9 CẢ NĂM - GLOBAL SUCCESS - NĂM HỌC 2024-2025 - ...
BÀI TẬP BỔ TRỢ TIẾNG ANH LỚP 9 CẢ NĂM - GLOBAL SUCCESS - NĂM HỌC 2024-2025 - ...
Juneteenth Freedom Day 2024 David Douglas School District
Juneteenth Freedom Day 2024 David Douglas School District
Beyond Degrees - Empowering the Workforce in the Context of Skills-First.pptx
Beyond Degrees - Empowering the Workforce in the Context of Skills-First.pptx
Pengantar Penggunaan Flutter - Dart programming language1.pptx
Pengantar Penggunaan Flutter - Dart programming language1.pptx
مصحف القراءات العشر أعد أحرف الخلاف سمير بسيوني.pdf
مصحف القراءات العشر أعد أحرف الخلاف سمير بسيوني.pdf
Level 3 NCEA - NZ: A Nation In the Making 1872 - 1900 SML.ppt
Level 3 NCEA - NZ: A Nation In the Making 1872 - 1900 SML.ppt
Mule event processing models | MuleSoft Mysore Meetup #47
Mule event processing models | MuleSoft Mysore Meetup #47
Andreas Schleicher presents PISA 2022 Volume III - Creative Thinking - 18 Jun...
Andreas Schleicher presents PISA 2022 Volume III - Creative Thinking - 18 Jun...
Testers developers think differently
- 1. Testers and Developers think differently Kishen SimbhoedatpandayTweet: @KishenPandayMail: kishen@eskape.nl
- 2. WHO THINKS TESTING IS OVERRATED? Be honest during this session
- 3. Quality is a Team Effort
- 5. Test Driven Development
- 6. Time for refactoring
- 7. Small test phases
- 9. Automate on different levels
- 10. Testing pyramid (Mike Cohn)
- 11. PopQuiz HotShot
- 12. 1. Required skill of a Tester?
- 13. 2. Required skill of a Developer?
- 14. 3. Required skill of a Developer?
- 15. 4. Required skill of a Tester?
- 16. 5. Required skill of a Developer?
- 17. 6. Required skill of a Tester?
- 18. Testers vs. Developers Get up-to-speed quickly Domain knowledge Ignorance is important Understand user behaviour Focus on what can go wrong Focus on severity of problem Thorough understanding Knowledge of product internals Expertise is important Understand system design Focus on how it can work Focus on interest in problem GoodTesters Good Developers
- 19. Testers vs. Developers Empirical What’s observed Sceptics Tolerate tedium Comfortable with conflicts Report problems Theoretical How it’s designed Believers Automate tedium Avoid conflicts Understands problems Good Testers Good Developers
- 20. Partnership Bad attitude Good attitude
- 21. It’s not about breaking software It comes to us already broken.