• Complain

John Ferguson Smart - BDD in Action: Behavior-driven development for the whole software lifecycle

Here you can read online John Ferguson Smart - BDD in Action: Behavior-driven development for the whole software lifecycle full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2014, publisher: Manning Publications, genre: Romance novel. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:

Romance novel Science fiction Adventure Detective Science History Home and family Prose Art Politics Computer Non-fiction Religion Business Children Humor

Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.

John Ferguson Smart BDD in Action: Behavior-driven development for the whole software lifecycle
  • Book:
    BDD in Action: Behavior-driven development for the whole software lifecycle
  • Author:
  • Publisher:
    Manning Publications
  • Genre:
  • Year:
    2014
  • Rating:
    4 / 5
  • Favourites:
    Add to favourites
  • Your mark:
    • 80
    • 1
    • 2
    • 3
    • 4
    • 5

BDD in Action: Behavior-driven development for the whole software lifecycle: summary, description and annotation

We offer to read an annotation, description, summary or preface (depends on what the author of the book "BDD in Action: Behavior-driven development for the whole software lifecycle" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.

Summary

BDD in Action teaches you the Behavior-Driven Development model and shows you how to integrate it into your existing development process. First youll learn how to apply BDD to requirements analysis to define features that focus your development efforts on underlying business goals. Then, youll discover how to automate acceptance criteria and use tests to guide and report on the development process. Along the way, youll apply BDD principles at the coding level to write more maintainable and better documented code.

Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications.

About the Technology

You cant write good software if you dont understand what its supposed to do. Behavior-Driven Development (BDD) encourages teams to use conversation and concrete examples to build up a shared understanding of how an application should work and which features really matter. With an emerging body of best practices and sophisticated new tools that assist in requirement analysis and test automation, BDD has become a hot, mainstream practice.

About the Book

BDD in Action teaches you BDD principles and practices and shows you how to integrate them into your existing development process, no matter what language you use. First, youll apply BDD to requirements analysis so you can focus your development efforts on underlying business goals. Then, youll discover how to automate acceptance criteria and use tests to guide and report on the development process. Along the way, youll apply BDD principles at the coding level to write more maintainable and better documented code.

No prior experience with BDD is required.

Whats Inside

  • BDD theory and practice
  • How BDD will affect your team
  • BDD for acceptance, integration, and unit testing
  • Examples in Java, .NET, JavaScript, and more
  • Reporting and living documentation

About the Author

John Ferguson Smart is a specialist in BDD, automated testing, and software lifecycle development optimization.

Table of Contents

    PART 1: FIRST STEPS
  1. Building software that makes a difference
  2. BDDthe whirlwind tour
  3. PART 2: WHAT DO I WANT? DEFINING REQUIREMENTS USING BDD
  4. Understanding the business goals: Feature Injection and related techniques
  5. Defining and illustrating features
  6. From examples to executable specifications
  7. Automating the scenarios
  8. PART 3: HOW DO I BUILD IT? CODING THE BDD WAY
  9. From executable specifications to rock-solid automated acceptance tests
  10. Automating acceptance criteria for the UI layer
  11. Automating acceptance criteria for non-UI requirements
  12. BDD and unit testing
  13. PART 4: TAKING BDD FURTHER
  14. Living Documentation: reporting and project management
  15. BDD in the build process

John Ferguson Smart: author's other books


Who wrote BDD in Action: Behavior-driven development for the whole software lifecycle? Find out the surname, the name of the author of the book and a list of all author's works by series.

BDD in Action: Behavior-driven development for the whole software lifecycle — read online for free the complete book (whole text) full work

Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "BDD in Action: Behavior-driven development for the whole software lifecycle" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.

Light

Font size:

Reset

Interval:

Bookmark:

Make
BDD in Action: Behavior-Driven Development for the whole software lifecycle
John Ferguson Smart

BDD in Action Behavior-driven development for the whole software lifecycle - image 1

Copyright

For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact

Special Sales Department Manning Publications Co. 20 Baldwin Road PO Box 761 Shelter Island, NY 11964 Email: orders@manning.com

2015 by Manning Publications Co. All rights reserved.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher.

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps.

Picture 2 Recognizing the importance of preserving what has been written, it is Mannings policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15 percent recycled and processed without the use of elemental chlorine.

Picture 3Manning Publications Co.20 Baldwin RoadPO Box 761Shelter Island, NY 11964Development editor: Dan MaharryTechnical development editor Ray LugoCopyeditor: Benjamin BergProofreaders: Andy Carroll, Melody DolabTypesetter: Dennis DalinnikCover designer: Marija Tudor

ISBN: 9781617291654

Printed in the United States of America

1 2 3 4 5 6 7 8 9 10 EBM 19 18 17 16 15 14

Brief Table of Contents
Table of Contents
Deliberate DiscoveryA Sonnet
Uncertaintys the muse of all thats new,And ignorance the space in which she plays;A years enough to prove a vision true,But we could prove it false in only days.We dream, and chase our dream, and never fearTo fail, and fail. Up, up! And on again,But ask us to pursue anothers goalsAnd failure makes us mice where we were men.Ah, best laid plans! Where were you at the endWho chained us and constrained us from the start?We knew you made a fickle, fragile friend;You tricked us when you claimed you had a heart!We thought less travelled roads would see us winningIn places other fools had feared to strayIf only we had known from the beginningThe ignorance we found along the way.And yet, a list of dangers and disastersFilled out, and scanned, and added to some moreWould still have left out some of what we masteredWe didnt know we didnt know before.We planned our way with maps wed made alreadyAssuming the terrain would be the same,Expecting well-paved roads to keep us steadyAnd any local creatures to be tame.We loaded up our caravans and wagonsWith good advice, best practices and toolsBut didnt spot the legendHere be dragons!So we got burnt, again. They say that foolsRush in, and yet we count ourselves as wise,We praise each others skill and raise a glassTo intellectignoring the demiseOf expeditions just as skilled as ours.When they return, worn out, their pride in shreds,We laugh and say, A death march! You expectSuch things to fail. And in our clever headsIts obviousat least in retrospect.The dragons of our ignorance will slay usIf we dont slay them first. We could be braveAnd work for kings who dont refuse to pay usWhen were delayed because we found their cave.They say that matter cannot be created,A fundamental principle and law,While dragons keep emerging, unabated;As many as you slay, theres still one more.Our ignorance is limitlessbe grateful,Or else wed find weve nothing left to learn;To be surprised by dragons may be fateful,But truth be told, its best laid plans that burn.We could seek out the dragons in their dungeonsAnd tread there softly, ready to retreat;We could seek other roads, postponing large ones,And only fight the ones we might defeat.The world could be a world of dragon slayersAnd stand as men and women, not as mice;The joy that comes from learning more should sway us;The fiercest dragons wont surprise us twice.Discover tiny dragons, be they few,And all the mightiest, with equal praiseUncertaintys our muse of all thats new,And ignorance the space in which she plays.

Liz Keogh

Foreword

Since its modest beginnings as a coaching experiment over a decade ago, Behavior-Driven Development (BDD) has taken off in a way I never would have imagined. Id like to tell you how it started, and why I believe it is more relevant today than it has ever been.

When I first started working on BDD back in 2003, the software industry was going through a revolution. It was a time of possibility, with everything I knew about enterprise software delivery open to question. Two years earlier, a group of software professionals had come together to formulate the Agile Manifesto, and the year after that, in 2002, I was fortunate enough to join some of the pioneers of this new movement. In April of that year, I was hired in the newly opened London office of ThoughtWorks, Inc., a software consulting company at the forefront of the agile movement. Their chief scientist Martin Fowler was one of the signatories of the Agile Manifesto and a few years earlier had written Refactoring (Addison-Wesley Professional, 1999), which had a profound effect on how I thought about software. He was also on the first XP project at Chrysler with Kent Beck and Ward Cunningham. It is safe to say his agile credentials are pretty solid, and he had joined the team at ThoughtWorks because they worked in a way that resonated with those values.

At this point I was over ten years into my career and I thought I was a decent programmer. That didnt last very long. I was constantly amazed by the talent of the people I was working with and the game-changing nature of the things I was encountering, things we now take for granted. My first tech lead turned out to have invented continuous integration, which would have been even more intimidating if he hadnt been such a thoroughly nice guy. That seemed to be a common theme among the early agilists. They were without exception generous with their knowledge, generous with their time, and humble about their discoveries and achievements.

I had some great mentors in my early years at ThoughtWorks. I was encouraged to try things Id never done beforecoaching skeptical programmers, reaching out to anxious testers, and engaging with suspicious business folks. This, then, was the context in which BDD was born. It was a response to a triple conundrum: programmers didnt want to write tests; testers didnt want programmers writing tests; and business stakeholders didnt see any value in anything that wasnt production code. I didnt think I was inventing a methodologyI was just trying to teach TDD to a bunch of programmers without scaring off the testers.

Next page
Light

Font size:

Reset

Interval:

Bookmark:

Make

Similar books «BDD in Action: Behavior-driven development for the whole software lifecycle»

Look at similar books to BDD in Action: Behavior-driven development for the whole software lifecycle. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.


Reviews about «BDD in Action: Behavior-driven development for the whole software lifecycle»

Discussion, reviews of the book BDD in Action: Behavior-driven development for the whole software lifecycle and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.