Comprehensive checker rule listing, see also Core checker rules. More...

Public Attributes
Severity.Critical	UnitTest_Chk001
	No mix of unit tests and OTX test logic More...

Severity.Critical	UnitTest_Chk002
	Correct test case arguments More...

Severity.Critical	UnitTest_Chk003
	Correct minimal and maximal value of a range More...

Severity.Critical	UnitTest_Chk004
	Step value of a range greater than zero More...

Severity.Critical	UnitTest_Chk005
	Only one TestProcedures element per document More...

Severity.Critical	UnitTest_Chk006
	Only exist inside test procedure More...

Severity.Warning	UnitTest_Chk007
	At least one test should exist More...

Severity.Critical	UnitTest_Chk008
	Correct callback parameters More...

Severity.Critical	UnitTest_Chk009
	Only exist inside CallbackProcedure More...

Severity.Critical	UnitTest_Chk010
	Only exist inside TestProcedureRealisation or SetupProcedureRealisation More...

Detailed Description

Comprehensive checker rule listing, see also Core checker rules.

Member Data Documentation

◆ UnitTest_Chk001

Severity.Critical OpenTestSystem.Otx.Extensions.UnitTest.CheckerRule.UnitTest_Chk001

No mix of unit tests and OTX test logic

Criterion: Test procedures shall not be stored together with OTX procedures inside a PTX file.

Comment: This ensures a clear distinction between test logic and unit tests of that test logic.

◆ UnitTest_Chk002

Severity.Critical OpenTestSystem.Otx.Extensions.UnitTest.CheckerRule.UnitTest_Chk002

Correct test case arguments

Criterion: In a test case, the given arguments shall match to the corresponding test procedure parameter declaration, but only if the procedure has a realisation. This concerns parameter names as well as data types.

Comment: If the called test procedure has no realisation, the call is a NOP. In this case it is pointless to match arguments to parameters because parameters are not described yet (specification stage).

Comment: Type inference shall be supported in any depth.

◆ UnitTest_Chk003

Severity.Critical OpenTestSystem.Otx.Extensions.UnitTest.CheckerRule.UnitTest_Chk003

Correct minimal and maximal value of a range

Criterion: The Minimal value must be less than the maximum value of a range.

◆ UnitTest_Chk004

Severity.Critical OpenTestSystem.Otx.Extensions.UnitTest.CheckerRule.UnitTest_Chk004

Step value of a range greater than zero

Criterion: The step value shall be greater than zero.

◆ UnitTest_Chk005

Severity.Critical OpenTestSystem.Otx.Extensions.UnitTest.CheckerRule.UnitTest_Chk005

Only one TestProcedures element per document

Criterion: Per document only one TestProcedures element shall be exists.

◆ UnitTest_Chk006

Severity.Critical OpenTestSystem.Otx.Extensions.UnitTest.CheckerRule.UnitTest_Chk006

Only exist inside test procedure

Criterion: The unit test related activities Assume, Warning, AssertThrows, Pass, Fail, Ignore and Inconclusive may only be exists inside TestProcedureRealisation. They are not allowed to be stored together with OTX test logic.

Comment: This ensures a clear distinction between test logic and unit tests of that test logic.

◆ UnitTest_Chk007

Severity.Warning OpenTestSystem.Otx.Extensions.UnitTest.CheckerRule.UnitTest_Chk007

At least one test should exist

Criterion: A test procedure should have at least one test case or the action Assertion.Assert, Assume or Warning, ProcedureCall, the compound node AssertThrows or the end nodes Pass, Fail, Ignore or Inconclusive.

Comment: If the test procedure does not contain at least one of this elements, the test procedure will be ignored.

◆ UnitTest_Chk008

Severity.Critical OpenTestSystem.Otx.Extensions.UnitTest.CheckerRule.UnitTest_Chk008

Correct callback parameters

Criterion: The parameter declarations of a callback function shall match to the parameters of the related action.This concerns parameter names as well as data types. Furthermore, the parameter shall use the XML element with the same name.

Comment: For example, the declaration in the callback function for the parameter "title" of the ConfirmDialog action shall have the name "title" and shall be of data type "String".

Comment: OTF designer and OTL editor shall support the author to fulfil this requirement in a propitiate way.

◆ UnitTest_Chk009

Severity.Critical OpenTestSystem.Otx.Extensions.UnitTest.CheckerRule.UnitTest_Chk009

Only exist inside CallbackProcedure

Criterion: The callback related actions and terms shall only be exists inside CallbackProcedure flow.

Comment: This ensures a clear distinction between test logic and tests of that test logic.

◆ UnitTest_Chk010

Severity.Critical OpenTestSystem.Otx.Extensions.UnitTest.CheckerRule.UnitTest_Chk010

Only exist inside TestProcedureRealisation or SetupProcedureRealisation

Criterion: The simulation related actions and terms shall only be exists inside TestProcedureRealisation or SetupProcedureRealisation flows.

Public Attributes