Tag: Agile Team

Given-When-Then | Glossary

Diwakar Varadharajan Leave a comment

Definition
It is a template/ format specified to facilitate the writing of acceptance tests for a User Story. The test cases can be tested manually, or as browser tests with Selenium.

  • Given: Specifies the context
  • When: The action that needs to be carried out
  • Then: A set of observable results that are obtained as a result of actions taken.

Origin
 Given-When-Then was invented by Dan North as a part of Behavior-Driven Development.

Further Reading

  • “Specification by Example: How Successful Teams Deliver the Right Software“, by Gojko Adzic.
  • “Feature Injections: Three Steps to Success”, by Chris Matts and Gojko Adzic.
  • “Introducing BDD”, by Dan North.

Know more about Given-When-Then by visiting our website.

Features | Glossary

Diwakar Varadharajan Leave a comment

Definition

A feature is an attribute of a software product or system. Features are large and complex, and comprise many unit requirements. A feature, is usually implemented through many user stories. Features may be functional or non-functional; they provide the basis for organizing stories.

People usually end up confusing the terms “Feature” and “User Story” in Agile Software Development. This can be avoided, as the difference is very simple: A feature is a collection of User stories, i.e. it’s implemented through many user stories.

Origin

1350–1400; 1905–10 for def 3; Middle English phrase “feture” < Anglo-French, Middle-French phrase “faiture” < Latin “factūra . Predominantly used in software development from late 1980s.

Know more about Features by visiting our website.