The heklp files will tell you this:
</font><blockquote><font size="1" face="Verdana, Arial, Helvetica">code:</font><hr /><pre style="font-size:x-small; font-family: monospace;">An appstate declares an application state.
An application state is typically used to put an
application into the state it should be in at
the start of a testcase.
You can define the application state from scratch
or base the definition on another application
state, which in turn can be based on another
application state, and so on. The base state is
the lowest level of application state in this
chain of inheritance. The application state
DefaultBaseState is predefined for your use by
SilkTest.</pre><hr /></blockquote><font size="2" face="Verdana, Arial, Helvetica">And there's loads more about it.
Actually, I avoid appstates. Segue's philosophy seems to be to drive the application to a certain state, perform test and then clean up.
I prefer to clean up at the start, then drive the application to a certain state and then perform test.
This way has lead to more robust system for me, with fewer cascading failures.
What state of an application can SilkTest record?
Size, location, or customized tool bar?
If yes, and some application have this function themselves.
What SilkTest point at is those have no this function. Am I right?
I wanna know the use of "appstate".
You might want to take a quick look at UML (Unified Modeling Language). That would help your understanding of state machines and their meaning. Personally, I don't really use appstates in Silk, but I think it is necessary to understand them in order to disable them, too! I personally base my testcases on an appstate which is basedon none to eliminate extra code running that I don't want.
Chris R Mead
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.