Skip to main content

Test Early, Test Often

  • Chapter
  • First Online:
  • 757 Accesses

Abstract

As we’ll show in this chapter, having a clear, well-defined testing process is especially important on the kinds of rapidly developed, large-team projects that Parallel Agile (PA) is often used on. In the first part of the chapter, we’ll cover some of the main reasons we recommend our particular approach to testing. After that, we’ll illustrate how to incorporate automated software testing into a PA project. To do this, we draw heavily from Matt’s own software testing process, domain-oriented testing (DOT), which just happens to be a perfect fit for PA.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   34.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   44.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD   44.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Notes

  1. 1.

    In Chap. 8, Barry identifies concurrent testing with development as a critical success factor for scalability.

  2. 2.

    Also check out Matt’s article on the subject: http://bit.ly/never-bug-free.

  3. 3.

    Acceptance tests can also cover nonfunctional requirements—for example, “The system must handle up to 1000 transactions/second as a consistent load”—though DOT is chiefly concerned with identifying functional acceptance tests. That isn’t to say that nonfunctional tests aren’t important; they’re just beyond the scope of this chapter.

  4. 4.

    Remember from Chap. 5 that user stories are requirements from the user’s perspective.

  5. 5.

    If you’re a developer and you want to know more, head over to https://www.domainorientedtesting.com/ or check out Matt’s upcoming book (likely release early 2020), unsurprisingly called Domain Oriented Testing.

  6. 6.

    Meanwhile, in a secret laboratory somewhere deep beneath the Swiss Alps the⋯is hovering

References

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2020 Springer Nature Switzerland AG

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Rosenberg, D., Boehm, B., Stephens, M., Suscheck, C., Dhalipathi, S.R., Wang, B. (2020). Test Early, Test Often. In: Parallel Agile – faster delivery, fewer defects, lower cost. Springer, Cham. https://doi.org/10.1007/978-3-030-30701-1_6

Download citation

  • DOI: https://doi.org/10.1007/978-3-030-30701-1_6

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-030-30700-4

  • Online ISBN: 978-3-030-30701-1

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics