| A1: | This is really hard to answer, since as a reader of this book, you don't know the underlying architecture of XTrack. If you tried any of the exercises, though, you may have a feel for what would make it easier to test. If so, we want to hear from you! One obvious feature that would help with the automated tests is a delete function for users, stories, and so on. We have add, update, and display, but no delete. The tests that test the add functions can't clean up after themselves; we need a separate mechanism for putting the data back into the state in which we started. XTrack is written in C, and it's perfectly possible to automate the tests below the user interface, if desired. We did Exercise 19 through the user interface, because we felt the UI was fairly stable and our test framework enables us to automate quickly. |
