We use our calibrated ABM and our AI algorithm to make case-by-case predictions of outcomes in new out-of-sample test data. These predictions concern: the full partisan composition of the cabinets which form, participation by particular parties in the cabinets which form, and the observed durations of the cabinet which forms. Absent a baseline model of government formation in such complex settings against which we can evaluate our results, we compare success rates with those of a prediction of minimal winning coalitions which is common to a large number of existing studies. Bearing in mind that the ABM in particular generates probability distributions of predicted outcomes in each case, which we feel is substantively realistic, while only a single outcome can be observed, we are very satisfied with the predictive accuracy of the model. Successful predictions relating to cabinet durations are particularly distinctive to the model, deriving from the model-predicted number of issues tabled in formation negotiations, and the model-predicted likelihood than a random shock will create a situation in which a majority of legislators now prefer some alternative to the incumbent.

This chapter focuses on the scope and content of the Intellectual Property Chapter of the TPP, to examine how strict the new IP international protection and enforcement standard is, and to determine how far it goes beyond the existing FTAs and TRIPS. TPP provisions are compared with the “Pre-TPP relevant standards” (both intra-TPP and extra-TPP), and, of course, the WTO TRIPS Agreement. We looked at the NAFTA (the US, Canada, and Mexico) and the US agreements with Singapore, Chile, Australia, the CAFTA countries, Peru, and Korea (KORUS FTA). Some references were made to agreements signed by the European Union with Korea (EU--KOREA FTA) and the one with Canada, the Comprehensive Economic and Trade Agreement (CETA), as well as to the TPP predecessor -- the P4 Agreement -- signed between Brunei Darussalam, Chile, New Zealand, and Singapore. While reviewing the enforcement provisions, comparisons were made to the Anti-Counterfeiting Trade Agreement (ACTA).

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.

Building on the knowledge gained in chapter 1, this chapter explains the next form of black-box testing, based on the boundary values of each equivalence partition.

As an introduction to white-box testing, the first technique presented shows how to identify lines of code that have not been executed during testing, and how to develop additional tests to ensure that they produce the correct results when executed.

Application testing is often emphasised in practice, as it ensures that an entire software system works for a user. However, this is substantially more complex than unit-testing, so this topic is addressed after the underlying concepts have been introduced in the previous chapters. As for object-oriented testing, this is a significant topic, and the reader is introduced to the common form used in practice: user-story testing. A worked example is used to present the techniques involved to analyse the software interface and produce a fully automated set of tests for a web-based application. A more detailed analysis follows, identifying many of the more difficult problems that an application tester will experience.

There is a subtle distinction between statements in a program, and the branches between those statements. Even with full statement coverage, faults may remain. This chapter presented shows how to identify branches in the code that have not been taken during testing, and how to develop additional tests to ensure that they produce the correct results when they are taken.

Combinations of different inputs, when not correctly handled, are a frequent cause of faults in software. Decision tables allow the tester to identify these combinations, and further improve the test coverage. Building on the knowledge gained in the previous chapters, this chapter explains how to identify casues and effects, build a decision table, and then use the rules in the table to develop test cases and automated tests.