Description

This class contains specification for test points.

Test points are implemented as breakpoints at arbitrary points in executable, where test execution stops, expresisons can be evaluated to test target state, and variables modified to inject fault conditions. It is also possible to log values and include them to test reports.

#include <CTestPoint.h>

Inheritance diagram for isys::CTestPoint:

Public Types
enum	ETestPointSections
	Ids of test specification sections.

Public Member Functions
	CTestPoint (const CTestBaseSPtr &parent)
	Initializes new instance. More...

bool	isMerged () const
	Returns true, if the CTestSpecification section containing this object is merged. More...

const std::string	getId ()
	Returns the test point id.

iconnect::ETristate	isActive ()
	Returns true, if test point is active during test execution.

bool	isCustomActivation ()
	Returns true, if test point will not be activated before test execution, but during test execution from custom script. More...

int	getConditionCount ()
	Returns condition count for test-point.

std::string	getConditionExpr ()
	Returns condition expression for test-point.

std::string	getScriptFunctionName ()
	Returns script function to be called when test-point is hit.

CTestLocationSPtr	getLocation (bool isConst)
	Returns location of test point.

isys::CTestLogSPtr	getLogConfig (bool isConst)
	Returns logging configuration.

isys::CTestMinMaxSPtr	getHitLimits (bool isConst)
	Returns hit limits.

CTestBaseListSPtr	getSteps (bool isConst)
	Returns list of objects, which contain information about expected values and modifications of variable to perform.

void	setId (const std::string &testPointId)
	Sets the test point id.

void	setActive (iconnect::ETristate isActive)
	If parameter is `true`, then the test point is active during test execution.

void	setCustomActivation (iconnect::ETristate isActive)
	If parameter is `true`, then the test point will not be activated before test execution, but during test execution from custom script. More...

void	setConditionCount (int conditionCount)
	Sets condition count for test-point.

void	setConditionExpr (const std::string &expr)
	Sets condition expression for test-point.

void	setScriptFunc (const std::string &scriptFunc)
	Sets script function to be called when test-point is hit.

std::string	validate ()
	Validates consistency of data in object.

virtual bool	isEmpty () const
	This method returns true, if the object contains no data.

virtual void	serialize (const isys::IEmitterSPtr &emitter)
	Sends contents of this class to emitter.

virtual std::string	toString ()
	Returns object data as YAML string.

Static Public Member Functions
static CTestPointSPtr	cast (const CTestBaseSPtr &testBase)
	Casts the given object to this class. More...

Protected Member Functions
void	setStaticTagsAsConst ()
	This method is called by all objects which are immediately contained in CTestSpecification, for example CTestCoverage, CTestHIL, ...

Constructor & Destructor Documentation

◆ CTestPoint()

isys::CTestPoint::CTestPoint ( const CTestBaseSPtr & parent )

Initializes new instance.

Parameters

parent an instance of parent CTestSpecification class.

Member Function Documentation

◆ cast()

static CTestPointSPtr isys::CTestPoint::cast ( const CTestBaseSPtr & testBase )

static

Casts the given object to this class.

Returns NULL if input is NULL.

Exceptions

IllegalArgumentException if input object is not instance of this class.

◆ isCustomActivation()

bool isys::CTestPoint::isCustomActivation ( )

Returns true, if test point will not be activated before test execution, but during test execution from custom script.

This functionality can be used when the order of test point hits is known, and there are not enough hardware breakpoints available.

◆ isMerged()

bool isys::CTestPoint::isMerged ( ) const

virtual

Returns true, if the CTestSpecification section containing this object is merged.

Reimplemented from isys::CTestBase.

◆ setCustomActivation()

void isys::CTestPoint::setCustomActivation ( iconnect::ETristate isActive )

If parameter is true, then the test point will not be activated before test execution, but during test execution from custom script.

This functionality can be used when the order of test point hits is known, and there are not enough hardware breakpoints available.

Description

Public Types

Public Member Functions

Static Public Member Functions