|
|
|
|
|
|
|
|
|
|
- Operating mode
- Managing assertions
TestCheckNotNull (Function) In french: TestVérifieNonNull Checks whether an expression is not Null in assertive programming and in automated test mode. ElementArray is dynamic array of MyClass
// Fill the array
...
// Browse the array elements
FOR I = 1 _TO_ ElementArray.Count
// The element should be allocated
TestCheckNotNull(ElementArray[I], "The object #%1 was not allocated", I)
// Process the element
...
END
Syntax
TestCheckNotNull(<Expression> [, <Comments> [, <Parameter 1> [... [, <Parameter N>]]]])
<Expression>: Character string Expression that must be checked. <Comments>: Character string Character string in the format defined by StringBuild. <Parameter 1>: Any type First parameter expected by <Comments>. <Parameter N>: Any type Last parameter expected by <Comments>. Remarks Operating mode When the expression is Null:   in automated test mode, an error is added to the test status report (equivalent to TestWriteResult). - in manual test mode, an assertion is displayed (equivalent to dbgAssert).
- in runtime mode, an assertion is displayed if the assertions have been enabled (equivalent to dbgAssert).
When running an application, the expression is not evaluated if the assertions are not enabled. dbgOnError allows you to automatically start a WLanguage procedure used to retrieve the comment linked to the error.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|