@foo what's your favorite testing framework for biff itself?
I just do manual testing
er... i'm thinking about writing test cases for biff to understand how biff works and how testing in clojure works. i'm open to doing anything. if you had a framework you like, i'd do it in that and then it might be helpful for you too.
how do i connect cider to it? i would like to have a repl in emacs connected to the running page, but i tried just doing cider-jack-in-cljs, it complains that a server is already running.
i've been able to connect sibling repls before in other test projects, but i'm not really sure how i did, or if that applies here
i also tried killing the server and running cider-jack-in-cljs, shadow-cljs, :app. it successfully opened localhost:9630
, but not <my-ip>:9630
, also i get nothing on localhost:8081
or <my-ip>:8081
. here's a dump of the cider-repl buffer https://wtools.io/paste-code/b1NO
and here's what happened when i tried running cider-jack-in-cljs after creating a vanilla biff/example, running ./task setup and running and killing ./task dev https://wtools.io/paste-code/b1NP
I'd say just go with clojure.test first. Not as fancy as some other options but it has the essentials. I haven't used emacs/cider myself (I use vim + fireplace) and am unfamiliar with how exactly the tooling works in emacs land, but biff starts an nrepl server on port 7888 by default, so see if you can connect to that explicitly. currently, shadow-cljs and biff run in separate jvms, so that's why killing the biff process will leave shadow-cljs running on port 9630. In Findka's codebase I've changed it so shadow-cljs runs in the same process as biff, but I haven't put that code into the biff repo yet.
that's for a backend repl anyway, for frontend you can connect to shadow-cljs's nrepl server on port 7889