Do a search on regular expression in the archive and you will come up with some material that will help you... I had the same question not too long ago.
Quality is the result of a carefully constructed cultural environment. It has to be the fabric of the organization, not part of the fabric.
There's "usercheck" procedure for entering results in the test log. You can also trigger a runtime error by Err.Raise. We use exclusively these two since checks are too inflexible for our needs. So when we want to know if an editbox has a certain value, insted of creating a check we use compare value of Editbox.Text and the expected value. If they won't match we report an error using usercheck.
Basing my experiences from Rational Visual Test, I am finding some aspects of TestPartner rather daunting, so I was hoping that some members of this community could help me.
Part of the software that I am testing involves checking components that TestPartner currently does not list in its "Check Wizard"--e.g., examining the contents of files.
Would anyone know of a way to hook in a procedure as such into TestPartner's Check mechanism, as to make such an operation appear in the TestLog as a pass or a fail? Basically, be there any quick-and-easy way to create checks that do not exist in the "Check Wizard?"
p.s. - Has TestPartner any regular expressions capability in terms of matching or searching for windows?