Published online by Cambridge University Press: 10 July 2020
This chapter is about how to tell whether your program is correct. It discusses systematic testing, and how this can be automated, e.g. using a unit testing framework such as JUnit. It covers what tests you should have, and when you should write them, mentioning Test-Driven Development, an approach to programming in which you write the tests before you write the code that is to be tested. Finally it discusses property-based testing, commonly used in Haskell. In this approach you specify and test something about the relationship between the inputs and outputs of your program, and that relationship is tested on many randomly-chosen input examples.
To save this book to your Kindle, first ensure no-reply@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.
Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.
Find out more about the Kindle Personal Document Service.
To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.
To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.