Behavior-Driven Design: One Team's Exploration
•Download as PPTX, PDF•
0 likes•701 views
Looking into a team’s experience with adopting Behavior-Driven Development (BDD) and at answering these questions: - Why did we try it? - What tools and processes did we adopt? - How did it go?
Report
Share
Report
Share
Recommended
Introduction to BDD
BDD is about implementing the software by describing its behavior from the perspective of its stakeholders, and customers.
8th Alg--Dec14
The document outlines assignments due tomorrow including a chapter 5 review packet and test, with instructions to complete a timed test, turn in checked homework, and work on the review packet with a partner.
Introduction to TDD and BDD
This document introduces Behavior-Driven Development (BDD). BDD focuses on defining desired software behaviors and outcomes from the perspective of stakeholders through user stories and scenarios. Scenarios are expressed using a simple domain-specific language called Gherkin that both documents requirements and serves as automated tests. BDD promotes collaboration between teams through examples that are shared to discuss requirements, design code, and implement tests. Its benefits include improved understanding of requirements, increased confidence in refactoring code, and faster delivery of working, tested software.
React Native: How It Works
The trend of using React Native for developing iOS and Android apps is growing. But what exactly is React Native and how does it work under the hood?
Definition Of Done
The document discusses defining the "Definition of Done" (DoD) which establishes the quality standards and activities required to consider a user story or increment of work complete. It notes problems that can occur without a DoD such as technical debt, unpredictable delivery dates, and overcommitting work. The document recommends that the team, including the product owner, define the DoD during backlog estimation and that the definition evolves over sprints based on the team's experience. It provides some examples of DoD criteria for user stories and sprints.
Integration of automation framework with ci tools
This document discusses continuous integration (CI) and how to integrate an automation testing framework with a CI tool. It defines key CI concepts like pipelines, stages, jobs, and tasks. A pipeline contains multiple stages that run sequentially, with each stage containing parallel jobs made up of sequential tasks. The document also provides instructions on downloading, installing, and configuring a Go CI server and agent to run an automation test suite through CI pipelines.
Agile or: how I learned to stop worrying and love changing requirements
This document provides an overview of Agile project management principles and practices. It begins by introducing Agile and its focus on adapting to changing requirements. It then discusses key Agile concepts like iterative development, working software at each build, self-organizing teams, and prioritizing customer collaboration. The document outlines Agile roles like developers, Scrum masters, and product owners. It also summarizes practices like story pointing, daily standups, iteration planning, and retrospectives. Finally, it discusses adapting processes through inspection and emphasizes the benefits of a pull-based workflow over push-based development.
Working effectively with legacy code chapter1
This document discusses working with legacy code and reasons for changing code. It notes that while code may not be object-oriented or beautiful, lack of tests makes changing code risky. Tests allow for refactoring even awful code. The four reasons for changing code are adding features, fixing bugs, refactoring, and optimizing. Changes affect structure, new functions, existing functions, resources, and test code depending on the reason. Changing code is difficult because it's hard to determine what to change, confirm the change is correct, and ensure nothing is broken. Not changing also risks increasing complexity, decreasing change skills over time, and growing fear of changing code.
Recommended
Introduction to BDD
BDD is about implementing the software by describing its behavior from the perspective of its stakeholders, and customers.
8th Alg--Dec14
The document outlines assignments due tomorrow including a chapter 5 review packet and test, with instructions to complete a timed test, turn in checked homework, and work on the review packet with a partner.
Introduction to TDD and BDD
This document introduces Behavior-Driven Development (BDD). BDD focuses on defining desired software behaviors and outcomes from the perspective of stakeholders through user stories and scenarios. Scenarios are expressed using a simple domain-specific language called Gherkin that both documents requirements and serves as automated tests. BDD promotes collaboration between teams through examples that are shared to discuss requirements, design code, and implement tests. Its benefits include improved understanding of requirements, increased confidence in refactoring code, and faster delivery of working, tested software.
React Native: How It Works
The trend of using React Native for developing iOS and Android apps is growing. But what exactly is React Native and how does it work under the hood?
Definition Of Done
The document discusses defining the "Definition of Done" (DoD) which establishes the quality standards and activities required to consider a user story or increment of work complete. It notes problems that can occur without a DoD such as technical debt, unpredictable delivery dates, and overcommitting work. The document recommends that the team, including the product owner, define the DoD during backlog estimation and that the definition evolves over sprints based on the team's experience. It provides some examples of DoD criteria for user stories and sprints.
Integration of automation framework with ci tools
This document discusses continuous integration (CI) and how to integrate an automation testing framework with a CI tool. It defines key CI concepts like pipelines, stages, jobs, and tasks. A pipeline contains multiple stages that run sequentially, with each stage containing parallel jobs made up of sequential tasks. The document also provides instructions on downloading, installing, and configuring a Go CI server and agent to run an automation test suite through CI pipelines.
Agile or: how I learned to stop worrying and love changing requirements
This document provides an overview of Agile project management principles and practices. It begins by introducing Agile and its focus on adapting to changing requirements. It then discusses key Agile concepts like iterative development, working software at each build, self-organizing teams, and prioritizing customer collaboration. The document outlines Agile roles like developers, Scrum masters, and product owners. It also summarizes practices like story pointing, daily standups, iteration planning, and retrospectives. Finally, it discusses adapting processes through inspection and emphasizes the benefits of a pull-based workflow over push-based development.
Working effectively with legacy code chapter1
This document discusses working with legacy code and reasons for changing code. It notes that while code may not be object-oriented or beautiful, lack of tests makes changing code risky. Tests allow for refactoring even awful code. The four reasons for changing code are adding features, fixing bugs, refactoring, and optimizing. Changes affect structure, new functions, existing functions, resources, and test code depending on the reason. Changing code is difficult because it's hard to determine what to change, confirm the change is correct, and ensure nothing is broken. Not changing also risks increasing complexity, decreasing change skills over time, and growing fear of changing code.
Dicoding Developer Coaching #38: Android | 5 Library Android yang Patut Kamu ...
Dicoding Developer Coaching merupakan webinar, yang membahas tuntas kendala maupun pertanyaan yang sering ditanyakan di Academy Dicoding.
Tema kali ini adalah "5 Library Android yang Patut Kamu Coba di 2021"
Library sering sekali membantu kita sebagai developer untuk mengembangkan aplikasi dengan lebih cepat dan efisien. Nah, di sini kita akan memilih 5 Library yang patut kamu coba di tahun 2021. Ada library yang dapat membantu dalam memanajemen log dan juga error ketika aplikasi dirilis. Ada juga library yang dapat membuat desain aplikasi menjadi lebih menarik. Selain itu, ada juga library yang dapat digunakan untuk menampilkan peta. Penasaran library apa sajakah itu? Yuk ikuti developer coaching penutup dari series Android ini.
Is Agile Better
- The document discusses the benefits of Agile development over traditional development methods. It outlines some key differences like using whole teams, short iterations with frequent feedback, and incremental design versus "big bang" development.
- Some benefits of Agile cited include higher quality, more options/flexibility, increased visibility, and higher ROI sooner. Benefits for individuals include less cancelled work, less stress, more involvement and ownership.
- The document provides an overview of Agile practices like continuous integration, user stories, short iterations and reviews, and questions whether Agile is better than traditional methods.
ALE15 The real value of a definition of done
The document discusses the value of having a Definition of Done (DoD) for software development iterations. A DoD lists all the criteria needed to consider a user story complete. This helps improve quality, deliver features faster, and minimize bugs and rework. It also provides transparency into a team's process and capabilities. The DoD should evolve over time as a team's skills improve to balance delivering quickly while maintaining quality.
Continuous Delivery in Practice (extended)
Extended version of a previously uploaded presentation:
10 practical field-proven tips for building a continuously delivered service, based on Kenshoo's experience with its RTB service - a critical, high throughput, highly available component, serving millions of requests per minute in under 50 milliseconds.
From coding practices to test automation, from monitoring tools to feature A/B testing - the entire development chain should be focused around removing blockers and manual steps between your code and your clients, without ever settling for quality. Join to see what makes our clients and developers happy and effective.
Definition of done training
This document discusses definitions of done at the sprint and release levels in Scrum. It provides examples of what could be included in a definition of done at the sprint level, such as code being complete, passing unit tests, and product owner acceptance. It distinguishes acceptance criteria, which ensures the right functionality is built, from the definition of done, which ensures quality. The document concludes by providing instructions for an exercise where a team discusses and creates their own definition of done, capturing deliverables needed at each level.
Reactjs workshop (1)
This document outlines a Reactjs workshop covering an introduction to Reactjs, its core concepts, and coding with Reactjs. The workshop introduces Reactjs as a library for building user interfaces, discusses its core concepts including components, virtual DOM, JSX, state and props, and demonstrates how to install and start coding with Reactjs. The document provides resources for further learning Reactjs.
PHX Session #3 - "It Works on My Machine!" Closing the Loop Between Developme...
The document discusses closing the loop between development and testing. It emphasizes that quality is a shared responsibility of both developers and testers. Effective communication between these teams is important, and automation can help reduce manual testing effort. The document argues that by working together and applying lessons learned through each iteration, development and testing teams can improve their process and deliver high quality software.
Using Crowdsourced Testing to Turbocharge your Development Team
Developer-owned QA testing is becoming more common as many organizations shift to leaner development processes and eschew traditional QA strategies.
This presentation discusses how crowdsourced testing can help teams offload repetitive testing work and streamline Agile testing processes. It also demonstrates how Rainforest Developer Experience (DevX) allows developers to increase productivity and minimize testing time with workflow-native crowdsourced testing.
Interested in seeing how Rainforest has helped companies save dev time and QA spend? Check out these success stories!
Guru: http://hubs.ly/H06lwC60
America's Test Kitchen: http://hubs.ly/H06lCX50
Coderetreat @ CodersTUG
This document outlines an agenda for a coderetreat event. It includes:
- An introduction that describes the event organizer and purpose of learning through sharing.
- An agenda with sessions on test-driven development, extreme programming, cost of change, simple design principles, and mechanics of TDD.
- Descriptions of pair programming, test-driven development, and the Game of Life cellular automaton that will be used in exercises.
- Logistical details like session structure, pairing rotations, and expectations around deleting code between sessions.
GG WORKSHOP GAMES & APPS IN JAVASCRIPT
The document discusses various techniques for building games and applications using JavaScript, including DOM manipulation, Canvas API, events, communication, and touch devices. It provides examples and links to resources for DOM manipulation using direct appending, document fragments, and innerHTML. It also covers topics like removing event handlers, conditional statements, and social networks APIs.
TDD and Simple Design Workshop - Session 1 - March 2019
The document discusses test-driven development (TDD) and simple design. It introduces TDD and some of its core practices, including test-driven development, simple design, refactoring, and pair programming. It provides an agenda for a workshop that will cover these topics over three sessions, including extreme programming (XP), the four elements of simple design, test doubles, outside-in TDD, and SOLID principles. The workshop aims to communicate best practices for using technical practices to succeed with agile development.
“Startup - it’s not just an IT project” - a random sampling of problems we’ve...
“Startup - it’s not just an IT project” - a random sampling of problems we’ve...MobileMonday Estonia
Taavet Tamm, Senior Dev, Fortumo: "“Startup - it’s not just an IT project” - a random sampling of problems we’ve faced so far."Implementing automation in definition of done is team effort
This document discusses implementing automation in the Definition of Done (DoD) as a team effort. It outlines some challenges, like passing tickets to the next sprint if automation is incomplete or only automating new features. It proposes having the team collectively work on automation by having QA automate new features, business analysts automate backlog items using scriptless tools, and developers support maintenance. With a team approach, more automation can be achieved to include in the DoD compared to relying only on QA efforts.
The art of not being too good at the Marshmallow test
Martin Henk, Co-Founder, Head of Product Management, Pipedrive: "The art of not being too good at the Marshmallow test"
what's blocking our way
just my experience after releasing a software and after that release i started to think how we can improve ourself more. thats what i share on this slide
QA in Agile World
This document discusses quality assurance (QA) in agile software development. It explains that in agile, QA is a continuous process integrated throughout the project lifecycle. Each iteration aims to produce potentially shippable code through practices like test-driven development, refactoring, and continuous integration which help build quality in from the start. The agile lifecycle is broken into short iterative cycles in contrast to the traditional waterfall model where testing occurs in distinct phases after coding is complete.
Dedicated QA person in scrum team
A dedicated QA person in a Scrum team can help achieve quality by focusing solely on quality assurance tasks. The document describes a scenario where one Scrum team with a dedicated QA person delivered a higher quality product than other teams without dedicated QA. Having a QA specialist allows the person to fully concentrate on test case development, automation, and testing without also having development responsibilities. This dedicated role is needed because quality assurance requires significant mental effort that may not get fully addressed if distributed among generalist team members with other priorities.
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.
Story Based Burn Down
Scrum teams use burn down chart to represent/track the iteration progress, and the most common burn down chart is the time-based one. But when doing that our team got some problems, it's not accurate to use time-based burn down to represent the true velocity and the feature completion. We experienced the situation that the team-velocity was pretty good, which means team could "burn" enough hours, while we didn't DELIVER as many feature comparing with the burn down. This topic is a case study based on what we did trying to resolve our problems.
Testing With OutSystems
This document provides an agenda for a lab on testing with OutSystems. The lab will give an overview of testing with OutSystems, introduce the BDD testing framework and Gherkin language, and include a hands-on portion. Attendees will learn about Behavior Driven Development, the OutSystems Forge Component for BDD, and how to get started using Gherkin through an interactive demo link.
Behaviour Driven Development Hands-on
This document outlines a hands-on session on behaviour driven development (BDD) that uses the "CodeBreaker" guessing game as an example. It introduces the Gherkin language for writing BDD specifications, shows examples of Gherkin features and scenarios for the CodeBreaker game, and outlines the BDD development process and coding steps. It also lists feedback from the session and resources on BDD.
Behaviour Driven Development - Beyond given when then
Behaviour Driven Development (BDD) builds upon Test Driven Development (TDD) by formalizing good habits like slicing tests vertically around user stories rather than horizontally across layers. This allows for earlier feedback. BDD expresses tests and examples using patterns like "Given, When, Then" to define the context, action, and expected outcome. It also encourages describing user interactions to enable testing through different interfaces.
More Related Content
What's hot
Dicoding Developer Coaching #38: Android | 5 Library Android yang Patut Kamu ...
Dicoding Developer Coaching merupakan webinar, yang membahas tuntas kendala maupun pertanyaan yang sering ditanyakan di Academy Dicoding.
Tema kali ini adalah "5 Library Android yang Patut Kamu Coba di 2021"
Library sering sekali membantu kita sebagai developer untuk mengembangkan aplikasi dengan lebih cepat dan efisien. Nah, di sini kita akan memilih 5 Library yang patut kamu coba di tahun 2021. Ada library yang dapat membantu dalam memanajemen log dan juga error ketika aplikasi dirilis. Ada juga library yang dapat membuat desain aplikasi menjadi lebih menarik. Selain itu, ada juga library yang dapat digunakan untuk menampilkan peta. Penasaran library apa sajakah itu? Yuk ikuti developer coaching penutup dari series Android ini.
Is Agile Better
- The document discusses the benefits of Agile development over traditional development methods. It outlines some key differences like using whole teams, short iterations with frequent feedback, and incremental design versus "big bang" development.
- Some benefits of Agile cited include higher quality, more options/flexibility, increased visibility, and higher ROI sooner. Benefits for individuals include less cancelled work, less stress, more involvement and ownership.
- The document provides an overview of Agile practices like continuous integration, user stories, short iterations and reviews, and questions whether Agile is better than traditional methods.
ALE15 The real value of a definition of done
The document discusses the value of having a Definition of Done (DoD) for software development iterations. A DoD lists all the criteria needed to consider a user story complete. This helps improve quality, deliver features faster, and minimize bugs and rework. It also provides transparency into a team's process and capabilities. The DoD should evolve over time as a team's skills improve to balance delivering quickly while maintaining quality.
Continuous Delivery in Practice (extended)
Extended version of a previously uploaded presentation:
10 practical field-proven tips for building a continuously delivered service, based on Kenshoo's experience with its RTB service - a critical, high throughput, highly available component, serving millions of requests per minute in under 50 milliseconds.
From coding practices to test automation, from monitoring tools to feature A/B testing - the entire development chain should be focused around removing blockers and manual steps between your code and your clients, without ever settling for quality. Join to see what makes our clients and developers happy and effective.
Definition of done training
This document discusses definitions of done at the sprint and release levels in Scrum. It provides examples of what could be included in a definition of done at the sprint level, such as code being complete, passing unit tests, and product owner acceptance. It distinguishes acceptance criteria, which ensures the right functionality is built, from the definition of done, which ensures quality. The document concludes by providing instructions for an exercise where a team discusses and creates their own definition of done, capturing deliverables needed at each level.
Reactjs workshop (1)
This document outlines a Reactjs workshop covering an introduction to Reactjs, its core concepts, and coding with Reactjs. The workshop introduces Reactjs as a library for building user interfaces, discusses its core concepts including components, virtual DOM, JSX, state and props, and demonstrates how to install and start coding with Reactjs. The document provides resources for further learning Reactjs.
PHX Session #3 - "It Works on My Machine!" Closing the Loop Between Developme...
The document discusses closing the loop between development and testing. It emphasizes that quality is a shared responsibility of both developers and testers. Effective communication between these teams is important, and automation can help reduce manual testing effort. The document argues that by working together and applying lessons learned through each iteration, development and testing teams can improve their process and deliver high quality software.
Using Crowdsourced Testing to Turbocharge your Development Team
Developer-owned QA testing is becoming more common as many organizations shift to leaner development processes and eschew traditional QA strategies.
This presentation discusses how crowdsourced testing can help teams offload repetitive testing work and streamline Agile testing processes. It also demonstrates how Rainforest Developer Experience (DevX) allows developers to increase productivity and minimize testing time with workflow-native crowdsourced testing.
Interested in seeing how Rainforest has helped companies save dev time and QA spend? Check out these success stories!
Guru: http://hubs.ly/H06lwC60
America's Test Kitchen: http://hubs.ly/H06lCX50
Coderetreat @ CodersTUG
This document outlines an agenda for a coderetreat event. It includes:
- An introduction that describes the event organizer and purpose of learning through sharing.
- An agenda with sessions on test-driven development, extreme programming, cost of change, simple design principles, and mechanics of TDD.
- Descriptions of pair programming, test-driven development, and the Game of Life cellular automaton that will be used in exercises.
- Logistical details like session structure, pairing rotations, and expectations around deleting code between sessions.
GG WORKSHOP GAMES & APPS IN JAVASCRIPT
The document discusses various techniques for building games and applications using JavaScript, including DOM manipulation, Canvas API, events, communication, and touch devices. It provides examples and links to resources for DOM manipulation using direct appending, document fragments, and innerHTML. It also covers topics like removing event handlers, conditional statements, and social networks APIs.
TDD and Simple Design Workshop - Session 1 - March 2019
The document discusses test-driven development (TDD) and simple design. It introduces TDD and some of its core practices, including test-driven development, simple design, refactoring, and pair programming. It provides an agenda for a workshop that will cover these topics over three sessions, including extreme programming (XP), the four elements of simple design, test doubles, outside-in TDD, and SOLID principles. The workshop aims to communicate best practices for using technical practices to succeed with agile development.
“Startup - it’s not just an IT project” - a random sampling of problems we’ve...
“Startup - it’s not just an IT project” - a random sampling of problems we’ve...MobileMonday Estonia
Taavet Tamm, Senior Dev, Fortumo: "“Startup - it’s not just an IT project” - a random sampling of problems we’ve faced so far."Implementing automation in definition of done is team effort
This document discusses implementing automation in the Definition of Done (DoD) as a team effort. It outlines some challenges, like passing tickets to the next sprint if automation is incomplete or only automating new features. It proposes having the team collectively work on automation by having QA automate new features, business analysts automate backlog items using scriptless tools, and developers support maintenance. With a team approach, more automation can be achieved to include in the DoD compared to relying only on QA efforts.
The art of not being too good at the Marshmallow test
Martin Henk, Co-Founder, Head of Product Management, Pipedrive: "The art of not being too good at the Marshmallow test"
what's blocking our way
just my experience after releasing a software and after that release i started to think how we can improve ourself more. thats what i share on this slide
QA in Agile World
This document discusses quality assurance (QA) in agile software development. It explains that in agile, QA is a continuous process integrated throughout the project lifecycle. Each iteration aims to produce potentially shippable code through practices like test-driven development, refactoring, and continuous integration which help build quality in from the start. The agile lifecycle is broken into short iterative cycles in contrast to the traditional waterfall model where testing occurs in distinct phases after coding is complete.
Dedicated QA person in scrum team
A dedicated QA person in a Scrum team can help achieve quality by focusing solely on quality assurance tasks. The document describes a scenario where one Scrum team with a dedicated QA person delivered a higher quality product than other teams without dedicated QA. Having a QA specialist allows the person to fully concentrate on test case development, automation, and testing without also having development responsibilities. This dedicated role is needed because quality assurance requires significant mental effort that may not get fully addressed if distributed among generalist team members with other priorities.
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.
Story Based Burn Down
Scrum teams use burn down chart to represent/track the iteration progress, and the most common burn down chart is the time-based one. But when doing that our team got some problems, it's not accurate to use time-based burn down to represent the true velocity and the feature completion. We experienced the situation that the team-velocity was pretty good, which means team could "burn" enough hours, while we didn't DELIVER as many feature comparing with the burn down. This topic is a case study based on what we did trying to resolve our problems.
Testing With OutSystems
This document provides an agenda for a lab on testing with OutSystems. The lab will give an overview of testing with OutSystems, introduce the BDD testing framework and Gherkin language, and include a hands-on portion. Attendees will learn about Behavior Driven Development, the OutSystems Forge Component for BDD, and how to get started using Gherkin through an interactive demo link.
What's hot (20)
Dicoding Developer Coaching #38: Android | 5 Library Android yang Patut Kamu ...
Dicoding Developer Coaching #38: Android | 5 Library Android yang Patut Kamu ...
PHX Session #3 - "It Works on My Machine!" Closing the Loop Between Developme...
PHX Session #3 - "It Works on My Machine!" Closing the Loop Between Developme...
Using Crowdsourced Testing to Turbocharge your Development Team
Using Crowdsourced Testing to Turbocharge your Development Team
TDD and Simple Design Workshop - Session 1 - March 2019
TDD and Simple Design Workshop - Session 1 - March 2019
“Startup - it’s not just an IT project” - a random sampling of problems we’ve...
“Startup - it’s not just an IT project” - a random sampling of problems we’ve...
Implementing automation in definition of done is team effort
Implementing automation in definition of done is team effort
The art of not being too good at the Marshmallow test
The art of not being too good at the Marshmallow test
Viewers also liked
Behaviour Driven Development Hands-on
This document outlines a hands-on session on behaviour driven development (BDD) that uses the "CodeBreaker" guessing game as an example. It introduces the Gherkin language for writing BDD specifications, shows examples of Gherkin features and scenarios for the CodeBreaker game, and outlines the BDD development process and coding steps. It also lists feedback from the session and resources on BDD.
Behaviour Driven Development - Beyond given when then
Behaviour Driven Development (BDD) builds upon Test Driven Development (TDD) by formalizing good habits like slicing tests vertically around user stories rather than horizontally across layers. This allows for earlier feedback. BDD expresses tests and examples using patterns like "Given, When, Then" to define the context, action, and expected outcome. It also encourages describing user interactions to enable testing through different interfaces.
Modelling by Example Workshop - PHPNW 2016
Modelling by Example is a set of practices that combine BDD (Behaviour Driven Development) and DDD (Domain Driven Design) techniques to create a workflow that directly drives code from a starting point of user requirements. We define a feature via conversation with stakeholders, capture it as automatable requirements, then express it in code using Behat and PhpSpec.
Acceptance Test Driven Development and Robot Framework
This presentation is about using Robot Framework automation test framework to implement Acceptance Test Driven Development, BDD or Specification By Example
BDD style Unit Testing
Here are some potential caveats with BDD style testing:
1. The framework can feel too "magical" if it uses too much metaprogramming under the hood. The implementation details should not be obscured.
2. Descriptions can become too vague if they only state intentions at a very high level without concrete examples. Tests as documentation only works if the descriptions are clear and specific.
3. There is a risk of duplication if contexts or examples are not properly organized and nested. Descriptions should aim to be DRY.
4. Performance overhead of the framework if it does a lot of runtime reflection or string manipulation. The framework should have a small performance footprint.
5. Tests become brittle
ATDD Using Robot Framework
Acceptance Test Driven Development (ATDD) uses examples and tests to guide development. Robot Framework is an open source test automation framework that supports the ATDD process and approach. It uses a tabular syntax to define executable tests and keywords in a simple, readable format and has a rich ecosystem of support libraries and tools.
Driving Design through Examples
Modelling by Example is a set of practices that combine BDD (Behaviour Driven Development) and DDD (Domain Driven Design) techniques to create a workflow that directly drives code from a starting point of user requirements. We will see how a simple feature can be defined via conversation with stakeholders, captured as automatable requirements, and expressed directly in the object model using tools such as Behat and PhpSpec.
Viewers also liked (7)
Behaviour Driven Development - Beyond given when then
Behaviour Driven Development - Beyond given when then
Acceptance Test Driven Development and Robot Framework
Acceptance Test Driven Development and Robot Framework
Similar to Behavior-Driven Design: One Team's Exploration
BDD Selenium for Agile Teams - User Stories
BSS using Selenium for Agile Teams - User Stories.
Presented by Ganesh Sahai at the SF Selenium Meetup on July 26, 2017.
Test Driven Development Methodology and Philosophy
A technique for building software that guides software development by writing tests. This is the philosophy and state of mind that a developer should change and start following TDD
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.
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.
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.
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.
TDD
Test Driven Development (TDD) is an approach where test cases are written before functional code to think about how components should work. It follows the principles of Red-Green-Refactor, writing a test (Red), then the functional code to pass the test (Green), then refactoring the code. TDD leads to well-designed, loosely coupled code with full test coverage that is easy to maintain and refactor with confidence in changes. While it may initially take longer, TDD finds bugs earlier and reduces bugs by 45-90%, saving significant time versus fixing issues late in development.
Bdd. Automate your requirements
This document discusses Behavior-Driven Development (BDD), which is a software engineering practice that uses concrete examples to build a common understanding of how features should be implemented to deliver business value. BDD motivates teams to specify features by working with customers to develop executable documentation in the form of acceptance tests written in a natural language format. This approach facilitates communication between technical and non-technical stakeholders and helps ensure the delivered system meets the customer's needs. Tools like Cucumber automate the execution of acceptance tests written in a behavior-driven style to help validate features and provide living documentation.
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.
Unit testing
Unit testing involves testing individual units or components of code, such as classes or methods, in isolation from the rest of the code base. A unit test asserts certain conditions or tests for specific behaviors and returns a pass/fail result. The purpose of unit testing is to validate that each piece of code works as intended, allowing code to be refactored with confidence and problems to be identified early. Best practices for unit testing include writing tests for new code, designing code for testability, and following an arrange-act-assert structure. Tests should be fast, isolated, and clearly named. Unit testing promotes code quality, documentation, and easier refactoring.
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.
Design for Testability
One reasonable definition of good design is testability. It is hard to imagine a software system that is both testable and poorly designed. It is also hard to imagine a software system that is well designed but also untestable.
I'll talk you through how bad design may affect testability. We will learn how to design robust tests which are not just increasing code coverage but are bringing real value to your project.
Finally we will explore the best way to integrate these tests to your continuous integration environment so they will be acting as top class guards against sloppy commits.
Keywords : design principles, unit tests, integration tests, stress tests, java, spring, junit @Rule, junit @Category, @RunWith, @Parameters, surefire, maven, jenkins, quality metrics, selenium , tdd, mocks, stubs, etc...
Search microservice
This document summarizes a discussion about moving a search functionality to a service at a company called GYG. It outlines the current search capabilities, considerations for the software architecture and infrastructure, and an iterative approach to implementing the first use cases. The goals are to enable more engineers to work in parallel, evolve search independently of other code, and build momentum for additional use cases in the next quarter. Principles discussed include keeping the initial implementation simple, delaying decisions, embracing change, and allowing the architecture to scale with complexity rather than planning for all possible features upfront. Feedback is requested to help the team learn.
Tdd - Test Driven Development
TDD involves writing tests before writing code to ensure code works as intended and allows for refactoring. The TDD process involves writing specifications, tests, and then code. Tests provide confidence that code works, help design better code, and act as documentation. Tests should be written even for code that currently works perfectly since requirements and needs change over time. The benefits of TDD include producing modular code that is easy to change and refactor.
Bdd in action
BDD in Action discusses how the author has implemented Behavior Driven Development (BDD) in their projects. BDD uses examples to describe software behaviors and tests scenarios first before development. The author explains how using Gherkin language and Cucumber automation tools allowed them to write acceptance criteria as examples, collaborate with business stakeholders, and develop using a test-first approach. Challenges included experimental scenario writing and appium instability, but overall BDD provided living documentation, less regression testing, and ensured development matched stakeholder expectations.
Understanding Why Testing is Importaint
The document discusses the importance of testing code through test-driven development (TDD) and behavior-driven development (BDD). It explains that TDD involves writing tests, watching them fail, making them pass, refactoring, and repeating. BDD is more complex and involves business analysts, developers, and stakeholders specifying desired behaviors as user stories. The document encourages writing unit tests because it allows for quick code changes with confidence, helps understand code design, and documents expected behavior, though it takes time initially.
Introducing BDD and TDD with Cucumber
This topic covers how business requirements are used to drive development using Behavior Driven Development (BDD) and its predecessor, Test Driven Development (TDD).
Automated Testing in Angular Slides
This document provides an overview of automated testing in AngularJS, including unit testing, end-to-end testing, and acceptance testing using tools like Protractor and CucumberJS. It discusses the benefits of automated testing such as enabling safe refactoring and reducing bugs. It then demonstrates how to set up testing frameworks like Protractor and Karma and write tests using page objects and test-driven development. The document also covers acceptance testing with CucumberJS by writing step definitions and features in Gherkin and linking them to tests.
Manual Testing real time questions .pdf
The document provides interview questions and answers related to manual testing. It is divided into 4 parts with a total of 27 questions. The questions cover topics such as the tester's role and responsibilities, software testing concepts like SDLC models, regression testing, quality assurance vs quality control, verification vs validation, and testing techniques like black box testing and white box testing. Sample scenarios are also provided to test applications like a login window, chair, mobile and a calculator.
Software Testing Basic Concepts
The document discusses testing concepts such as code with tests vs without tests, test-oriented development, and different types of testing including unit testing, integration testing, and acceptance testing. It provides examples of test-driven development (TDD) and behavior-driven development (BDD) processes. The document also discusses tips for testing, including only testing what is necessary and identifying the appropriate types of testing for an application. Frameworks and tools for test automation and continuous integration are also mentioned.
Similar to Behavior-Driven Design: One Team's Exploration (20)
Test Driven Development Methodology and Philosophy
Test Driven Development Methodology and Philosophy
Test Automation Framework using Cucumber BDD overview (part 1)
Test Automation Framework using Cucumber BDD overview (part 1)
Recently uploaded
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
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.
SMS API Integration in Saudi Arabia| Best SMS API Service
Discover the benefits and implementation of SMS API integration in the UAE and Middle East. This comprehensive guide covers the importance of SMS messaging APIs, the advantages of bulk SMS APIs, and real-world case studies. Learn how CEQUENS, a leader in communication solutions, can help your business enhance customer engagement and streamline operations with innovative CPaaS, reliable SMS APIs, and omnichannel solutions, including WhatsApp Business. Perfect for businesses seeking to optimize their communication strategies in the digital age.
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/
What is Master Data Management by PiLog Group
PiLog Group's Master Data Record Manager (MDRM) is a sophisticated enterprise solution designed to ensure data accuracy, consistency, and governance across various business functions. MDRM integrates advanced data management technologies to cleanse, classify, and standardize master data, thereby enhancing data quality and operational efficiency.
socradar-q1-2024-aviation-industry-report.pdf
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
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
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.
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
https://2024.springio.net/sessions/automated-software-refactoring-with-openrewrite-and-generative-ai/
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.
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.
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.
Energy consumption of Database Management - Florina Jonuzi
Presentation from Florina Jonuzi at the GSD Community Stage Meetup on June 06, 2024
OpenMetadata Community Meeting - 5th June 2024
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
Oracle Database 19c New Features for DBAs and Developers.pptx
Oracle Database 19c New Features for DBAs and Developers. This video you can watch from my youtube channel at https://youtu.be/m-F-mZA3MkU
What is Augmented Reality Image Tracking
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
Vitthal Shirke Java Microservices Resume.pdf
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
Microservice Teams - How the cloud changes the way we work
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
E-commerce Development Services- Hornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Recently uploaded (20)
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Empowering Growth with Best Software Development Company in Noida - Deuglo
Empowering Growth with Best Software Development Company in Noida - Deuglo
SMS API Integration in Saudi Arabia| Best SMS API Service
SMS API Integration in Saudi Arabia| Best SMS API Service
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
Automated software refactoring with OpenRewrite and Generative AI.pptx.pdf
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
Energy consumption of Database Management - Florina Jonuzi
Energy consumption of Database Management - Florina Jonuzi
Oracle Database 19c New Features for DBAs and Developers.pptx
Oracle Database 19c New Features for DBAs and Developers.pptx
Microservice Teams - How the cloud changes the way we work
Microservice Teams - How the cloud changes the way we work
Behavior-Driven Design: One Team's Exploration
- 1. Behavior-Driven Development One Team’s Exploration
- 2. Behavior-Driven Development Or… ● BDD ● Acceptance Test-Driven Development ● Specification by Example ● ...
- 3. What is BDD? ● Focuses on specifying behavior instead of writing tests ● Defines a language for writing behaviors that can be executed o Gherkin - Given-When-Then statements
- 4. Why use BDD? ● functional, end-to-end testing ● communication o with product owner o with team members ● documentation ● building the right software
- 5. What’s wrong with TDD? ● Nothing ● Reading unit-tests harder for the business
- 6. What tools & processes did we use? We were building a REST service with Java, so…cucumber-jvm with groovy. ● simplified step-definition (vs Java) Given(~'^an order with all details$') {-> @Given("^a vehicle exists$") public void a_vehicle_exists() throws Throwable {
- 7. What tools & processes did we use? ● groovy - cucumber-spring integration o wasn’t strong, but can be worked around ● Could’ve used unit testing directly Scenario: place a valid order Given an order with all details When an order is placed Then a "CREATED" response is returned And the location of the new order is returned And a confirmation number is returned And the status is "ACTIVE" def “place a valid order”() { given: “an order with all details” when: “an order is placed” then: “a CREATED response is returned” and: “the location of the new order is returned” and: “a confirmation number is returned” and: “the status is ACTIVE” }
- 8. How did it go?
- 10. Less Assumptions Clarified assumptions with the Given clauses
- 11. Reviews and Unit Testing Code review focus ● Read tests first Unit test changes ● Used the Spock given-when-then structure, often with comments, to explain the test similar to Cucumber.
- 12. Product Owner Involvement Product Owner never ended up looking at the tests
- 13. Story Breakdown Difficulty with scrum story breakdown and swarming ● Starting with Cucumber feature left us feeling constrained with how the next steps would happen. ● How to get more than two people on it and still feel effective?
- 14. Others More time consuming Not everyone likes it
- 15. What would I do differently? ● Continue working on involving product owner ● Create feature statements as part of story creation ● Demonstrate progress through test report
- 16. Summary ● BDD was a good thing ● I think we should continue the practice o though stronger business involvement is needed for it to be truly effective
- 17. Questions
Editor's Notes
- Who has heard of BDD? Who is currently using BDD?
- Other reasons?
- Points to cover: We explored this with the Spock framework Code would be between each line Text wouldn’t read as easily
- What people didn’t like: Time it takes to run tests - they are functional, so they have to set up the world Time it takes to develop Developer needing to be a tester too