Doc:latest/taeguide/testintg - Revision history

Stone: /* Stub */

2013-03-13T18:13:57Z

‎Stub

Stone: /* Stub3 */

2013-03-13T18:13:29Z

‎Stub3

Stone: /* Stub4 */

2013-03-13T18:10:14Z

‎Stub4

Stone: /* Stub5 */

2013-03-13T18:09:56Z

‎Stub5

Stone: /* Stub2 */

2013-03-13T17:59:34Z

‎Stub2

Stone: /* Stub1 */

2013-03-13T17:59:18Z

‎Stub1

Bot: 1 revision

2011-10-24T19:05:46Z

1 revision

Senthilk at 05:07, 27 August 2010

2010-08-27T05:07:40Z

New page

=== Integration ===

After you have created the model using IDE and generated the source, add a "test" directory just below the model's root (as a peer to "app") and make subdirectories below "test" for your major functional blocks.

==== Python TAE Interface ====
The python testcase files should be present in "<model>/src/test" directory. Since you are probably already programming your test cases in Python using our testcase framework, nothing further need be done.

==== C TAE Interface ====
The Python "layer" for an exclusively "C" implementation is simple :

<pre>
import openclovis.test.testcase as testcase

class test(testcase.TestGroup):

def test_sg006(self):
r"""
\testcase BIC-UTL-BIT.TG001
\brief Test group based on SG "tcSg005Bitmap"
"""
# List of service groups to unlock, Maximum time (in seconds) that the test takes to run
self.run_sg_based_test(['tcSg005Bitmap'], 60)

</pre>

This python file should be present in "<model>/src/test" directory.

You also need to add some test initialization code in clCompAppMain.c of the component. Here is an example of what all you need to initialize/register :

===== Stub1 =====
In the global context of the file clCompAppMain.c, you need to add following code with BEGIN/END block :
<pre>
/*
* ---BEGIN_APPLICATION_CODE---
*/

int
clTestBitmapRun(ClTcParamListT *param_list)
{
clTestBitmapMain();
return 0;
}

void*
clTcRunThread(void *param)
{
clTcRun();
return NULL;
}

/*
* ---END_APPLICATION_CODE---
*/
</pre>

*Where, clTestBitmapMain() is the main test function (where all the test cases will start their execution). The example code for this function is present in "Testcase Implementation" section.

===== Stub2 =====
In main() function, TC initialize should be done in following way :
<pre>
/*
* Do the application specific initialization here.
*/

/*
* ---BEGIN_APPLICATION_CODE---
*/
rc = clTcInitialize("Bitmap Utility", "BIT", clTestBitmapRun);
if(CL_OK != rc)
{
clprintf(CL_LOG_SEV_ERROR, "clTcInitialize() failed, rc : 0x%x", rc);
return rc;
}

/*
* ---END_APPLICATION_CODE---
*/
</pre>

===== Stub3 =====
Before blocking on AMF file descriptor for callbacks, in main() function a thread should be created to run the test in the thread context. Alternatively, you can block on the AMF file descriptor in another thread and let the test run in main thread.

<pre>
/*
* ---BEGIN_APPLICATION_CODE---
*/
rc = clOsalTaskCreateDetached(NULL, CL_OSAL_SCHED_OTHER,
CL_OSAL_THREAD_PRI_NOT_APPLICABLE,
CL_OSAL_MIN_STACK_SIZE,
clTcRunThread, NULL);

/*
* ---END_APPLICATION_CODE---
*/

/*
* Block on AMF dispatch file descriptor for callbacks
*/
</pre>

===== Stub4 =====
In clCompAppTerminate() finalize the TC in following way :

<pre>
/*
* ---BEGIN_APPLICATION_CODE---
*/
clTcFinalize();

/*
* ---END_APPLICATION_CODE---
*/
</pre>

===== Stub5 =====
In clCompAppAMFCSISet(), call TC activate in SA_AMF_HA_ACTIVE context :

<pre>
switch ( haState )
{
case SA_AMF_HA_ACTIVE:
{
/*
* AMF has requested application to take the active HA state
* for the CSI.
*/

/*
* ---BEGIN_APPLICATION_CODE---
*/
clTcActivate((ClAmsCSIDescriptorT*)&csiDescriptor, haState);

/*
* ---END_APPLICATION_CODE---
*/

</pre>

@@ Line 29: / Line 29: @@
 You also need to add some test initialization code in clCompAppMain.c of the component. Here is an example of what all you need to initialize/register :
-===== Stub =====
+===== The "C" Code =====
 Define all your tests inside a function that can be called in a thread:
 <pre>

← Older revision		Revision as of 18:13, 13 March 2013
Line 28:		Line 28:

	You also need to add some test initialization code in clCompAppMain.c of the component. Here is an example of what all you need to initialize/register :		You also need to add some test initialization code in clCompAppMain.c of the component. Here is an example of what all you need to initialize/register :
−
−	~~===== Stub3 =====~~
−	Before blocking on AMF file descriptor for callbacks, in main() function a thread should be created to run the test in the thread context. Alternatively, you can block on the AMF file descriptor in another thread and let the test run in main thread.
−
−	~~<pre>~~
−	/*
−	* ---BEGIN_APPLICATION_CODE---
−	*/
−	~~rc = clOsalTaskCreateDetached(NULL, CL_OSAL_SCHED_OTHER,~~
−	~~CL_OSAL_THREAD_PRI_NOT_APPLICABLE,~~
−	~~CL_OSAL_MIN_STACK_SIZE,~~
−	~~clTcRunThread, NULL);~~
−
−	/*
−	* ---END_APPLICATION_CODE---
−	*/
−
−	/*
−	* Block on AMF dispatch file descriptor for callbacks
−	*/
−	~~</pre>~~

	===== Stub =====		===== Stub =====

@@ Line 64: / Line 64: @@
 </pre>
-===== Stub5 =====
+===== Stub =====
-In clCompAppAMFCSISet(), call TC activate in SA_AMF_HA_ACTIVE context :
+Define all your tests inside a function that can be called in a thread:
 <pre>
     switch ( haState )
+     {
@@ Line 76: / Line 91: @@
               * for the CSI.
               */
-            /*
+         /* Spawn a thread that runs your test.
-             * ---END_APPLICATION_CODE---
+            you may choose to use the Posix compliant pthread_create function.
-             */
+            Here we are using the equivalent SAFplus function
+            (interoperability wrapper)  */
 </pre>

← Older revision		Revision as of 17:59, 13 March 2013
Line 28:		Line 28:

	You also need to add some test initialization code in clCompAppMain.c of the component. Here is an example of what all you need to initialize/register :		You also need to add some test initialization code in clCompAppMain.c of the component. Here is an example of what all you need to initialize/register :
−
−	~~===== Stub2 =====~~
−	~~In main() function, TC initialize should be done in following way :~~
−	~~<pre>~~
−	/*
−	* Do the application specific initialization here.
−	*/
−
−	/*
−	* ---BEGIN_APPLICATION_CODE---
−	*/
−	~~rc = clTcInitialize("Bitmap Utility", "BIT", clTestBitmapRun);~~
−	~~if(CL_OK != rc)~~
−	{
−	~~clprintf(CL_LOG_SEV_ERROR, "clTcInitialize() failed, rc : 0x%x", rc);~~
−	~~return rc;~~
−	}
−
−	/*
−	* ---END_APPLICATION_CODE---
−	*/
−	~~</pre>~~

	===== Stub3 =====		===== Stub3 =====

← Older revision		Revision as of 17:59, 13 March 2013
Line 28:		Line 28:

	You also need to add some test initialization code in clCompAppMain.c of the component. Here is an example of what all you need to initialize/register :		You also need to add some test initialization code in clCompAppMain.c of the component. Here is an example of what all you need to initialize/register :
−
−	~~===== Stub1 =====~~
−	~~In the global context of the file clCompAppMain.c, you need to add following code with BEGIN/END block :~~
−	~~<pre>~~
−	/*
−	* ---BEGIN_APPLICATION_CODE---
−	*/
−
−	~~int~~
−	~~clTestBitmapRun(ClTcParamListT *param_list)~~
−	{
−	~~clTestBitmapMain();~~
−	~~return 0;~~
−	}
−
−	void*
−	~~clTcRunThread(void *param)~~
−	{
−	~~clTcRun();~~
−	~~return NULL;~~
−	}
−
−	/*
−	* ---END_APPLICATION_CODE---
−	*/
−	~~</pre>~~
−
−	*Where, clTestBitmapMain() is the main test function (where all the test cases will start their execution). The example code for this function is present in "Testcase Implementation" section.

	===== Stub2 =====		===== Stub2 =====

@@ Line 47: / Line 47: @@
      /*
       * Block on AMF dispatch file descriptor for callbacks
       */
 </pre>