Find stack targets, ...

At the moment, if one test suite depens on hspec or on a lib, then all test suites will be loaded with their corresponding libs: commercialhaskell/stack#3695

NOTES.md

@@ -0,0 +1,8 @@
+# Notes
+
+* in ghci, do `let main = Main.main` > `:main -m etc` to disambiguate between different mains that may be in scope (this happens in HIE)
+* in HIE, running the tests a second time results in this: ** Exception: ./test-main.log: openFile: resource busy (file is locked)
+    for HIE, we'd need `let main = hspec Spec.spec`. this may different on a per-project basis, so put it in configuration? dhall config file?
+
+* Discovered tests are organized by module name, minus "Spec". I.e., ApplyRefactPluginSpec -> ApplyRefactPlugin
+  * But NOT non-discovered tests (see `stack ghci --with-ghc intero haskell-ide-engine:test:haskell-ide-func-test haskell-ide-engine:lib`)

README.md

@@ -1,6 +1,12 @@
-# README
-## This is the README for the "languageprovider-sample" 
--------------------
+# Haskell Test Runner for VSCode
+
+## Troubleshooting
+
+* > cannot satisfy -package quickcheck-instances-0.3.12
+
+    You might have to run `stack build && stack test` once
+
+## This is the README for the "languageprovider-sample"
 
 This folder contains a sample VS code extension that demonstrates an extension that runs a language server
 
@@ -11,8 +17,8 @@ The code for the extension is in the 'client' folder. It uses the 'vscode-langua
 
 The language server is located in the 'server' folder. 
 
+## How to run locally
 
-# How to run locally
 * `npm install` to initialize the extension and the server
 * `npm run compile` to compile the extension and the server
 * open this folder in VS Code. In the Debug viewlet, run 'Launch Client' from drop-down to launch the extension and attach to the extension.