BDD and QA - Make Yourself More Valuable
•Download as ODP, PDF•
1 like•245 views
This document discusses the career journey of a QA engineer who has transitioned through various QA roles over 14 years. It poses a series of questions about the tester's experiences with manual and automation testing, challenges in the QA field, different software development lifecycles (SDLCs), and their experiences adopting behavior-driven development (BDD). The QA engineer offers to demonstrate a sample BDD project using Cucumber, Selenium, and the Serenity framework to illustrate how BDD differs from traditional SDLC models and discuss best practices.
Report
Share
Report
Share
Recommended
Игорь Калганов, Workle
The document outlines 16 levels or grades of experience for employees in UX & Design, Back-end, Front-end, and QC roles, defining the typical title or role for each level from Student to Expert. It includes a table mapping each role to grade levels 1 through 16, with some roles capped at certain levels. The document is signed by Igor Kalganov, CEO of Workle.
Scrum overview
Scrum is an agile framework for managing product development that focuses on quality, collaboration, and adaptability over rigid adherence to processes or plans. It emphasizes frequent inspection and adaptation, self-organizing cross-functional teams, and transparency. Key aspects include prioritizing a backlog of features based on business value, conducting short development iterations called sprints, and daily stand-up meetings for teams to share progress and issues. The goal is to deliver high quality, valuable software more quickly through an adaptive process of continuous improvement.
TDD, Refactoring - Workshop
This document discusses test-driven development (TDD) and refactoring using the Gilded Rose kata exercise. It provides rules for TDD, such as only writing production code with a failing test and refactoring code after each test. Simple design principles are outlined, like revealing intention and avoiding duplication. Extreme object-oriented programming rules are also listed, like limiting indentation and properties. The goal is to practice TDD and refactoring skills through the Gilded Rose kata.
Polar talks: code generation
3rd Polar Talks session:
How code generation and meta-programming influence developer's activity?
Do we gain more productivity, consistency and simplicity during everyday development for the cost of maintenability and complexity of the generated code?
It was an open public discussion involving colleague experts from other companies. The goal is to tackle the opinions on a certain topics from IT.
Bahaviour Driven Development
This document introduces Behavior Driven Development (BDD) as a rethinking and repurposing of existing agile methodologies like test-driven development (TDD) and extreme programming (XP) with a focus on defining value upfront. It discusses how BDD uses features made up of scenarios in a given-when-then format to define required system behaviors. This drives the development process through a red-green-refactor cycle of writing failing acceptance tests, unit tests, and code to pass the tests. The document recommends BDD tools like FitNesse, Story Q, and Cucumber and emphasizes that BDD is not about tools but rather delivering value through defined behaviors.
jSession#6 - Adam Bieńkowski - JGiven - BDD testing in plain Java
The document discusses Behavior Driven Development (BDD) testing using the JGiven framework in Java. It notes that BDD requires high business collaboration and follows a Given-When-Then structure. JGiven allows for writing tests in a natural language format with scenario, stage, and step annotations. It provides features for readability like tables, formatting, and reports. JGiven tests are highly readable, secure, and resistant to breaking due to refactoring thanks to the framework's design that separates behavior from implementation.
Test driven developement
Test Driven Development (TDD) is a software development process where test cases are written before code to validate requirements and ensure code quality. TDD focuses on designing code through testing by writing tests first and then code to pass those tests in short cycles. This enforces well-designed, stable code and speeds up development. The TDD cycle involves adding a test, running all tests with the new one failing, writing code to pass the test, running tests to confirm all pass, and refactoring code before repeating.
Collective ownership in agile teams
What is collective code ownership in agile teams? what are its advantages? .What are the common pitfalls of it ?.
What would be the ways to implement into software development teams. If you would like to talk more on the topic feel free to email kapil@jyaasa.com
Recommended
Игорь Калганов, Workle
The document outlines 16 levels or grades of experience for employees in UX & Design, Back-end, Front-end, and QC roles, defining the typical title or role for each level from Student to Expert. It includes a table mapping each role to grade levels 1 through 16, with some roles capped at certain levels. The document is signed by Igor Kalganov, CEO of Workle.
Scrum overview
Scrum is an agile framework for managing product development that focuses on quality, collaboration, and adaptability over rigid adherence to processes or plans. It emphasizes frequent inspection and adaptation, self-organizing cross-functional teams, and transparency. Key aspects include prioritizing a backlog of features based on business value, conducting short development iterations called sprints, and daily stand-up meetings for teams to share progress and issues. The goal is to deliver high quality, valuable software more quickly through an adaptive process of continuous improvement.
TDD, Refactoring - Workshop
This document discusses test-driven development (TDD) and refactoring using the Gilded Rose kata exercise. It provides rules for TDD, such as only writing production code with a failing test and refactoring code after each test. Simple design principles are outlined, like revealing intention and avoiding duplication. Extreme object-oriented programming rules are also listed, like limiting indentation and properties. The goal is to practice TDD and refactoring skills through the Gilded Rose kata.
Polar talks: code generation
3rd Polar Talks session:
How code generation and meta-programming influence developer's activity?
Do we gain more productivity, consistency and simplicity during everyday development for the cost of maintenability and complexity of the generated code?
It was an open public discussion involving colleague experts from other companies. The goal is to tackle the opinions on a certain topics from IT.
Bahaviour Driven Development
This document introduces Behavior Driven Development (BDD) as a rethinking and repurposing of existing agile methodologies like test-driven development (TDD) and extreme programming (XP) with a focus on defining value upfront. It discusses how BDD uses features made up of scenarios in a given-when-then format to define required system behaviors. This drives the development process through a red-green-refactor cycle of writing failing acceptance tests, unit tests, and code to pass the tests. The document recommends BDD tools like FitNesse, Story Q, and Cucumber and emphasizes that BDD is not about tools but rather delivering value through defined behaviors.
jSession#6 - Adam Bieńkowski - JGiven - BDD testing in plain Java
The document discusses Behavior Driven Development (BDD) testing using the JGiven framework in Java. It notes that BDD requires high business collaboration and follows a Given-When-Then structure. JGiven allows for writing tests in a natural language format with scenario, stage, and step annotations. It provides features for readability like tables, formatting, and reports. JGiven tests are highly readable, secure, and resistant to breaking due to refactoring thanks to the framework's design that separates behavior from implementation.
Test driven developement
Test Driven Development (TDD) is a software development process where test cases are written before code to validate requirements and ensure code quality. TDD focuses on designing code through testing by writing tests first and then code to pass those tests in short cycles. This enforces well-designed, stable code and speeds up development. The TDD cycle involves adding a test, running all tests with the new one failing, writing code to pass the test, running tests to confirm all pass, and refactoring code before repeating.
Collective ownership in agile teams
What is collective code ownership in agile teams? what are its advantages? .What are the common pitfalls of it ?.
What would be the ways to implement into software development teams. If you would like to talk more on the topic feel free to email kapil@jyaasa.com
JavaScript Unit Testing
This document discusses JS unit testing and provides guidance on how to implement it. It explains that unit tests isolate and test discrete functions to ensure they work as intended. This helps refactor code to be modular, scalable, and easier to understand. While unit tests add initial time, they speed up development in the long run. Common JS testing libraries include Mocha, Jasmine, and assertion libraries like Chai to validate results. The document also provides example unit test code and links to additional resources on JS testing.
Java interfaces design perspective
To make it simple - Java Interfaces are nothing but APIs, without implementation, as they are nothing but component interfaces. Using Interfaces in the design, one can achieve loose coupling, but declaring the component interfaces and vary the implementations
Practiced agile developer with tdd & bdd
This document discusses test-driven development (TDD) and behavior-driven development (BDD) as practices in agile software development. It explains that TDD focuses on writing tests before code to ensure code quality, while BDD extends TDD by specifying tests in terms of desired behaviors or requirements from a business perspective using a ubiquitous language. BDD aims to improve cohesion between technical implementation and the problem domain to make sense to both developers and business stakeholders.
Big feature - small sprint
My talk presentation from SQA Days 21 conference.
During last two years I've been working in Agile teams and quite often have come across the situation when the feature is pretty big, but they still want to release it at the end of the sprint. That is in spite of the fact, that there is a great risk of violation of the timing and poor product quality.
So what should we, quality guards, do when eventually everything depends on us?
My report presents the analysis of the development stages from the testing point of view in such a difficult situation and provides tips for success.
Behavior Driven Education: A Story of Learning ROR
This document provides an overview and reflection of the presenter's experience learning web development through behavior driven education (BDE) and Ruby on Rails (ROR). It defines test driven development (TDD) and behavior driven development (BDD), outlines the presenter's path to learning Rails, and describes the Cucumber BDD workflow and advantages/disadvantages of a BDE approach.
Bdd development flow process from end to end
This is the flow how a developer and SDET works in BDD and pushes every story to live. This included from and idea to live including automation in BDD.
(Sprint 1) besser childress logerquist-swain
The document summarizes the goals and achievements of Sprint 1 of a project to create an employee suggestion system mobile app. The team created login and registration pages, employee and reviewer views, and pulled ideas from a database to display dynamically. They aimed to complete the app framework but did not finish reviewing or commenting on ideas. The team encountered challenges with the Android development workflow, documentation, implementing mockups, and version control.
How Google Said - Ninja Code Review With Gerrit
This presentation explains why and what for we should use:
1) Trunk Based Development
2) Pre-commit Code Review
3) Gerrit
4) How they can be used together
This presentation was shared in one of Java User Groups in Astana, Kazakhstan
TDD and more than 9000 tries to sell it to a customer
1. TDD is a long-term investment that may not show results for months, so customers need to understand it requires patience.
2. Teams may not be experienced enough with TDD and would benefit from drills or training before adopting it.
3. TDD principles are more difficult to apply to legacy code that lacks tests, but training can help use TDD effectively anyway.
4. TDD is primarily an internal design tool, not just for catching bugs, so its design benefits need emphasis over external quality assurances.
Effective Testing in Agile
This document discusses effective testing in Agile environments. It introduces the Agile Testing Quadrants model which divides testing into four categories: technology-facing tests that support the team (unit and integration testing), business-facing tests that support the team (acceptance and functional testing), business-facing tests that critique the product (usability and exploratory testing), and technology-facing tests that critique the product (performance and security testing). It provides examples of tools that can be used for each testing quadrant and recommends practicing test automation, exploratory testing, and only documenting what is useful.
QA tester in the Scrum
A QA tester plays an important role in each part of the Scrum process. In sprint planning, they help estimate development and QA tasks and share test specifications. During the sprint, they write automation and manual tests, review each other's work, and share testing knowledge. In daily standups, they update on previous and current tasks. At the end of the sprint, they participate in the review and retrospective.
A Story’s Journey
A simple demonstration of the journey a User Story takes from idea to production, highlighting the amount of attention it gets ensuring quality and business value.
Tdd and bdd
a brief introduction to Test Driven Development and Behavior Driven Development and the main differences between both.
Using Scrum Internship Course
SCRUM usage is a document that outlines the goals and processes of Scrum project management. It describes Scrum as a strategy where a self-managed team works together to achieve common goals while allowing for changing requirements. The key actors in Scrum are the product owner, who represents the client, and the Scrum team. Sprints involve planning, daily stand-ups, retrospectives, and demos to incrementally deliver working software.
What is Agile Testing?
Agile Methodology is not new. Many organisations / teams have already adopted Agile way of Software Development or are in the enablement journey for the same. What does this mean for Testing? There is no doubt that the Testing approach and mindset also needs to change to be in tune with the Agile Development methodology. Learn what does it mean to Test on Agile Projects.
Post agile confessions
The document discusses issues that can arise with Agile practices and provides suggestions for improvement. It notes that while Agile principles aim for customer satisfaction, changing requirements, and frequent delivery, some implementations experience problems like a lack of continuous improvement, low code quality, and cultural challenges. The document advocates rediscovering the heart of Agile and experimentation to address these issues, and provides an example of using specification by example to improve collaboration between developers and quality specialists. It concludes by acknowledging Agile is a learning process and that change is needed for progress.
How to get stakeholder involvement in an agile world?v2
Stakeholder involvement in an agile world with My Product is a James Bond Movie.
Speaking at IPMA Global Congress Rotterdam Oct 1st 2014
Design Process for Robotics Competition
In this presentation, I share about the importance of planning a design process for a robotic competition. The content covers Design Requirement and Objective (DR&O) and Iterative Design Process to guide us through the process of designing robots for competition.
Agile Network India | Be Customer Centric with Test First Development | Mamat...
This document discusses how adopting test-first development strategies like Test Driven Development (TDD) and Behavior Driven Development (BDD) can help organizations build a more customer-centric culture. It emphasizes that in today's competitive environment, focusing on agile practices, DevOps, and test-first methodologies gives companies an edge over those that do not. The document outlines how the organization matured in applying TDD and BDD, from initial training and pair programming to integrating automated testing into their development process and using examples from feature files as test cases.
Agile tester 3.0
The document discusses Daniel Ricardo de Amorim and his role as an Agile QA Consultant. It explores how agile testers work as part of development teams rather than as separate roles. It sorts QA profiles into three dimensions: business, technical, and DevOps. The business dimension involves acceptance testing and BDD. The technical dimension covers programming skills, TDD, test automation, and security and performance testing. The DevOps dimension focuses on continuous delivery and automating repeatable tasks. All QAs keep the team focused on delivery, product quality, test ownership, and wear many hats to infect the team with quality practices.
Q3
Here is my answer to question 3 for my evaluation, containing numerous ideas and thoughts as to why I chose specific media institutions who may or may not distribute my media film product. Enjoy!
More Related Content
What's hot
JavaScript Unit Testing
This document discusses JS unit testing and provides guidance on how to implement it. It explains that unit tests isolate and test discrete functions to ensure they work as intended. This helps refactor code to be modular, scalable, and easier to understand. While unit tests add initial time, they speed up development in the long run. Common JS testing libraries include Mocha, Jasmine, and assertion libraries like Chai to validate results. The document also provides example unit test code and links to additional resources on JS testing.
Java interfaces design perspective
To make it simple - Java Interfaces are nothing but APIs, without implementation, as they are nothing but component interfaces. Using Interfaces in the design, one can achieve loose coupling, but declaring the component interfaces and vary the implementations
Practiced agile developer with tdd & bdd
This document discusses test-driven development (TDD) and behavior-driven development (BDD) as practices in agile software development. It explains that TDD focuses on writing tests before code to ensure code quality, while BDD extends TDD by specifying tests in terms of desired behaviors or requirements from a business perspective using a ubiquitous language. BDD aims to improve cohesion between technical implementation and the problem domain to make sense to both developers and business stakeholders.
Big feature - small sprint
My talk presentation from SQA Days 21 conference.
During last two years I've been working in Agile teams and quite often have come across the situation when the feature is pretty big, but they still want to release it at the end of the sprint. That is in spite of the fact, that there is a great risk of violation of the timing and poor product quality.
So what should we, quality guards, do when eventually everything depends on us?
My report presents the analysis of the development stages from the testing point of view in such a difficult situation and provides tips for success.
Behavior Driven Education: A Story of Learning ROR
This document provides an overview and reflection of the presenter's experience learning web development through behavior driven education (BDE) and Ruby on Rails (ROR). It defines test driven development (TDD) and behavior driven development (BDD), outlines the presenter's path to learning Rails, and describes the Cucumber BDD workflow and advantages/disadvantages of a BDE approach.
Bdd development flow process from end to end
This is the flow how a developer and SDET works in BDD and pushes every story to live. This included from and idea to live including automation in BDD.
(Sprint 1) besser childress logerquist-swain
The document summarizes the goals and achievements of Sprint 1 of a project to create an employee suggestion system mobile app. The team created login and registration pages, employee and reviewer views, and pulled ideas from a database to display dynamically. They aimed to complete the app framework but did not finish reviewing or commenting on ideas. The team encountered challenges with the Android development workflow, documentation, implementing mockups, and version control.
How Google Said - Ninja Code Review With Gerrit
This presentation explains why and what for we should use:
1) Trunk Based Development
2) Pre-commit Code Review
3) Gerrit
4) How they can be used together
This presentation was shared in one of Java User Groups in Astana, Kazakhstan
TDD and more than 9000 tries to sell it to a customer
1. TDD is a long-term investment that may not show results for months, so customers need to understand it requires patience.
2. Teams may not be experienced enough with TDD and would benefit from drills or training before adopting it.
3. TDD principles are more difficult to apply to legacy code that lacks tests, but training can help use TDD effectively anyway.
4. TDD is primarily an internal design tool, not just for catching bugs, so its design benefits need emphasis over external quality assurances.
Effective Testing in Agile
This document discusses effective testing in Agile environments. It introduces the Agile Testing Quadrants model which divides testing into four categories: technology-facing tests that support the team (unit and integration testing), business-facing tests that support the team (acceptance and functional testing), business-facing tests that critique the product (usability and exploratory testing), and technology-facing tests that critique the product (performance and security testing). It provides examples of tools that can be used for each testing quadrant and recommends practicing test automation, exploratory testing, and only documenting what is useful.
QA tester in the Scrum
A QA tester plays an important role in each part of the Scrum process. In sprint planning, they help estimate development and QA tasks and share test specifications. During the sprint, they write automation and manual tests, review each other's work, and share testing knowledge. In daily standups, they update on previous and current tasks. At the end of the sprint, they participate in the review and retrospective.
A Story’s Journey
A simple demonstration of the journey a User Story takes from idea to production, highlighting the amount of attention it gets ensuring quality and business value.
Tdd and bdd
a brief introduction to Test Driven Development and Behavior Driven Development and the main differences between both.
Using Scrum Internship Course
SCRUM usage is a document that outlines the goals and processes of Scrum project management. It describes Scrum as a strategy where a self-managed team works together to achieve common goals while allowing for changing requirements. The key actors in Scrum are the product owner, who represents the client, and the Scrum team. Sprints involve planning, daily stand-ups, retrospectives, and demos to incrementally deliver working software.
What is Agile Testing?
Agile Methodology is not new. Many organisations / teams have already adopted Agile way of Software Development or are in the enablement journey for the same. What does this mean for Testing? There is no doubt that the Testing approach and mindset also needs to change to be in tune with the Agile Development methodology. Learn what does it mean to Test on Agile Projects.
Post agile confessions
The document discusses issues that can arise with Agile practices and provides suggestions for improvement. It notes that while Agile principles aim for customer satisfaction, changing requirements, and frequent delivery, some implementations experience problems like a lack of continuous improvement, low code quality, and cultural challenges. The document advocates rediscovering the heart of Agile and experimentation to address these issues, and provides an example of using specification by example to improve collaboration between developers and quality specialists. It concludes by acknowledging Agile is a learning process and that change is needed for progress.
How to get stakeholder involvement in an agile world?v2
Stakeholder involvement in an agile world with My Product is a James Bond Movie.
Speaking at IPMA Global Congress Rotterdam Oct 1st 2014
Design Process for Robotics Competition
In this presentation, I share about the importance of planning a design process for a robotic competition. The content covers Design Requirement and Objective (DR&O) and Iterative Design Process to guide us through the process of designing robots for competition.
Agile Network India | Be Customer Centric with Test First Development | Mamat...
This document discusses how adopting test-first development strategies like Test Driven Development (TDD) and Behavior Driven Development (BDD) can help organizations build a more customer-centric culture. It emphasizes that in today's competitive environment, focusing on agile practices, DevOps, and test-first methodologies gives companies an edge over those that do not. The document outlines how the organization matured in applying TDD and BDD, from initial training and pair programming to integrating automated testing into their development process and using examples from feature files as test cases.
Agile tester 3.0
The document discusses Daniel Ricardo de Amorim and his role as an Agile QA Consultant. It explores how agile testers work as part of development teams rather than as separate roles. It sorts QA profiles into three dimensions: business, technical, and DevOps. The business dimension involves acceptance testing and BDD. The technical dimension covers programming skills, TDD, test automation, and security and performance testing. The DevOps dimension focuses on continuous delivery and automating repeatable tasks. All QAs keep the team focused on delivery, product quality, test ownership, and wear many hats to infect the team with quality practices.
What's hot (20)
Behavior Driven Education: A Story of Learning ROR
Behavior Driven Education: A Story of Learning ROR
TDD and more than 9000 tries to sell it to a customer
TDD and more than 9000 tries to sell it to a customer
How to get stakeholder involvement in an agile world?v2
How to get stakeholder involvement in an agile world?v2
Agile Network India | Be Customer Centric with Test First Development | Mamat...
Agile Network India | Be Customer Centric with Test First Development | Mamat...
Viewers also liked
Q3
Here is my answer to question 3 for my evaluation, containing numerous ideas and thoughts as to why I chose specific media institutions who may or may not distribute my media film product. Enjoy!
conceptos de enfermedad y trastorno mental. clasificación. trastornos clínico...
conceptos de enfermedad y trastorno mental. clasificación. trastornos clínico...Alejandro Montoya Zamora
Este documento discute los conceptos de enfermedad y trastorno mental, la clasificación de trastornos psiquiátricos, y las bases etiopatogénicas de los trastornos mentales. Explica que el término "trastorno mental" es más amplio que "enfermedad mental" y se aplica a cualquier alteración de la salud mental, independientemente de su causa. También describe las dos clasificaciones psiquiátricas más utilizadas, la CIE-10 y el DSM-IV-TR, y sus limitaciones. Finalmente, señEXERCÍCIOS DA APOSTILA "MODELOS ATÔMICOS" - 2º ANOS
O documento discute os modelos atômicos de Dalton, Thomson e Rutherford. Resume que Dalton considerou os átomos como indivisíveis e maciços, Thomson propôs que os átomos consistem de uma esfera positiva com elétrons negativos dentro, e Rutherford determinou que os átomos têm um núcleo positivo pequeno com elétrons orbitando ao redor.
Lessons in Persuasive Language from The Game of Thrones
The document discusses Tyrion's persuasive speech to Daenerys in Game of Thrones, comparing it to speeches by Winston Churchill and Jerry Maguire. It notes that Tyrion's speech was effective without slides or props, relying solely on his words and delivery. The document suggests that while tools like PowerPoint are useful, the most persuasive presentations are often given by a speaker alone on stage expressing their viewpoint with conviction.
Module 3 recruitment
The document discusses recruitment processes and techniques. It defines recruitment as finding and attracting capable applicants for jobs in an organization. The recruitment process includes identifying vacancies, preparing job descriptions, advertising positions, managing responses, shortlisting, interviewing, and making hiring decisions. Sources of recruitment can be internal like current employees or external like job boards, agencies, and colleges. The recruitment function is influenced by internal factors controlled by the organization and external factors outside its control like economic conditions. The objective of recruitment is to attract qualified candidates and hire the best ones to meet organizational needs.
Reports of automation all problems one solution
This document discusses the need for a custom tool to analyze automation test reports from multiple platforms in a systematic way. It notes that while testing may feel completed, the real work of analyzing often hundreds of results starts then. The tool would help address this pain point faced by automation testers. It also stresses the importance of selecting the right technologies, following the correct approach, and considering important factors like backward traceability when designing such a solution.
M-Agile - Best practices for successful Mobile Agile - Roy Nuriel PerfectoMobile
The Agile Manifesto was published in 2001 and now nearly every software development team claims to be following Agile practices (to some extent). Client server and web app project teams have reached a level of maturity enabling frequent releases with a predictable velocity and high quality. Agile practices move organizations towards embedding quality throughout the process.
But, these same teams are feeling daily pressure to deliver similar capabilities on mobile devices. Business is shifting to the digital experience and mobility is the central focus. Organizations succeeding to deliver standard web and other technologies are now struggling to achieve the same maturity in the mobile (web & native) world or what we are calling M-Agile (Mobile Agile).
In this session we will explore why the unique aspects of mobile app development are changing SDLC (software development lifecycle) practices. There is no magic to adapt current practices. Rather, we will share a recommended set of practices to achieve predictable velocity and deliver high quality mobile apps. The conversation will specifically address how to implement continuous integration (CI) to achieve the fast feedback / fast correction cycle required to drive mobile app engagement. CI can help teams also achieve Continuous Quality by embedding functional and non-functional verification in every build.
Testing as a container
This document discusses using Docker containers to improve testing workflows. It outlines challenges with traditional testing approaches that can slow down deployments. Containers are presented as a solution by providing isolated, portable testing environments. The rest of the document demonstrates how to test applications using Docker containers, Docker Compose, and Selenium with examples of API, web, and Selenium Grid tests. Best practices are provided for containerizing tests along with a proposed continuous integration workflow using containers.
Gallup Report
The document summarizes the results of a strengths assessment for Johnathan Flores Torres. It identifies his top five signature themes: Achiever, Futuristic, Strategic, Command, and Activator. These themes provide insight into Johnathan's natural talents and abilities that lead to his consistent success. His Achiever theme drives him to achieve something tangible every day in order to feel satisfied. As a Futuristic, he enjoys envisioning potential futures and uses visions of what could be to energize himself and others.
Viewers also liked (13)
Open Education - warum soll man in freie Bildung investieren?
Open Education - warum soll man in freie Bildung investieren?
conceptos de enfermedad y trastorno mental. clasificación. trastornos clínico...
conceptos de enfermedad y trastorno mental. clasificación. trastornos clínico...
EXERCÍCIOS DA APOSTILA "MODELOS ATÔMICOS" - 2º ANOS
EXERCÍCIOS DA APOSTILA "MODELOS ATÔMICOS" - 2º ANOS
Lessons in Persuasive Language from The Game of Thrones
Lessons in Persuasive Language from The Game of Thrones
M-Agile - Best practices for successful Mobile Agile - Roy Nuriel PerfectoMobile
M-Agile - Best practices for successful Mobile Agile - Roy Nuriel PerfectoMobile
Similar to BDD and QA - Make Yourself More Valuable
Agile Testing Agile Ottawa April 2015
Agile testing focuses on delivering valuable working software through collaboration, feedback, and automation. It involves the whole team taking responsibility for quality. Agile testers provide continuous feedback, prioritize value, and think critically to challenge assumptions and find problems. They collaborate with developers to shift testing left in the SDLC through approaches like specification by example and behavior driven development which define examples of desired behavior to build shared understanding.
1x10 - QA Engineer Role in JIRA
This document discusses the role of a QA Engineer in an agile team working on the JIRA project. It describes how the QA Engineer works closely with developers throughout the development process, providing guidance on testing and quality assurance. Key responsibilities of the QA Engineer include risk identification, automation testing, code reviews, and demoing new features to gain confidence before being marked as complete. The document advocates for an approach where developers take responsibility for testing their own code, with QA Engineers acting as assistants to help educate on quality best practices rather than doing all the testing themselves.
1×10 rola QA w tworzeniu Atlassian JIRA
This document discusses the role of a QA Engineer in JIRA. It notes that the QA Engineer works with a team of 15 people including developers, product managers, UX designers, and other QAs. It emphasizes that with Agile development, testing is now a shared responsibility of developers rather than being isolated to testers. Developers are expected to write and execute both manual and automated tests as part of development. The document outlines the development and release process at JIRA, with major releases every 2-3 months and bugfix releases every 2 weeks for the on-demand product. It stresses testing early and often through the development cycle rather than relying on testing at the end. Automated regression tests run on every code change to prevent
Ba why development projects fail
This document discusses the role of business analysts (BAs) in software development projects and testing. It notes that many projects fail due to poor requirements, lack of communication, or an inability to manage changes. The BA plays an important role in eliciting requirements, communicating with stakeholders, and ensuring requirements are tested throughout development in an iterative process. BAs should work closely with developers from the start of a project using techniques like agile development and iterative testing to help address changes and improve the chances of project success.
What is and is not QA!
The document discusses the role and responsibilities of a quality analyst (QA). It defines QA as the first level of customers, a guide for overall software quality, and someone who focuses on prevent defects rather than just finding them. Typical QA activities include managing test scenarios and defects, automating test cases, raising quality risks, and establishing client relationships. The document also discusses test automation best practices like the test pyramid and when different types of manual and automated tests should be used. It invites the reader to learn more about a career in QA.
Software Testing Overview
Software testing involves validating that the product being built is the right one and verifying that it is being built correctly. Testing helps find bugs, missing features, and ensures quality by providing feedback. There are different types of manual and automated testing techniques as well as common challenges like tests being difficult to write and maintain. The future of testing is trending toward more mature testing roles, cloud and social testing, smarter results analysis, and standards like ISO 29119.
Software development. xp, agile, etc.
Agile, eXtreme Programming (XP), and software prototyping are approaches to software development. Agile focuses on individuals, interactions, working software, and responding to change over processes, tools, documentation, and plans. XP uses pair programming, continuous integration, refactoring, and frequent releases. It also emphasizes shared understanding. Software prototyping identifies requirements early, gets users involved, and enhances or discards prototypes to reduce time and costs and ensure user satisfaction. Different methodologies work best depending on project size and needs.
Lets cook cucumber !!
This document provides an overview of Cucumber, a behavior-driven development framework. It discusses what BDD is, the benefits it provides like usability, fewer defects, and living documentation. Popular BDD tools like Cucumber, Jasmine and JBehave are mentioned. Cucumber is introduced in more detail, explaining how it executes scenarios using a Given, When, Then format and supports multiple programming languages. Hands-on examples demonstrate features like data and table-driven execution, background, hooks, tags and reports. Suggested additional reading materials on BDD and Cucumber are also provided.
Using AI-Powered Visual Tests to empower your tests
This document discusses using AI-powered visual testing to improve test automation. It describes problems with current functional testing approaches like fragile selectors, complex validation code, and only validating expected outcomes. Visual testing is presented as a solution by replacing fragile selectors and complex code with whole-page image comparisons. Challenges with naive image diffing like anti-aliasing differences are addressed through cloud-based solutions using AI algorithms to detect meaningful visual differences like humans. The document demonstrates these concepts through a visual testing tool demo.
Test Automation Framework using Cucumber BDD overview (part 1)
This seminar is about understanding BDD concepts. This includes overview of test automation framework using Cucumber/Java.
Indix Engineering Culture Code (2015)
Set of Engineering Principles that were part of the engineering culture at Indix. This document was authored during the beginning of 2015.
Quality is a Mindset
Quality is not the responsibility of testers alone, but of the whole agile team. It should be a shared mindset and definition agreed upon by the team. Several techniques can help build quality in, including defining acceptance criteria through conversations between product owners, developers and testers; practicing test-driven development; and ensuring story kick-offs and "shoulder taps" between team members to facilitate collaboration and catch issues early. The document discusses the importance of collaboration, automation, and not trading off quality to deliver features quickly.
Development Projects Failing? What can the Business Analyst Do?
This seminar strives to explore why development projects often fail to deliver and what the BA can do about it. Though there are no magic solutions that will fix development challenges, there are industry recognized practices that can help the BA or PM strive to keep the work on track and deliver value to the client on time. The first half of the presentation explores the cause of development project failures and the second half presents practical and applicable solutions that any BA or PM can bring back to their team.
РОМАН ЯКИМЧУК «Оптимізація QA процесів» Kyiv QADay 2021
Roman Yakymchuk is a QA consultant with 9 years of experience who provides QA process optimization services. He recommends using exploratory testing approaches, simplifying processes, automating repeatable tasks, and communicating effectively between teams. Key advice includes taking part in discussions early, learning about competitors, automating only worthwhile tasks, and sharing knowledge to prevent issues from a single person's absence. The goal of QA should be to prevent bugs rather than just find them.
Choosing the right QA strategy for a successful project
- Why is QA the most important factor behind successful software projects? QA helps create high quality products through well-defined processes without shortcuts in development.
- How to develop quality software and not go bankrupt? Choose the optimal QA strategy including the right testing approach, layers, and automation for cost-effective quality.
- Which types of tests will be the best? Consider the Test Pyramid vs Testing Trophy to discuss and decide on the best testing types including integration, unit, and end-to-end tests.
BDD - Collaboration & Hands-on practices
This document discusses Behavior-Driven Development (BDD) and how it can help deliver valuable software quickly by focusing on business value and user behavior through techniques like ubiquitous language, living documentation, and specifying examples. It provides tips for implementing BDD, including defining requirements and acceptance criteria, writing scenarios, test automation approaches, and ensuring business involvement. The document emphasizes that BDD is not restricted to any one layer or framework, and can be applied to both user interfaces and APIs.
Agile work practices and tools
Agile work pratices and tools.
Focuses on the various collaboration and development practices, characteristic of Agile Software Development.
Test driven development - why you should test first?
My goal is to convince you to test your code the next time you are developing an application.
Introduction to test driven development
Gauge your BDD Test (vodQA Hyderabad)
This is the presentation for the "Gauge your BDD Tests" automation testing workshop conducted at vodQA Hyderabad 2015 in ThoughtWorks Hyderabad office.
BDD with Gauge
The document discusses Behavior Driven Development (BDD) and the Gauge testing framework. It begins with an overview of BDD, noting that it is a collaborative way to define test behavior using natural language. Examples are given of well-written BDD tests in the Given-When-Then format. The document then introduces the Gauge framework, highlighting its key features like simple Markdown syntax, multiple language support, and integration with CI/CD pipelines. A hands-on workshop on using Gauge is outlined, followed by a Q&A session.
Similar to BDD and QA - Make Yourself More Valuable (20)
Using AI-Powered Visual Tests to empower your tests
Using AI-Powered Visual Tests to empower your tests
Test Automation Framework using Cucumber BDD overview (part 1)
Test Automation Framework using Cucumber BDD overview (part 1)
Development Projects Failing? What can the Business Analyst Do?
Development Projects Failing? What can the Business Analyst Do?
РОМАН ЯКИМЧУК «Оптимізація QA процесів» Kyiv QADay 2021
РОМАН ЯКИМЧУК «Оптимізація QA процесів» Kyiv QADay 2021
Choosing the right QA strategy for a successful project
Choosing the right QA strategy for a successful project
Test driven development - why you should test first?
Test driven development - why you should test first?
Recently uploaded
DDS-Security 1.2 - What's New? Stronger security for long-running systems
DDS Security Version 1.2 was adopted in 2024. This revision strengthens support for long runnings systems adding new cryptographic algorithms, certificate revocation, and hardness against DoS attacks.
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Allez au-delà du battage médiatique autour de l’IA et découvrez des techniques pratiques pour utiliser l’IA de manière responsable à travers les données de votre organisation. Explorez comment utiliser les graphes de connaissances pour augmenter la précision, la transparence et la capacité d’explication dans les systèmes d’IA générative. Vous partirez avec une expérience pratique combinant les relations entre les données et les LLM pour apporter du contexte spécifique à votre domaine et améliorer votre raisonnement.
Amenez votre ordinateur portable et nous vous guiderons sur la mise en place de votre propre pile d’IA générative, en vous fournissant des exemples pratiques et codés pour démarrer en quelques minutes.
Artificia Intellicence and XPath Extension Functions
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
The quest for the best AI face swap solution is marked by an amalgamation of technological prowess and artistic finesse, where cutting-edge algorithms seamlessly replace faces in images or videos with striking realism. Leveraging advanced deep learning techniques, the best AI face swap tools meticulously analyze facial features, lighting conditions, and expressions to execute flawless transformations, ensuring natural-looking results that blur the line between reality and illusion, captivating users with their ingenuity and sophistication.
Web:- https://undressbaby.com/
E-commerce Application Development Company.pdf
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
Mobile App Development Company In Noida | Drona Infotech
Looking for a reliable mobile app development company in Noida? Look no further than Drona Infotech. We specialize in creating customized apps for your business needs.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptx
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
May Marketo Masterclass, London MUG May 22 2024.pdf
Can't make Adobe Summit in Vegas? No sweat because the EMEA Marketo Engage Champions are coming to London to share their Summit sessions, insights and more!
This is a MUG with a twist you don't want to miss.
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
Empowering Growth with Best Software Development Company in Noida - Deuglo
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
LORRAINE ANDREI_LEQUIGAN_HOW TO USE ZOOM
Zoom is a comprehensive platform designed to connect individuals and teams efficiently. With its user-friendly interface and powerful features, Zoom has become a go-to solution for virtual communication and collaboration. It offers a range of tools, including virtual meetings, team chat, VoIP phone systems, online whiteboards, and AI companions, to streamline workflows and enhance productivity.
SWEBOK and Education at FUSE Okinawa 2024
Takashi Kobayashi and Hironori Washizaki, "SWEBOK Guide and Future of SE Education," First International Symposium on the Future of Software Engineering (FUSE), June 3-6, 2024, Okinawa, Japan
Utilocate provides Smarter, Better, Faster, Safer Locate Ticket Management
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
GraphSummit Paris - The art of the possible with Graph Technology
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Hand Rolled Applicative User Validation Code Kata
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
GOING AOT WITH GRAALVM FOR SPRING BOOT (SPRING IO)
This session covers GraalVM & Spring Boot, Spring AOT, performance optimizations and using libraries
Recently uploaded (20)
DDS-Security 1.2 - What's New? Stronger security for long-running systems
DDS-Security 1.2 - What's New? Stronger security for long-running systems
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Artificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension Functions
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
Mobile App Development Company In Noida | Drona Infotech
Mobile App Development Company In Noida | Drona Infotech
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptx
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptx
May Marketo Masterclass, London MUG May 22 2024.pdf
May Marketo Masterclass, London MUG May 22 2024.pdf
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Empowering Growth with Best Software Development Company in Noida - Deuglo
Empowering Growth with Best Software Development Company in Noida - Deuglo
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
Utilocate provides Smarter, Better, Faster, Safer Locate Ticket Management
Utilocate provides Smarter, Better, Faster, Safer Locate Ticket Management
GraphSummit Paris - The art of the possible with Graph Technology
GraphSummit Paris - The art of the possible with Graph Technology
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
GOING AOT WITH GRAALVM FOR SPRING BOOT (SPRING IO)
GOING AOT WITH GRAALVM FOR SPRING BOOT (SPRING IO)
BDD and QA - Make Yourself More Valuable
- 1. Waiter to Assistant Cook aka QA to Co-Developer , Co-Product Manager
- 2. 14 years of Testing Journey ● Manual Tester ● Automation Tester ● Manual Testing Lead ● SDET ● BDD addict and preacher ( at present )
- 3. What I did , loved , hated ● Indian Software Industry from my eyes ● Role of QA in it ● Why QA is NOT treated at par with Developer , Product Manager ?
- 4. QA Complaints ● Are you QA engineer by choice or compulsion ? ● Do you like your job ? ● Do you like your salary ? ● Do you want to be in QA whole life ?
- 5. Questions to QA ● How can you be of more value in your project ? ● Do you know coding ? ● Do you know automation ?
- 6. Questions about Automation ● What kind of automation you do ? ● UI , Unit , API ? ● Which one is best in terms of testing coverage ?
- 7. Your project life cycle ● What kind of SDLC do you follow ? ● What is difference between Water fall , Agile , Scrum etc ● What is TDD , BDD ?
- 8. Achieving BDD ● How to shift to BDD from existing SDLC ? ● Challenges ● Changing behavior of Developer and PM to achieve success in BDD
- 9. … continue ● Example Mapping ● 3 Amigos Session ● Acceptance Testing – Who & How
- 10. BDD vs Existing Model ● NON BDD Coding ( adding bugs ) → testing → prioritization → Bug fixing and adding new -> repeat cycle ● BDD Discuss , clarify , agree → automated tests -> Coding to make tests pass ( lesser Bugs ) → Fix tests → Coding → repeat
- 11. Cucumber Tool ● What is it ? ● How is it used along with Selenium , Appium , API testing ? ● Contribute , learn , grow
- 12. …. continue ● Is it Automation Tool ? ● Is it replaces existing automation tools ? ● Does it have steep learning curve ?
- 13. Demo Project ( Git repo ) ● Serenity Framework ● Selenium + Java ● Cucumber
- 14. … continue ● Scenarios ● Test Cases vs Scenarios ● Tips ● Good practices
- 15. My Experiences with BDD ● Am I comfortable with BDD now ? ● Challenges being faced ? ● What I can do better ?