On Thu, Oct 29, 2015 at 11:42:58PM +0100, Kornel Benko wrote: > Am Donnerstag, 29. Oktober 2015 um 22:26:27, schrieb Georg Baum > <georg.b...@post.rwth-aachen.de> > > Scott Kostyshak wrote: > > > > > Please let me know if there is anything else specifically that I should > > > document regarding the export tests. I will try to keep updating this > > > file. > > > > Very good! I have one question: While investigating the language nesting > > stuff further I found already a nesting bug which is also in 2.1 (and fixed > > it locally). Running even a subset of the export tests is not really > > practical in thise case, but since this code is so complicated I cannot > > change it without testing a lot. > > > > Therefore I would like to create some specific test cases for language > > nesting. Pure export tests would be fine for now, we could still add a > > comparison of the exported .tex later. With these tests it would be enough > > to run those tests if any nesting bug is fixed to ensure that no > > regressions > > are introduced. How would I add those tests? In which directory? How to > > activate them in the test machinery?
Good idea, Georg. > This is easy, just add them in one of the scanned directories. > To activate, rerun the configuration part (cmake .....) > > After this they are accessible with e.g. > ctest -R <filename without extension> > > The scanned directories (and subdirectories) are ATM > lib/doc, lib/examples, lib/templates > > Locally I have also added 'development/mathmacros' > > See 'development/autotests/CMakefile.txt:141) Would another approach be to add a label? You can see the current labels we have with: ctest --print-labels Kornel's idea seems to me the most simple though. Scott
