EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024 
<== Date ==> <== Thread ==>
Subject: Re: Unit testing for databases
From: Simon Rose via Tech-talk <tech-talk at aps.anl.gov>
To: "Wang, Andrew" <wang126 at llnl.gov>, EPICS tech-talk <tech-talk at aps.anl.gov>
Date: Fri, 23 Sep 2022 08:40:57 +0000

Hi Andrew –

 

  1. If you look at how things are organized for EPICS base, it is most typical that the tests are in a separate directory. See for example https://github.com/epics-base/epics-base/tree/7.0/modules/libcom where you have both an src and a test directory.

    That said, I’m sure it would be fine either way; it’s more of an organizational thing.
  2. Regarding the contents and the # ADD RULES AFTER THIS LINE, they should be before that line; these are not defining new rules, but are being used by the EPICS build system to determine what to build. See again some of the examples from EPICS base above.
  3. I believe that you are correct about pdbbase.
  4. TESTFILES, as near as I can tell, is not strictly necessary unless you are working with RTEMS. Throughout all of the EPICS base tests, the only use of that variable is for RTEMS systems, and not otherwise. See https://github.com/epics-base/epics-base/blob/7.0/modules/libcom/test/Makefile#L343 for example.

 

Cheers,

 

Simon

 

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of "Wang, Andrew via Tech-talk" <tech-talk at aps.anl.gov>
Reply to: "Wang, Andrew" <wang126 at llnl.gov>
Date: Friday, 23 September 2022 at 10:02
To: EPICS tech-talk <tech-talk at aps.anl.gov>
Subject: Unit testing for databases

 

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)), 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?
  2. Do the contents of the Makefile example go after the comment, which reads # ADD RULES AFTER THIS LINE?
  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?
  4. What is the TESTFILES variable for? I couldn't find an explanation in the Application Developer's Guide.

Thank you,

Andy

References:
Unit testing for databases Wang, Andrew via Tech-talk
Navigate by Date:
Prev: Unit testing for databases Wang, Andrew via Tech-talk
Next: Re: Unit testing for databases Michael Davidsaver via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024 
Navigate by Thread:
Prev: Unit testing for databases Wang, Andrew via Tech-talk
Next: Re: Unit testing for databases Michael Davidsaver via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024