From 7d0734f1ed929e7fbeb2124bd25009fab5998ba0 Mon Sep 17 00:00:00 2001
From: Simon Michael <simon@joyful.com>
Date: Wed, 29 Mar 2017 08:21:30 -0700
Subject: [PATCH] update addons tests, note a todo

---
 tests/addons/addons.test | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/tests/addons/addons.test b/tests/addons/addons.test
index 747c0b520..3c291f069 100644
--- a/tests/addons/addons.test
+++ b/tests/addons/addons.test
@@ -1,19 +1,25 @@
 # "make test" sets up the dummy add-on scripts required for these tests
 
-#XXX these don't obey shelltest -w, always running the hledger executable in PATH
+# Note because of the PATH setting these don't obey shelltest -w, 
+# they always run the first hledger executable in PATH
 
-# 14. flags after an add-command are handled by the add-on
+# 1. flags after an add-command are handled by the add-on
  PATH=$PATH:. hledger addon --help
 >>> /hledger-addon/
 >>>=0
 
-# 15. add-on flags which are not also defined in the main executable are a problem
+# 2. add-on flags which are not also defined in the main executable are a problem
  PATH=$PATH:. hledger addon --addonflag
 >>>2 /Unknown flag: --addonflag/
 >>>=1
 
-# 16. hledger main executable ignores anything after -- (and hides the -- from the add-on)
+# 3. hledger main executable ignores anything after -- (and hides the -- from the add-on)
  PATH=$PATH:. hledger addon --help -- --addonflag
 >>> /hledger-addon/
 >>>=0
 
+# TODO how to reliably ensure no addons but still find the hledger executable ?
+# 4. having no addons shouldn't break the commands list
+# PATH= ~/.local/bin/stack exec -- hledger
+#>>>=0
+