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 IOCs and databases |
From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Stainer Tom <Tom.Stainer at sckcen.be> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Tue, 7 Sep 2021 15:39:29 +0000 |
Hi Tom,
This is covered in the documentation/Doxygen annotation comments.
Providing the test count is optional, but it’s there so the harness can detect if the test program crashes before it has completed all of the tests. During test program development you can call
testPlan(0) at the start and everything will work just fine, but we recommend that you fill in the count once you’ve finished adding tests or you can miss out on the check that it did actually run all of them. This also encourages
you to ensure that every test reports a single pass or fail result
An old parser for the TAP format for the Jenkins CI software didn’t originally check the count at all, and we had several occasions where a test seg-faulted on one architecture but the job passed because the parser didn’t realize there was a problem.
HTH,
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|