Can you explain why eValid doesn't have an "assert" command?
Great question BForrest.
Actually, eValid has a LOT of kinds of "assert" -- which we call validations!
Because eValid is intended to be a regression test tool the working assumption is that tests will 99% of the time PASS.
So, this working assumption translates into a system in which, so long as everything checks out, you don't need to do anything but continue the test.
When a test does fail, eValid throws a flag for an Alarm, an Error, a Timeout, or a Warning.
The flags are processed by the most-recently executed commands that specify what to do in case these are invoked:
These four have the GoScript, Email, or SendFile options.
So, you can set eValid up so that when an Error (a FAIL) happens you send an email to someone (management?) about the Error.
See the online documentation in the section of Flag Processing Commands for complete details.
-- eValid Support