Loading...

Follow Hiptest Blog on Feedspot

Continue with Google
Continue with Facebook
or

Valid

Behavior-driven development, or BDD, is all about improving communication between business and technical teams. The goal is to shorten feedback cycles and eliminate misunderstood or vague requirements using real-world examples. These examples describe how software should behave in the eyes of a user rather than how it should work on a technical level. The process starts with a deliberate discovery...

Source

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Many developers feel the benefits of behavior-driven development (BDD) and test-driven development (TDD). There are fewer ambiguous requirements, late nights troubleshooting errors or deploys that have everyone on edge. Everything runs better when business and technical teams are on the same page. The problem is that it’s challenging to quantify these benefits. Without demonstrating a return on...

Source

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Behavior-driven development, or BDD, is all about improving communication between business and technical teams. The goal is to shorten feedback cycles and eliminate misunderstood or vague requirements using real-world examples. These examples describe how software should behave in the eyes of a user rather than how it should work on a technical level. The process starts with a deliberate discovery...

Source

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Many developers feel the benefits of behavior-driven development (BDD) and test-driven development (TDD). There are fewer ambiguous requirements, late nights troubleshooting errors or deploys that have everyone on edge. Everything runs better when business and technical teams are on the same page. The problem is that it’s challenging to quantify these benefits. Without demonstrating a return on...

Source

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Test-driven and behavior-driven development, also known as TDD and BDD, often involve trade-offs between development time, software quality and test performance. These trade-offs are often questioned the most when testing non-functional requirements, or NFRs, since they involve a greater level of uncertainty than traditional functional requirements. Many development teams aren’t even sure if they...

Source

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Almost 1 year after HipTest joined SmartBear, Cucumber Ltd. has been acquired by SmartBear. Today is an exciting day for us. We’re happy to announce that SmartBear has acquired Cucumber Ltd. For BDD lovers, you probably already know Cucumber. With more than 30 million downloads and nearly a million users, Cucumber is the leader in Behavior-Driven Development (BDD) training and evangelism...

Source

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Behavior-driven development, or BDD, has become very popular over the past several years. While it’s easy to gather around the table and come up with Given-When-Then scenarios, going through the motions doesn’t necessarily lead to tangible benefits. Defining solid metrics and making progress visible is necessary to truly realize the benefits of BDD. In this article, we will take a closer look at...

Source

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Many developers treat behavior-driven development (BDD) like test-driven development (TDD). Rather than using it as an opportunity to communicate with product owners, they write the tests in isolation and then write the code necessary to make the tests pass — the same as they would with TDD tests. If you treat BDD like TDD, then you’re probably missing out on most of the benefits.

Source

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Test-driven and behavior-driven development, also known as TDD and BDD, often involve trade-offs between development time, software quality and test performance. These trade-offs are often questioned the most when testing non-functional requirements, or NFRs, since they involve a greater level of uncertainty than traditional functional requirements. Many development teams aren’t even sure if they...

Source

  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

The beginning of any software project is full of unknowns. While it’s important to have a vision, the initial product backlog is little more than a list of assumptions that must be validated and refined using feedback from customers and users. Grooming, or refinement, is the process of updating the product backlog based on feedback or changing requirements. For example, a team might remove...

Source

Read for later

Articles marked as Favorite are saved for later viewing.
close
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Separate tags by commas
To access this feature, please upgrade your account.
Start your free month
Free Preview