Teamleader testcon 2019
•Download as PPTX, PDF•
1 like•107 views
Testers, do you find yourself still siloed even after breaking down the “walls” between development and testing? Are you in a hole of never-ending test creation and maintenance, removing you from focusing on user experience? Does ad-hoc exploratory testing still happen because your tests aren’t stable enough to test the app before it gets to production? When your team starts to adopt agile and DevOps development practices, how do you scale testing to keep up with higher release frequencies? Test automation is a big part of the solution. But beware that you’re doing it the wrong way. In this talk I will explain how to reverse the negative impacts brought about from common – but not necessarily “good” – practices around automation tooling and QA hiring practices. I will talk about what changes you need to make to win back more time to develop and implement your test strategy. I will elevate your testing strategy from “surviving” to “thriving” in DevOps.
Report
Share
Report
Share
Recommended
Way to Agile - USTH
My presentation in Agile4U (Agile for University) program of HanoiScrum in 2013.
This presentation may have some customised content for University of Science and Technology of Ha Noi.
Test Driven Development
This document discusses test-driven development (TDD) and unit testing. It defines TDD as a process that involves writing a failing test first, then implementing code to pass that test, and refactoring if needed. Key benefits of TDD and unit testing include reduced bugs, lower maintenance costs, and improved code design. The document provides guidelines for writing good unit tests and emphasizes that tests should be quick, isolated, and answer what behavior was tested and what the expected and actual results were.
Алексей Денисюк "When Agile doesn't work. Tips and Tricks"
This document discusses challenges that can arise when implementing Agile methodology and provides potential solutions. It addresses three main challenges: 1) estimating timelines and costs when using Agile, 2) ensuring the customer understands their role in the Agile process, and 3) dealing with teams that are new or changing. For each challenge, the document outlines impacts on the project and provides ideas for solutions such as abstract estimations, controlled initial sprints, and gradually implementing Agile with stable teams. The overall message is that while Agile has benefits, organizations need to thoughtfully address these challenges to fully realize its advantages.
Unit testing for project managers
This presentation gives you the evidence as to why unit testing works and a process for how to bring it your team as soon as possible. There's a reason why the growth of unit testing, and automated unit testing in particular, has exploded over the past few years. It not only improves your code, it's faster than releasing code without tests. You'll learn: What, exactly, is a unit test?; The 7 reasons why managers love unit testing; and how to change mindset and processes to start unit testing now.
Agile xp crash_course_2010_05_21
This document provides an overview of Agile and eXtreme Programming (XP), including the core values and principles of the Agile Manifesto, roles and practices in XP, and how to adopt and apply XP to projects. It discusses key aspects of XP like short iterations, user stories, frequent releases, test-driven development, refactoring, collective code ownership, and more. The goal is to give the reader a crash course in Agile and XP methodologies.
From Gatekeeper to Partner by Kelsey Shannahan
The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.
Software testing presentation
Software development is hard! A common pattern in our field is project starting with the best of intentions and halfway through problems appear. Problems that slow us down, that will cause us to loose speed and flexibility. So, what is Test Driven Development and how it gives us back control over our projects?
Test Driven Development (TDD) & Continuous Integration (CI)
Sebuah pembahasan menarik tentang Agile Software Development dengan Test Driven Development (TDD) & Continuous Integration (CI). Materi ini disusun oleh Mas Disyam
Recommended
Way to Agile - USTH
My presentation in Agile4U (Agile for University) program of HanoiScrum in 2013.
This presentation may have some customised content for University of Science and Technology of Ha Noi.
Test Driven Development
This document discusses test-driven development (TDD) and unit testing. It defines TDD as a process that involves writing a failing test first, then implementing code to pass that test, and refactoring if needed. Key benefits of TDD and unit testing include reduced bugs, lower maintenance costs, and improved code design. The document provides guidelines for writing good unit tests and emphasizes that tests should be quick, isolated, and answer what behavior was tested and what the expected and actual results were.
Алексей Денисюк "When Agile doesn't work. Tips and Tricks"
This document discusses challenges that can arise when implementing Agile methodology and provides potential solutions. It addresses three main challenges: 1) estimating timelines and costs when using Agile, 2) ensuring the customer understands their role in the Agile process, and 3) dealing with teams that are new or changing. For each challenge, the document outlines impacts on the project and provides ideas for solutions such as abstract estimations, controlled initial sprints, and gradually implementing Agile with stable teams. The overall message is that while Agile has benefits, organizations need to thoughtfully address these challenges to fully realize its advantages.
Unit testing for project managers
This presentation gives you the evidence as to why unit testing works and a process for how to bring it your team as soon as possible. There's a reason why the growth of unit testing, and automated unit testing in particular, has exploded over the past few years. It not only improves your code, it's faster than releasing code without tests. You'll learn: What, exactly, is a unit test?; The 7 reasons why managers love unit testing; and how to change mindset and processes to start unit testing now.
Agile xp crash_course_2010_05_21
This document provides an overview of Agile and eXtreme Programming (XP), including the core values and principles of the Agile Manifesto, roles and practices in XP, and how to adopt and apply XP to projects. It discusses key aspects of XP like short iterations, user stories, frequent releases, test-driven development, refactoring, collective code ownership, and more. The goal is to give the reader a crash course in Agile and XP methodologies.
From Gatekeeper to Partner by Kelsey Shannahan
The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.
Software testing presentation
Software development is hard! A common pattern in our field is project starting with the best of intentions and halfway through problems appear. Problems that slow us down, that will cause us to loose speed and flexibility. So, what is Test Driven Development and how it gives us back control over our projects?
Test Driven Development (TDD) & Continuous Integration (CI)
Sebuah pembahasan menarik tentang Agile Software Development dengan Test Driven Development (TDD) & Continuous Integration (CI). Materi ini disusun oleh Mas Disyam
Agille Testing Meetup 1
This document summarizes the agenda and discussion at an Agile Testing meetup group. It introduces the purpose of the group as a place for testers to share experiences and learn new skills in Agile Testing. Key topics discussed include the benefits of testing earlier in the development cycle using automated tools. A demonstration was given of a keyword driven web testing solution using WebDriver and FitNesse. Attendees then shared challenges with testing in Agile and ideas for future meetup activities.
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 testingandautomation
1. The document discusses lessons learned about agile testing and automation. It emphasizes that testing is more than just checking and that both automated and exploratory testing are important.
2. It recommends automating output checking where possible but also using exploratory testing. It also stresses the importance of unit, integration and end-to-end tests as well as code reviews.
3. The document advocates for test-driven development and notes how automated tests can reduce regression testing time. It emphasizes that successful testing requires collaboration between developers, testers and business stakeholders.
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.
How to be proud when you are done
Although all of us speak the same language, each of us uses different meaning of words "soon”, "fine” and "done”. That’s why for one developer "I’m done” means that just a moment ago the part of the code with implemented functionality has been successfully executed, while for another developer it means that code has been committed to repository but without checking if build is green or not on continuous integration server. At the same time "done" of developer-perfectionist means totally refactored and optimized code. And only for "black swan”-developer phrase "I'm done“ means that all tests were passed, new functionality was documented on wiki and a new feature was verified by customer on the demo server.
So if you want to decrease a risk of misunderstanding inside a team or between team and customer you should make agreement about common vision of “definition of done“ and then start using it on a daily basis. In order to prevent losing your time and stepping on the hidden rake during discussion of your done criteria we will share our knowledge about creating compact and most effective “definition of done“. We will talk about lifecycle of this document and about approaches that help you to add important items to it. We will discuss doneness on different levels (preplanning, user story and task development, sprint). And of course we won’t forget to tell you how to create “Definition of Done“ which will satisfy not only your team but your customer as well.
XP Injection
Nikolay Alimenkou and Aleksey Solntsev will show how to migrate from Ant project to Maven2 project and start using full power of XP engineering practices: CI, TDD, refactoring.
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.
Strategies for Distributed Agile Testing
Distributed organisation / projects / teams is not a new phenomenon. It is a reality. However, do we really work well in Testing on such distributed teams? Learn some practices that help bridge the Distributed Testing gap!
Adventures in Agile Testing
Manual testing is a skill set that is still needed and works well within the agile methodology. This presentation covers techniques and processes to help testers who are new to agile and help those who are fluent in agile. Learn how to make testing a priority in every project.
Continuous delivery test strategies
A high level introduction why and how to test within in a continuous delivery or continuous integration process
Tdd
Test-driven development (TDD) is a software development process that relies on the repetition of short development cycles called red-green-refactor cycles. In TDD, tests are written before code to define desired functionality, and then code is written to pass those tests; this is followed by refactoring. The benefits of TDD include producing code that is robust, well-designed, and with fewer bugs due to comprehensive test coverage. While TDD requires discipline, it helps ensure code works as intended and allows refactoring with confidence that changes don't break existing functionality. Some potential vulnerabilities of TDD are that it may not prevent wrong solutions if requirements are unclear, can be difficult for UI or database-dependent programs
Continuous business goal validation
Building the rights Right. Use the concept of continuous validation (hypothesis driven development) to prevent that your automated software development pipeline becomes a vehicle to deliver crap fast and helps you focus on the goals that software should help you achieve
Developer testing webinar
Why can't programmers test and what can you do about it?
Do your developers take part in testing tasks?
Fact! [Most] developers are not good testers.
So how can we help then out?
Full webinar recording here:
https://www.practitest.com/qa-learningcenter/webinars/developer-testing-webinar/
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
Effective QA in Scrum
This document discusses how testers can be effective in agile teams using Scrum. It begins by distinguishing quality assurance (QA) from quality control (QC) and outlines how testers can focus on helping teams achieve "done" by collaborating in backlog grooming and preventing bugs. The document recommends that testers work with rather than against developers by pairing, writing automated tests, and participating in code reviews. It also advocates for exploratory testing and emphasizes the importance of collaboration between testers, developers, analysts and product owners.
Stc chandan patary_ua_testing _ stc
This document discusses ways to improve product development cycles through effective user acceptance testing and engagement. It describes how one organization achieved targets like reducing production to release cycles from 15 to 10 months by having product owners actively participate in validation testing. Stories from the trenches are shared about having product engineers directly involved in validation testing to better represent customer needs. Exploratory "monkey" testing of system boundaries is also discussed. The key takeaway is how design thinking principles were applied, like creating focus groups, prototyping solutions, and getting faster customer feedback through various iterative testing approaches.
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.
Notes On Agile Development
These are some tips that I learned over the years and was able to put into practice while working with the fantastic Ubuntu One team at Canonical.
Hey You Got Your TDD in my SQL DB by Jeff McKenzie
TDD involves writing tests before writing code to satisfy requirements. The document discusses TDD, providing:
1. An overview of the TDD process and definitions of its key steps - make a test, make it fail, make it pass.
2. An example walking through writing a test for an "easy button" and implementing the code to pass the test.
3. Reasons for using TDD, including improved code quality, design, discipline, and documentation from maintaining an automated test suite.
Gearing Startups for Success through Product Engineering
In the August edition of the #99XTWebinar Series, catch two of 99X Technology’s tech experts as they share some intuitive insights into product engineering for startups, and how they harnessed digital transformation to successfully launch a product.
Agile testing
Despite the belief that a shared context and collaboration drives quality, too often, software testers and quality professionals struggle to find their place within today's integrated agile teams. This session is a practitioner’s view of testing and testing practices within an iterative/incremental development environment. We will begin with a discussion of some of the challenges of testing within an agile environment and delve into the guiding principles of Agile Testing and key enabling practices. Agile Testing necessitates a change in mindset, and it is as much, if not more, about behavior, as it is about skills and tooling, all of which will be explored.
Test team dynamics, Антон Мужайло
The document discusses building an effective test team. It recommends hiring people with a mix of hard and soft skills at different experience levels who share common goals and are willing to teach and learn from each other. Soft skills like learning, sharing knowledge, explaining viewpoints, negotiating, and handling conflicts are emphasized as being more important than hard skills. The document provides examples of how to define needed hard skills and evaluate candidates based on their skills and experience levels. It also shows an example skills assessment of potential candidates for both manual and automation testing roles.
More Related Content
What's hot
Agille Testing Meetup 1
This document summarizes the agenda and discussion at an Agile Testing meetup group. It introduces the purpose of the group as a place for testers to share experiences and learn new skills in Agile Testing. Key topics discussed include the benefits of testing earlier in the development cycle using automated tools. A demonstration was given of a keyword driven web testing solution using WebDriver and FitNesse. Attendees then shared challenges with testing in Agile and ideas for future meetup activities.
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 testingandautomation
1. The document discusses lessons learned about agile testing and automation. It emphasizes that testing is more than just checking and that both automated and exploratory testing are important.
2. It recommends automating output checking where possible but also using exploratory testing. It also stresses the importance of unit, integration and end-to-end tests as well as code reviews.
3. The document advocates for test-driven development and notes how automated tests can reduce regression testing time. It emphasizes that successful testing requires collaboration between developers, testers and business stakeholders.
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.
How to be proud when you are done
Although all of us speak the same language, each of us uses different meaning of words "soon”, "fine” and "done”. That’s why for one developer "I’m done” means that just a moment ago the part of the code with implemented functionality has been successfully executed, while for another developer it means that code has been committed to repository but without checking if build is green or not on continuous integration server. At the same time "done" of developer-perfectionist means totally refactored and optimized code. And only for "black swan”-developer phrase "I'm done“ means that all tests were passed, new functionality was documented on wiki and a new feature was verified by customer on the demo server.
So if you want to decrease a risk of misunderstanding inside a team or between team and customer you should make agreement about common vision of “definition of done“ and then start using it on a daily basis. In order to prevent losing your time and stepping on the hidden rake during discussion of your done criteria we will share our knowledge about creating compact and most effective “definition of done“. We will talk about lifecycle of this document and about approaches that help you to add important items to it. We will discuss doneness on different levels (preplanning, user story and task development, sprint). And of course we won’t forget to tell you how to create “Definition of Done“ which will satisfy not only your team but your customer as well.
XP Injection
Nikolay Alimenkou and Aleksey Solntsev will show how to migrate from Ant project to Maven2 project and start using full power of XP engineering practices: CI, TDD, refactoring.
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.
Strategies for Distributed Agile Testing
Distributed organisation / projects / teams is not a new phenomenon. It is a reality. However, do we really work well in Testing on such distributed teams? Learn some practices that help bridge the Distributed Testing gap!
Adventures in Agile Testing
Manual testing is a skill set that is still needed and works well within the agile methodology. This presentation covers techniques and processes to help testers who are new to agile and help those who are fluent in agile. Learn how to make testing a priority in every project.
Continuous delivery test strategies
A high level introduction why and how to test within in a continuous delivery or continuous integration process
Tdd
Test-driven development (TDD) is a software development process that relies on the repetition of short development cycles called red-green-refactor cycles. In TDD, tests are written before code to define desired functionality, and then code is written to pass those tests; this is followed by refactoring. The benefits of TDD include producing code that is robust, well-designed, and with fewer bugs due to comprehensive test coverage. While TDD requires discipline, it helps ensure code works as intended and allows refactoring with confidence that changes don't break existing functionality. Some potential vulnerabilities of TDD are that it may not prevent wrong solutions if requirements are unclear, can be difficult for UI or database-dependent programs
Continuous business goal validation
Building the rights Right. Use the concept of continuous validation (hypothesis driven development) to prevent that your automated software development pipeline becomes a vehicle to deliver crap fast and helps you focus on the goals that software should help you achieve
Developer testing webinar
Why can't programmers test and what can you do about it?
Do your developers take part in testing tasks?
Fact! [Most] developers are not good testers.
So how can we help then out?
Full webinar recording here:
https://www.practitest.com/qa-learningcenter/webinars/developer-testing-webinar/
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
Effective QA in Scrum
This document discusses how testers can be effective in agile teams using Scrum. It begins by distinguishing quality assurance (QA) from quality control (QC) and outlines how testers can focus on helping teams achieve "done" by collaborating in backlog grooming and preventing bugs. The document recommends that testers work with rather than against developers by pairing, writing automated tests, and participating in code reviews. It also advocates for exploratory testing and emphasizes the importance of collaboration between testers, developers, analysts and product owners.
Stc chandan patary_ua_testing _ stc
This document discusses ways to improve product development cycles through effective user acceptance testing and engagement. It describes how one organization achieved targets like reducing production to release cycles from 15 to 10 months by having product owners actively participate in validation testing. Stories from the trenches are shared about having product engineers directly involved in validation testing to better represent customer needs. Exploratory "monkey" testing of system boundaries is also discussed. The key takeaway is how design thinking principles were applied, like creating focus groups, prototyping solutions, and getting faster customer feedback through various iterative testing approaches.
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.
Notes On Agile Development
These are some tips that I learned over the years and was able to put into practice while working with the fantastic Ubuntu One team at Canonical.
Hey You Got Your TDD in my SQL DB by Jeff McKenzie
TDD involves writing tests before writing code to satisfy requirements. The document discusses TDD, providing:
1. An overview of the TDD process and definitions of its key steps - make a test, make it fail, make it pass.
2. An example walking through writing a test for an "easy button" and implementing the code to pass the test.
3. Reasons for using TDD, including improved code quality, design, discipline, and documentation from maintaining an automated test suite.
Gearing Startups for Success through Product Engineering
In the August edition of the #99XTWebinar Series, catch two of 99X Technology’s tech experts as they share some intuitive insights into product engineering for startups, and how they harnessed digital transformation to successfully launch a product.
What's hot (20)
Test Strategy-The real silver bullet in testing by Matthew Eakin
Test Strategy-The real silver bullet in testing by Matthew Eakin
Hey You Got Your TDD in my SQL DB by Jeff McKenzie
Hey You Got Your TDD in my SQL DB by Jeff McKenzie
Gearing Startups for Success through Product Engineering
Gearing Startups for Success through Product Engineering
Similar to Teamleader testcon 2019
Agile testing
Despite the belief that a shared context and collaboration drives quality, too often, software testers and quality professionals struggle to find their place within today's integrated agile teams. This session is a practitioner’s view of testing and testing practices within an iterative/incremental development environment. We will begin with a discussion of some of the challenges of testing within an agile environment and delve into the guiding principles of Agile Testing and key enabling practices. Agile Testing necessitates a change in mindset, and it is as much, if not more, about behavior, as it is about skills and tooling, all of which will be explored.
Test team dynamics, Антон Мужайло
The document discusses building an effective test team. It recommends hiring people with a mix of hard and soft skills at different experience levels who share common goals and are willing to teach and learn from each other. Soft skills like learning, sharing knowledge, explaining viewpoints, negotiating, and handling conflicts are emphasized as being more important than hard skills. The document provides examples of how to define needed hard skills and evaluate candidates based on their skills and experience levels. It also shows an example skills assessment of potential candidates for both manual and automation testing roles.
The Holy Trinity of UI Testing by Diego Molina
The first step before testing is defining what we want to test. This may sound trivial, but in reality this not done often properly. We tend to oversee the obvious and we start testing without knowing what we want to accomplish. Do we want to validate the user behavior? Do we need to check that the page design is responsive on different devices? Knowing what is important and what needs to be validated can help us enormously to have a clear purpose.
When we know the purpose of our test, we can start planning, coding, executing and improving our tests. But overall, we will know what approach we can use to develop the test. Functional, layout and visual testing are the three pillars of the UI testing trinity. These are three approaches we can use to develop focused tests, tests that are asserting a specific aspect of a web application.
But how can we identify what approach to use? When should we combine them? This SauceCon 2018 session will help attendees to define what they want to test and what approach to use when developing the test. It will go deeper through scenarios and code examples that show how to create tests with great assertions and clear purpose, tests that give value to the team. It will also discuss scenarios where a functional test is not enough, or where a visual test is better than a layout test. This talk’s main goal is to offer a different perspective when testing a web application through the UI testing trinity.
Essential practices and thinking tools for Agile Adoption
Steven Mak presented tools and practices for adopting Agile, including:
- Thinking tools like systems thinking and lean thinking can help with adoption.
- Organizational practices like self-managing cross-functional teams and continuous improvement are important.
- Engineering practices like test-driven development, refactoring, and continuous integration can reduce technical debt.
- Adoption requires changing mindsets and habits through training, coaching, and leading by example.
Product quality in agile project
The document discusses product quality in agile projects. It covers traditional vs agile testing approaches, the four quadrants of agile testing (test-driven development, data-driven development, exploratory testing, and non-functional testing), the importance of automation in agile testing, and key success factors. It also discusses quality factors, the quality triangle in agile projects, and common problems that can occur in agile projects like defects and lack of testing if not properly managed.
Automation testing in Agile project
The document summarizes best practices for test automation, including:
- Unit tests should be automated as the first step and follow naming conventions.
- Integration and performance tests require grouping, isolation, and handling test data issues.
- UI tests can be automated with Selenium and integrated into the build pipeline.
- Automated test data, code, and plan generation may be useful once a project's structure stabilizes.
- Automation aims to provide transparency, improve skills, and reduce manual work over time through a smarter approach.
Mastering Agile Practices to Build High Performing Teams
These slides are from a talk that I gave to the Tampa Bay Agile Meetup on August 19, 2014. The talk was titled "Mastering Agile Practices to Build High Performing Teams". http://www.meetup.com/tampa-bay-agile/events/193898502/
Description:
You've read the books. You already know what your Agile team SHOULD be doing. Your Daily Standup meeting should be short and sweet. Your deployments should be automated. Your Sprint Retrospectives should inspire improvement.
So if you know what to do, why aren't you doing it?
The short answer is because Agile is hard. It takes real discipline and leadership to master even the most basic practices. Many teams have committed to adopting Agile, but they just don’t know how to get to the next level.
In this talk, I will share my real world experiences from years of coaching high performing Agile teams. I will discuss the key practices that must be mastered for a team to become great. Additionally, I will identify useful measurement techniques so that teams know if they are improving.
Demise of test scripts rise of test ideas
Tired of doing upfront test script creation in your testing efforts? Feeling bad for demotivating your testers? Want something to replace this sickening approach to software testing? This presentation outlines why test scripts are not useful, and how test ideas are the new way forward to better testing. Coverage, traceability, reporting, automation and skills are all covered. Take a quick look and see if you can see there is another way to do software testing that is actually pure common sense.
Resume_Testing_Sanjeev_latest
Sanjeev Kumar Jha has over 9 years of experience as a software tester, including 6 years of manual testing experience and 3 years of automation testing experience using Selenium WebDriver with Java. He has 3 years of experience as a Test Lead managing a team of 10 members. Some of his responsibilities include creating test plans, test strategies, test scenarios, and traceability matrices. He has worked on several insurance domain projects involving manual testing, functional testing, regression testing, and more.
Purushothama_Resume
Purushothama D is seeking a position in quality assurance where he can utilize 5 years of experience as a software testing professional at TATA Consultancy Services. He has skills in programming languages like Java, SQL, and scripting languages like VBScript. He has experience with manual and automation testing using tools like QTP, UFT, and Selenium. Notable projects include regression testing of web applications for The Home Depot, and testing a warehouse management system for Sainsbury's Supermarket including designing automated test frameworks. He was awarded certificates of achievement for his work and received "On the Spot" awards twice for his performance.
Testaus 2014: Paul Gerrard - The Changing Role of Testers'
Testausala on suuressa murroksessa. Muutos heijastuu testaajien työhön siten, että testaajan tulee miettiä entistä luovemmin suhtautumistaan omaan työhönsä. Sen sijaan että kehittäjät ja testaajat rajoittavat työskentelynsä yhteen tuotantotapaan, kuten vaikkapa yhteen tiettyyn Agile-viitekehykseen, heidän tulee itse osoittaa ketteryyttä valitsemalla ja yhdistelemällä luovasti erilaisia tuotantotapoja tilanteen vaatimalla tavalla.
Testaus 2014 -seminaari: Paul Gerrard. The Changing Role of Testers’.
Testausala on suuressa murroksessa. Sen sijaan että kehittäjät ja testaajat käyttävät kaikissa tilanteissa tiettyä tuotantotapaa, kuten vaikkapa Agilea, tulee ammattilaisen itse osoittaa ketteryyttä valitsemalla ja yhdistelemällä luovasti erilaisia tuotantotapoja tilanteen mukaan.
Fundamentals of Agile
The document discusses fundamentals of agile development including the agile manifesto and its 12 principles. It emphasizes values such as individuals and interactions, working software, customer collaboration, and responding to change. It also discusses agile processes like Scrum and Kanban, continuous improvement through inspection and adaptation, and techniques like test-driven development, pair programming, and continuous integration to enable regular rapid feedback. Finally, it notes that while agile is popular, the real question is whether it will make teams more successful in delivering value to customers on time and under budget.
Agile testing practice
The document provides an overview of agile testing principles and practices. It discusses that agile testing involves the entire cross-functional team working together to test software iteratively. Key aspects of agile testing covered include continuous feedback, delivering value to customers, enabling face-to-face communication, and keeping testing simple. The document also outlines typical testing activities in an agile project such as test planning, driving development, facilitating communication, and completing testing tasks within each sprint.
Resume_Testing_Sanjeev
Sanjeev Kumar Jha has over 8 years of experience as a software tester, including 6 years of manual testing experience and 2 years of automation testing experience using Selenium WebDriver with Java. He has worked as a Test Lead and Consultant on several projects in the insurance domain for clients like Capgemini and 3i Infotech. Some of his responsibilities have included test planning, test case design, automation framework development, defect tracking, and managing a team of 10 testers. He has expertise in various test techniques including functional testing, regression testing, and smoke testing.
Resume_Testing_Sanjeev
Sanjeev Kumar Jha has over 8 years of experience as a software tester, including 6 years of manual testing experience and 2 years of automation testing experience using Selenium WebDriver with Java. He has worked as a Test Lead and Consultant on several projects in the insurance domain for clients like Capgemini and 3i Infotech. Some of his responsibilities have included test planning, test case design, automation framework development, defect tracking, and managing a team of 10 testers. He has expertise in various test techniques including functional testing, regression testing, and smoke testing.
Scrum plus – why scrum is not enough for successful delivery
Why, where and how to include engineering practices in Scrum to maximize value of work done by development in Sprint.
Quality Jam: BDD, TDD and ATDD for the Enterprise
During Quality Jam 2016 I had the privilege of presenting with one of QASymphony's earliest customers, Better Cloud, on how methodologies like BDD, TDD and ATDD scale for the enterprises. Adam Satterfield is the VP of Quality Assurance at Bettercloud and has been in QA for many years; he has taught me a lot about Behavior Driven Development, Test Driven Development, Acceptance Test Driven Development. In the session we share a new way of testing-- what Adam and I believe to be the next generation of testing development.
We know that there are several ways to do testing and we are just showing one new way to do it - If this session doesn't inspire action, hopefully it will at least give you and your team something to think about.
What is agile
This document provides an introduction and overview of Agile software development. It discusses that Agile is a family of lightweight methodologies that advocate for human-centric development processes. The key aspects of Agile covered are the Agile Manifesto, values like communication and feedback, and practices like short iterations, test-driven development, planning, tracking progress, and maintaining a sustainable pace. It also discusses how Orange & Bronze has adopted Agile since 2005 and offers internal Agile training.
Software testing 2012 - A Year in Review
The document summarizes software testing trends in 2012. Key points include: Google introduced "Testing 2.0" which focuses on risk assessment and reducing probabilities of bugs; good test automation requires caring about results and addressing failed tests; context-driven testing emphasizes a risk-based approach and looking at multiple contexts rather than one school of thought; mindless automation and scripted manual regression testing are not effective at finding bugs; and customer involvement is important for testing in agile projects.
Similar to Teamleader testcon 2019 (20)
Essential practices and thinking tools for Agile Adoption
Essential practices and thinking tools for Agile Adoption
Mastering Agile Practices to Build High Performing Teams
Mastering Agile Practices to Build High Performing Teams
Testaus 2014: Paul Gerrard - The Changing Role of Testers'
Testaus 2014: Paul Gerrard - The Changing Role of Testers'
Testaus 2014 -seminaari: Paul Gerrard. The Changing Role of Testers’.
Testaus 2014 -seminaari: Paul Gerrard. The Changing Role of Testers’.
Scrum plus – why scrum is not enough for successful delivery
Scrum plus – why scrum is not enough for successful delivery
Recently uploaded
Literature Review Basics and Understanding Reference Management.pptx
Three-day training on academic research focuses on analytical tools at United Technical College, supported by the University Grant Commission, Nepal. 24-26 May 2024
ACEP Magazine edition 4th launched on 05.06.2024
This document provides information about the third edition of the magazine "Sthapatya" published by the Association of Civil Engineers (Practicing) Aurangabad. It includes messages from current and past presidents of ACEP, memories and photos from past ACEP events, information on life time achievement awards given by ACEP, and a technical article on concrete maintenance, repairs and strengthening. The document highlights activities of ACEP and provides a technical educational article for members.
Recycled Concrete Aggregate in Construction Part III
Using recycled concrete aggregates (RCA) for pavements is crucial to achieving sustainability. Implementing RCA for new pavement can minimize carbon footprint, conserve natural resources, reduce harmful emissions, and lower life cycle costs. Compared to natural aggregate (NA), RCA pavement has fewer comprehensive studies and sustainability assessments.
The Python for beginners. This is an advance computer language.
Python language is very important language at this time. we can easily understand this language by these notes.
Presentation of IEEE Slovenia CIS (Computational Intelligence Society) Chapte...
Presentation of IEEE Slovenia CIS (Computational Intelligence Society) Chapte...University of Maribor
Slides from talk presenting:
Aleš Zamuda: Presentation of IEEE Slovenia CIS (Computational Intelligence Society) Chapter and Networking.
Presentation at IcETRAN 2024 session:
"Inter-Society Networking Panel GRSS/MTT-S/CIS
Panel Session: Promoting Connection and Cooperation"
IEEE Slovenia GRSS
IEEE Serbia and Montenegro MTT-S
IEEE Slovenia CIS
11TH INTERNATIONAL CONFERENCE ON ELECTRICAL, ELECTRONIC AND COMPUTING ENGINEERING
3-6 June 2024, Niš, SerbiaA SYSTEMATIC RISK ASSESSMENT APPROACH FOR SECURING THE SMART IRRIGATION SYSTEMS
The smart irrigation system represents an innovative approach to optimize water usage in agricultural and landscaping practices. The integration of cutting-edge technologies, including sensors, actuators, and data analysis, empowers this system to provide accurate monitoring and control of irrigation processes by leveraging real-time environmental conditions. The main objective of a smart irrigation system is to optimize water efficiency, minimize expenses, and foster the adoption of sustainable water management methods. This paper conducts a systematic risk assessment by exploring the key components/assets and their functionalities in the smart irrigation system. The crucial role of sensors in gathering data on soil moisture, weather patterns, and plant well-being is emphasized in this system. These sensors enable intelligent decision-making in irrigation scheduling and water distribution, leading to enhanced water efficiency and sustainable water management practices. Actuators enable automated control of irrigation devices, ensuring precise and targeted water delivery to plants. Additionally, the paper addresses the potential threat and vulnerabilities associated with smart irrigation systems. It discusses limitations of the system, such as power constraints and computational capabilities, and calculates the potential security risks. The paper suggests possible risk treatment methods for effective secure system operation. In conclusion, the paper emphasizes the significant benefits of implementing smart irrigation systems, including improved water conservation, increased crop yield, and reduced environmental impact. Additionally, based on the security analysis conducted, the paper recommends the implementation of countermeasures and security approaches to address vulnerabilities and ensure the integrity and reliability of the system. By incorporating these measures, smart irrigation technology can revolutionize water management practices in agriculture, promoting sustainability, resource efficiency, and safeguarding against potential security threats.
Eric Nizeyimana's document 2006 from gicumbi to ttc nyamata handball play
this notes have been created
by Eric36 at nyamata ttc
after readings
pe book for y2sme .
Embedded machine learning-based road conditions and driving behavior monitoring
Car accident rates have increased in recent years, resulting in losses in human lives, properties, and other financial costs. An embedded machine learning-based system is developed to address this critical issue. The system can monitor road conditions, detect driving patterns, and identify aggressive driving behaviors. The system is based on neural networks trained on a comprehensive dataset of driving events, driving styles, and road conditions. The system effectively detects potential risks and helps mitigate the frequency and impact of accidents. The primary goal is to ensure the safety of drivers and vehicles. Collecting data involved gathering information on three key road events: normal street and normal drive, speed bumps, circular yellow speed bumps, and three aggressive driving actions: sudden start, sudden stop, and sudden entry. The gathered data is processed and analyzed using a machine learning system designed for limited power and memory devices. The developed system resulted in 91.9% accuracy, 93.6% precision, and 92% recall. The achieved inference time on an Arduino Nano 33 BLE Sense with a 32-bit CPU running at 64 MHz is 34 ms and requires 2.6 kB peak RAM and 139.9 kB program flash memory, making it suitable for resource-constrained embedded systems.
TIME DIVISION MULTIPLEXING TECHNIQUE FOR COMMUNICATION SYSTEM
Time Division Multiplexing (TDM) is a method of transmitting multiple signals over a single communication channel by dividing the signal into many segments, each having a very short duration of time. These time slots are then allocated to different data streams, allowing multiple signals to share the same transmission medium efficiently. TDM is widely used in telecommunications and data communication systems.
### How TDM Works
1. **Time Slots Allocation**: The core principle of TDM is to assign distinct time slots to each signal. During each time slot, the respective signal is transmitted, and then the process repeats cyclically. For example, if there are four signals to be transmitted, the TDM cycle will divide time into four slots, each assigned to one signal.
2. **Synchronization**: Synchronization is crucial in TDM systems to ensure that the signals are correctly aligned with their respective time slots. Both the transmitter and receiver must be synchronized to avoid any overlap or loss of data. This synchronization is typically maintained by a clock signal that ensures time slots are accurately aligned.
3. **Frame Structure**: TDM data is organized into frames, where each frame consists of a set of time slots. Each frame is repeated at regular intervals, ensuring continuous transmission of data streams. The frame structure helps in managing the data streams and maintaining the synchronization between the transmitter and receiver.
4. **Multiplexer and Demultiplexer**: At the transmitting end, a multiplexer combines multiple input signals into a single composite signal by assigning each signal to a specific time slot. At the receiving end, a demultiplexer separates the composite signal back into individual signals based on their respective time slots.
### Types of TDM
1. **Synchronous TDM**: In synchronous TDM, time slots are pre-assigned to each signal, regardless of whether the signal has data to transmit or not. This can lead to inefficiencies if some time slots remain empty due to the absence of data.
2. **Asynchronous TDM (or Statistical TDM)**: Asynchronous TDM addresses the inefficiencies of synchronous TDM by allocating time slots dynamically based on the presence of data. Time slots are assigned only when there is data to transmit, which optimizes the use of the communication channel.
### Applications of TDM
- **Telecommunications**: TDM is extensively used in telecommunication systems, such as in T1 and E1 lines, where multiple telephone calls are transmitted over a single line by assigning each call to a specific time slot.
- **Digital Audio and Video Broadcasting**: TDM is used in broadcasting systems to transmit multiple audio or video streams over a single channel, ensuring efficient use of bandwidth.
- **Computer Networks**: TDM is used in network protocols and systems to manage the transmission of data from multiple sources over a single network medium.
### Advantages of TDM
- **Efficient Use of Bandwidth**: TDM all
Iron and Steel Technology Roadmap - Towards more sustainable steelmaking.pdf
Iron and Steel Technology towards Sustainable Steelmaking
5214-1693458878915-Unit 6 2023 to 2024 academic year assignment (AutoRecovere...
Bigdata of technology
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODEL
As digital technology becomes more deeply embedded in power systems, protecting the communication
networks of Smart Grids (SG) has emerged as a critical concern. Distributed Network Protocol 3 (DNP3)
represents a multi-tiered application layer protocol extensively utilized in Supervisory Control and Data
Acquisition (SCADA)-based smart grids to facilitate real-time data gathering and control functionalities.
Robust Intrusion Detection Systems (IDS) are necessary for early threat detection and mitigation because
of the interconnection of these networks, which makes them vulnerable to a variety of cyberattacks. To
solve this issue, this paper develops a hybrid Deep Learning (DL) model specifically designed for intrusion
detection in smart grids. The proposed approach is a combination of the Convolutional Neural Network
(CNN) and the Long-Short-Term Memory algorithms (LSTM). We employed a recent intrusion detection
dataset (DNP3), which focuses on unauthorized commands and Denial of Service (DoS) cyberattacks, to
train and test our model. The results of our experiments show that our CNN-LSTM method is much better
at finding smart grid intrusions than other deep learning algorithms used for classification. In addition,
our proposed approach improves accuracy, precision, recall, and F1 score, achieving a high detection
accuracy rate of 99.50%.
官方认证美国密歇根州立大学毕业证学位证书原版一模一样
原版一模一样【微信：741003700 】【美国密歇根州立大学毕业证学位证书】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
A review on techniques and modelling methodologies used for checking electrom...
The proper function of the integrated circuit (IC) in an inhibiting electromagnetic environment has always been a serious concern throughout the decades of revolution in the world of electronics, from disjunct devices to today’s integrated circuit technology, where billions of transistors are combined on a single chip. The automotive industry and smart vehicles in particular, are confronting design issues such as being prone to electromagnetic interference (EMI). Electronic control devices calculate incorrect outputs because of EMI and sensors give misleading values which can prove fatal in case of automotives. In this paper, the authors have non exhaustively tried to review research work concerned with the investigation of EMI in ICs and prediction of this EMI using various modelling methodologies and measurement setups.
哪里办理(csu毕业证书)查尔斯特大学毕业证硕士学历原版一模一样
原版一模一样【微信：741003700 】【(csu毕业证书)查尔斯特大学毕业证硕士学历】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
Recently uploaded (20)
Literature Review Basics and Understanding Reference Management.pptx
Literature Review Basics and Understanding Reference Management.pptx
Manufacturing Process of molasses based distillery ppt.pptx
Manufacturing Process of molasses based distillery ppt.pptx
Recycled Concrete Aggregate in Construction Part III
Recycled Concrete Aggregate in Construction Part III
The Python for beginners. This is an advance computer language.
The Python for beginners. This is an advance computer language.
Presentation of IEEE Slovenia CIS (Computational Intelligence Society) Chapte...
Presentation of IEEE Slovenia CIS (Computational Intelligence Society) Chapte...
A SYSTEMATIC RISK ASSESSMENT APPROACH FOR SECURING THE SMART IRRIGATION SYSTEMS
A SYSTEMATIC RISK ASSESSMENT APPROACH FOR SECURING THE SMART IRRIGATION SYSTEMS
Eric Nizeyimana's document 2006 from gicumbi to ttc nyamata handball play
Eric Nizeyimana's document 2006 from gicumbi to ttc nyamata handball play
Embedded machine learning-based road conditions and driving behavior monitoring
Embedded machine learning-based road conditions and driving behavior monitoring
TIME DIVISION MULTIPLEXING TECHNIQUE FOR COMMUNICATION SYSTEM
TIME DIVISION MULTIPLEXING TECHNIQUE FOR COMMUNICATION SYSTEM
Iron and Steel Technology Roadmap - Towards more sustainable steelmaking.pdf
Iron and Steel Technology Roadmap - Towards more sustainable steelmaking.pdf
5214-1693458878915-Unit 6 2023 to 2024 academic year assignment (AutoRecovere...
5214-1693458878915-Unit 6 2023 to 2024 academic year assignment (AutoRecovere...
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODEL
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODEL
basic-wireline-operations-course-mahmoud-f-radwan.pdf
basic-wireline-operations-course-mahmoud-f-radwan.pdf
A review on techniques and modelling methodologies used for checking electrom...
A review on techniques and modelling methodologies used for checking electrom...
Teamleader testcon 2019
- 1. Building a testing strategy that scales Thomas Noë QA Architect, TeamLeader
- 2. www.teamleader.eu ● Studies: Bio-Engineer ● +5 years QA engineer ● +5 years QA manager ● 1,5 years @Teamleader ● Twitter:@Noe_Thomas_QA ● Linkedin: thomas-noë-82337a7 Who am I
- 3. www.teamleader.eu We simplify the work for 11 000+ SME’s https://www.teamleader.eu CRM, Invoicing, Project, HR, Marketplace https://www.teamleader.eu
- 7. Small PR’s ● Easy to review ● More thorough review ● Less likely to introduce bugs ● Less wasted work if they are rejected ● Easier to merge ● Less blocking on reviews ● Easier to revert
- 8. Some others ● Scalable automated CI pipeline ● Unit and API/integration automation tests ● Small testable user stories (1-3 workday) ● Daily PR merging to master ● Test environment rebuilded by the CI pipeline
- 9. Problem 1 Test cases and test execution
- 13. 0
- 14. Testing is providing information about the product Michael Bolton
- 15. We don’t have test cases, we have acceptance criteria Thomas Noë
- 16. Custom Test strategies Define your strategy together with your team. Acceptance criteria
- 17. Machines Do Regression, Humans do Exploratory
- 18. Problem 2 UI Test Automation
- 26. Stable Mabl tests Unstable Mabl tests Experimental Mabl tests Production deploy CI trigger Green Red Remove build
- 28. Codeless UI automation tools completely changes how QA engineers work
- 29. mabl.com/testcon
- 31. Fail Fast Fail Early Fail Often
- 34. Post “Continuous Testing in DevOps”, Dan Ashby
- 35. Mabl
- 36. Problem 4 QA team being a team on its own
- 38. A team is not a group of people who work together. A team is a group of people who trust each other. Simon Sinek
- 40. It takes both sides to build a bridge Frederic Nael
- 41. Leaders should be gardeners Team of Teams by General Stanley McChrystal
- 42. Do quality engineering with a holistic view Thomas Noë
- 43. Problem 5 Hiring
- 44. QA skills ● You have solid experience in Java, Php, etc ● You have good knowledge of either Gradle/Maven, JUnit, or Docker ● You’re experienced in writing clear, concise and comprehensive test plans and test cases ● You have hands-on experience with automated testing tools (Selenium, Ansible, etc.)
- 45. Hire potential Critical thinking Strong network skills Strong analytical thinker Strong emotional intelligence Thinks as a customer Fast self learning Determined/Focussed Entrepreneur
- 46. Become QA consultant/advisor Network Jump in a team for a while Read the team Help the team to improve quality closer to the code Explore test together as a team Show the mirror to the team (based on facts) Influence PM - Dev lead - VP PM - Architect - UX architect
- 47. GA Feature Exploratory testing Continuous automation BETA 1. Acceptance criteria > test cases 2. Codeless UI > Selenium 3. Fail > safe releases 4. Team > QA team 5. Hiring: QA advisor > QA engineer
Editor's Notes
- We should not ask or check with the architect or with the UX architect
- The new devops way of working helps all the guilds to connect to each other and talk to each other. The pipeline binds all guilds and they are forced to talk and move forward. Focus on the pipeline will bring all parties together
- Natural network is popping up due to the possibility to work more independent in some way because the pipeline connects all the teams and guilds. So you have a dual cooperation. If the pipe is red teams are forced to work together to know what is going on and how to fix it. Once its fixed teams go again towards their independent way of working and continue