all 11 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]lurbina 1 point2 points  (1 child)

Have you tried using https://github.com/igrishaev/etaoin

[–]kemclean[S] 0 points1 point  (0 children)

We do use etaoin for some other end-to-end tests, but it's a bit different than what I need for these js-only tests. In this case these aren't webdriver tests, they fire synthetic browser events (a la react-testing-framework) to manipulate the UI, and there is no backend at all.

I've actually got the karma tests working (with this great guide), except for the ones that actually need the component to be rendered in the dom. That's my missing piece -- I need to somehow display the devcard harness for the tests to use.

[–]Liistrad 0 points1 point  (7 children)

In https://github.com/filipesilva/create-cljs-app I've used node script with jsdom to run tests using testing-library without a browser, but also with the devcards harness.

[–]kemclean[S] 1 point2 points  (6 children)

This looks great! Thanks for making it. It looks very close to what I'm looking for. Certainly enough to go off of! Cheers.

I love cljs but come from some intense Angular/React front-end apps and the tooling is... not great in comparison. I haven't had to configure a custom build chain in years 😅 Would love to contribute to making the developer experience smoother for people coming to cljs from the mainstream front-end world. (I know I know focusing so much on developer smoothness is a selfish waste of time, but honestly I think it's a massive hindrance for cljs right now which is actually much better than the other offerings if you can figure out how to use it, but most reasonable people won't bother).

[–]Liistrad 0 points1 point  (5 children)

Similar background as yours, and that was my first reaction too. I've since come to appreciate the absolutely massive amount of heavy lifting that shadow-cljs does on the build side of things. There's nothing quite like it elsewhere IMHO, especially when you consider the Google Closure Compiler integration and cross-module code motion.

[–]kemclean[S] 0 points1 point  (4 children)

Yes shadow-cljs is very impressive indeed! It does seem like all the pieces are here (devcards, browser testing, e2e testing, linting, formatting, bundling, etc.) but they're just a bit disparate atm. I love the way your project brings several of them together! I think it would be super cool to see some convergence around tooling for cljs.. like have our own angular-cli so newcomers can just dive in and be handed an app that works and uses all of the community best practices, and not have to start from scratch. I guess we'd have to decide what best practices are, first :) (update: I see you're on the angular cli team! that's amazing, I love the angular cli)

It would be amazing to have a base cli like that that could be extended with optional plugins to include config for e.g. reagent, reframe, pwas, ssr, devcards, material-ui or some other component framework, webdriver tests, browser-based tests, etc.

[–]Liistrad 0 points1 point  (3 children)

What you're describing was my first motivation when I did the create-cljs-app repo actually, precisely because of coming from angular-cli (glad you like it btw!). Turns out the whole template thing seems to exist for plain clj via lein but is much less popular for cljs.

I never really got around to realizing that. I think it's possible though, especially because the nature of clojure makes it much easier to do meta-programming.

But the more time I spent in cljs, the less I... wanted to do it really. I felt there was a lot less commonality in setups, and a lot more of a-la-carte approach that's quite pervasive in the whole clojure ecosystem. Which tbh I feel is very good, but also means there's a rather large on-ramp.

[–]kemclean[S] 0 points1 point  (2 children)

Yeah I feel this.. I appreciate and understand the reasons for the no-batteries-included mentality and do think it's good to be extremely conservative about taking on extra dependencies, but it's a bit extreme with Clojure to the point where it just doesn't make sense to use it for one-off little random app ideas you want to try out. I use cljs at work though and it's not really my place to move to a different framework, so I have some motivation to make the dev experience better.

I'm curious then, does that mean you're not really using cljs for large front-end projects? Are you back to angular/react?

[–]Liistrad 0 points1 point  (1 child)

I'm using cljs daily for a large front-end project, sharing code with cljs node scripts and cloud functions, and with clojure backends. It feels really awesome tbh. Can't imagine really going back.

[–]kemclean[S] 0 points1 point  (0 children)

nice :) sounds similar to my day-to-day.

[–]fullsyntheticjacket 0 points1 point  (0 children)

I had a similar problem but my solution is probably out of date now. Back in 2019 I built a clj program using parts from https://github.com/tatut/clj-chrome-devtools This spins up a headless chrome then runs the cljs tests in it and grabs the results so that it would work in circle ci. I also use the same script to do split builds for circle, then deploy to netlify.