When you have built a new Calva extension VSIX file you should put it through some quick testing to check that it is not totally broken. Blow some smoke into the build and confirm that no smoke leaks out. This is until we automate these smoke tests. Which you are encouraged to look into.
Check the following things in order.
You will see this in the Calva says output channel.
Syntax highlighting works
NB: Rainbow parens sometimes fail to activate. Reload the window to try wake it.
- Formatting current form (press
tabat a strategic point in the file)
- Auto-indent (press
enterat a strategic point in the file)
Paredit activation is currently glitchy, try switching focus back and forth from adn to the file to wake Paredit up.
Jack in works
Use your favourite project. This is enough in most cases. But depending on the nature of your change, you might want to cover some different project types and combos:
- Clojure CLI
- Figwheel Main
- Figwheel Legacy
- Custom Jack-in/Connect sequences
Evaluate a form in the REPL Window.
You can test this on a project you have jacked in to.
- Load a file
- Hover docs on some symbols.
- Peek definition (ctrl/cmd while hovering)
- Go to definition (ctrl/cmd click symbol)
- Evaluate some code
- Evaluate some coee with pprint toggled on and off
And please help keeping this page updated with things you think it is important to do in a smoke test.