On 9/23/22 01:02, Wang, Andrew via Tech-talk wrote:
> Hi all,
>
> I am attempting to create a unit test for an IOC I had written per project specification. I have been attempting to follow the example on this Doxygen page (EPICS Base: Unit testing of record processing (anl.gov) <
https://urldefense.us/v3/__https://epics.anl.gov/base/R7-0/6-docs/doxygen/dbunittest.html__;!!G2kpM7uM-TzIFchu!gLi2eI6CwW4YBoHkox7lDvPUMsGc97vMbGDetU5i6VR8dd3qQ7tKd3TXmlKv_yeTVa8$
>), however I seem to have hit a road block. My questions are below.
>
> 1. In the Makefile example, are those variables for the Makefile inside the app/src directory of an IOC application?
I typically put tests in another directory, although is no necessary.
TESTPROD executables are only special in that they are not installed.
> 2. Do the contents of the Makefile example go after the comment, which reads # ADD RULES AFTER THIS LINE?
Like most assignments, put them after
> include $(TOP)/configure/CONFIG
and before
> include $(TOP)/configure/RULES
> 3. Is pdbbase the same global variable as described in Chapter 14 which is titled "Static Database Access"? If so, then I would need to include dbAccess.h?
Yes, and Yes.
> 4. What is the TESTFILES variable for? I couldn't find an explanation in the Application Developer's Guide.
This is used to capture files which are read by test executables.
Currently only used when running tests on RTEMS/vxWorks.