A fixture for an ActionFixture table uses an actor that is started as one of the actions of the table.
The other actions that apply are enter, press, and check. These actions are mapped into corresponding methods in the actor.
Questions & Answers
Q1:
Is Fit really relevant to programmers?
A1:
Yes, most definitely. We need a concrete way of discussing what's needed with the businesspeople. We need to write the fixtures. We need to know when we're done. And we need to know the detail of what's required.
For program-level tests that are inherently tabular, Fit tables may be more convenient than using a unit testing framework, such as JUnit. ColumnFixture and RowFixture tables are more likely to be useful for such tests than are ActionFixture tables.
Q2:
How do you test through the GUI?
A2:
Avoid testing the application explicitly through the GUI. The GUI is likely to change more often than the application and so makes the tests vulnerable to change. Such tests tend to be more detailed as well. We'll say more about this in Chapter 32, when we show how a fixture may test through the GUI until the system under test has been changed to allow tests to be made directly.
Q3:
So what do you test in the GUI?
A3:
You test that the GUI itself is acting appropriately; for example, that menu items are disabled and enabled correctly, that a button click acts on the currently selected item, and so on.
Q4:
Can Fit be used for performance and stress testing?
