ACTF Runtime

The Runtime View controls states of the validation process during an Inter-JVM (Internal) AOP-based validation launched from either the Java Application with ACTF or Eclipse Application with ACTF launch configurations.

picture of the ACTF Runtime View with the default values

Notice that each toggle may be checked or unchecked and each toggle has a message for each of these states. This message gives more information about the state of the validation process.

The following table describes each toggle available in the view:

Toggle Description Default
Perform validation

When checked, ACTF is validating the GUI launched from either the Java or Eclipse Application with ACTF launch configuration. Think of this toggle as a start/stop validation switch for ACTF. The toggle is useful for larger applications in which a validation of the entire application is not necessary; validations can be enabled when desired, and haulted for parts of the application that need not be validated.

checked
Validate hidden

When checked, ACTF will validate hidden components, components that may not be visible on the screen and that may have their visibility property set to false. It is usually most useful to disable this toggle as the validation of components that are visible (and, hence, navigable) are typically most interesting.

unchecked
Revalidate components

When checked, ACTF will re-validate GUI component instances that have previously been validated. Whether or not a GUI component has been validated depends upon whether ACTF has encountered the hash code of the component as returned by System.identityHashCode. Thus, a GUI component that is garbage collected and re-instantiated (say, a Find dialog in an application) will always be revalidated regardless of the state of this toggle. On the other hand, a component that is merely hidden and then reshown will not be re-validated if this toggle is checked.

checked