We use cookies to distinguish you from other users and to provide you with a better experience on our websites. Close this message to accept cookies or find out how to manage your cookie settings.
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 .
To save content items to your Kindle, first ensure [email protected]
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.
The latest edition of the definitive guide to the Ada language covers the full details of the core language Ada 2012 as updated by the 2016 ISO Corrigendum and introduces the key new features in Ada 2022. The book is in four parts. It begins by introducing the fundamental concepts for newcomers, before moving onto algorithmic aspects and then structural features such as OOP and multitasking. The fourth part gives details of the standard library and interaction with the external environment. Six complete executable programs illustrate the core features of the language in action. The book concludes with an appendix focussing on the new features in Ada 2022. These new features aid program proof and the efficient use of multicore architectures.
Software testing can be regarded as an art, a craft, and a science. The practical, step-by-step approach presented in this book provides a bridge between these different viewpoints. A single worked example runs throughout, with consistent use of test automation. Each testing technique is introduced in the context of this example, helping students see its strengths and weaknesses. The technique is then explained in more detail, providing a deeper understanding of underlying principles. Finally the limitations of each technique are demonstrated by inserting faults, giving learners concrete examples of when each technique succeeds or fails in finding faults. Coverage includes black-box testing, white-box testing, random testing, unit testing, object-oriented testing, and application testing. The authors also emphasise the process of applying the techniques, covering the steps of analysis, test design, test implementation, and interpretation of results. The book's web site has programming exercises and Java source code for all examples.
Quality is an important issue for the software industry, though there is a balance between cost and quality. Starting with a few examples of software failures, this chapter discusses the need for testing, and uses an example to demonstrate why heuristics are needed to test software. A seven-step approach to testing software is introduced: analysis, identifying test coverage items and test cases, verifying the test design, implementing and executing the tests, and interpreting the test results. Key concepts are defined as used throughout the book, with a reference to the key IEEE/ISO software testing standard.
Random testing presents three main chanllenges: the test oracle problem, the test data selection problem, and the problem of when to finish testing. These are discussed in detail, and unit-test and application-test examples are worked using a simple but effective solution to these.Barriers to full automation are presented along with an overview of more advanced types of random testing. Some of the limitations are examined through the introduction of faults.
Testing with equivalence partitions introduces the reader to the first and simplest form of black-box and unit testing. First a worked example is used to demonstrate how to progress from a specification of the software to a fully automated test. The steps of the process are then examined in more detail, and the strengths and weaknesses examined through the introduction of faults into the software. The chapter ends, as do all the chapters which introduce new testing techniques, with notes for the experienced tester.
Testing object-oriented software is a significant topic in its own right, and this chapter presents the user with the essential underlying test techniques: testing in class context, and inheritance testing. As in the previous chapters, a worked example is used to introduce the reader to the concepts, which are then subsequently discussed in more detail. The chapter then summarises some more advanced techniques; state-based testing, UML-based testing, and built-in testing. Some of the limitations are examined through the introduction of faults into the working code.
Some forms of testing are significantly more time consuming to develop, and all-paths coverage is one of these. Is introduced to the reader as it is one of the most powerful forms of white-box testing, ensuring that every path from the beginning to the end of the code is exercised during testing. It is unlikely that a tester will use this technique in practice, but an understanding of this technique provides a baseline to compare other white-box tests against.