Michael Albinus writes: > Morgan Smith writes: > >>> We might be better with >>> >>> --8<---------------cut here---------------start------------->8--- >>> @$(EMACS) -Q --batch -L . -L ./test -l $(TESTSOURCE) -f ert-run-tests-batch-and-exit >>> --8<---------------cut here---------------end--------------->8--- >>> >> >> I did the '-L ./test' part but I kept the foreach. >> >> Without the foreach the command looks like "... -l file1.el file2.el >> file3.el ..." and emacs only actually loads the first file. The command >> needs to look like "... -l file1.el -l file2.el -l file3.el ..." > > My point is, that we have only the make target 'check', which runs all > ert tests located in different files. But I would also like to run only > the tests in, say for example, debbugs-tests.el. So we need an own > target for every *-tests.el file. > I've now implemented the interface I've seen in other projects (guix, org-mode) to enable this feature. It looks something like this: "make check TESTS='get-status'". >>>> --- /dev/null >>>> +++ b/test/debbugs-test-helpers.el >>>> @@ -0,0 +1,146 @@ >>>> +(defconst debbugs-test--bug-status-soap-return >>>> +(defconst debbugs-test--bug-status >>> >>> Perhaps we should move these data into an ert-resource file (or two). >>> I still don't understand why it would be beneficial to have the data in resource files. I also think that maybe it should be classified as an enhancement that goes beyond the scope of this particular patch series. If you would like to do this please feel free. I've only got so many hours in my day.