aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorStefan Monnier2015-08-08 19:43:14 -0400
committerStefan Monnier2015-08-08 19:43:14 -0400
commit7e8f7e089f3e72644c9a6e0d022d51d3166bbb07 (patch)
tree543d572a52d29bf65358508f75e8cc138bd40f61
parent3a5f75193ed10ee5fb458e9879340947f31d5e12 (diff)
downloademacs-7e8f7e089f3e72644c9a6e0d022d51d3166bbb07.tar.gz
emacs-7e8f7e089f3e72644c9a6e0d022d51d3166bbb07.zip
* test/automated/ert-tests.el (ert-test-deftest): Add FIXME.
-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."
345 (should (equal actual-condition expected-condition))))))) 345 (should (equal actual-condition expected-condition)))))))
346 346
347(ert-deftest ert-test-deftest () 347(ert-deftest ert-test-deftest ()
348 ;; FIXME: These tests don't look very good. What is their intent, i.e. what
349 ;; are they really testing? The precise generated code shouldn't matter, so
350 ;; we should either test the behavior of the code, or else try to express the
351 ;; kind of efficiency guarantees we're looking for.
348 (should (equal (macroexpand '(ert-deftest abc () "foo" :tags '(bar))) 352 (should (equal (macroexpand '(ert-deftest abc () "foo" :tags '(bar)))
349 '(progn 353 '(progn
350 (ert-set-test 'abc 354 (ert-set-test 'abc