summaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authorStefan Monnier <monnier@iro.umontreal.ca>2015-08-08 19:43:14 -0400
committerStefan Monnier <monnier@iro.umontreal.ca>2015-08-08 19:43:14 -0400
commit7e8f7e089f3e72644c9a6e0d022d51d3166bbb07 (patch)
tree543d572a52d29bf65358508f75e8cc138bd40f61 /test
parent3a5f75193ed10ee5fb458e9879340947f31d5e12 (diff)
downloademacs-7e8f7e089f3e72644c9a6e0d022d51d3166bbb07.tar.gz
* test/automated/ert-tests.el (ert-test-deftest): Add FIXME.
Diffstat (limited to 'test')
-rw-r--r--test/automated/ert-tests.el4
1 files changed, 4 insertions, 0 deletions
diff --git a/test/automated/ert-tests.el b/test/automated/ert-tests.el
index fcfc7ee4823..5382c400962 100644
--- a/test/automated/ert-tests.el
+++ b/test/automated/ert-tests.el
@@ -345,6 +345,10 @@ This macro is used to test if macroexpansion in `should' works."
(should (equal actual-condition expected-condition)))))))
(ert-deftest ert-test-deftest ()
+ ;; FIXME: These tests don't look very good. What is their intent, i.e. what
+ ;; are they really testing? The precise generated code shouldn't matter, so
+ ;; we should either test the behavior of the code, or else try to express the
+ ;; kind of efficiency guarantees we're looking for.
(should (equal (macroexpand '(ert-deftest abc () "foo" :tags '(bar)))
'(progn
(ert-set-test 'abc