What is the best way to test type 2 component ?

hey guys, i wanted to get some opinions on a good way to run some functional tests on a re_frame app. i already have what I would call “smoke” tests that use a webdriver api to click through a couple major components, testing a few happy paths e2e across live apis. what i’m looking for next is ui-focused tests that 1) still use a webdriver-style click-through/interaction-via-browser, but doesn’t talk to real APIs and instead only receives precanned json responses

this in theory is really simple, just replace the :http cofx i have registered, and mock out a bunch of precanned responses instead of live network requests. the problem is at my implementation level … what’s a good strategy for running a testing suite from clj? the best i can come up with is pre-building the app under a different target, where this build is a copy of my “live build” except the cofx that touch apis are replaced by stubs. i really wish I could just use with-redefs [my.existing/http mock-http] but obv that doesnt work because you can’t mix clj/cljs runtimes 😞

What is the best practice SPA with re-frame to see on github? I am talking about something real and bigger than todo challenge.

in my re-frame app I had namespaced subscriptions and events. now I’ve removed the namespaced ones and replaced with normal ones (with the same names of course. I just changed :: to :) and now none of my subscriptions and event handlers work. could there be a reason for this?

oh actually never mind. I don’t have them loaded in my core.cljs

and that’s why..

looking for some advice. if you’re building a simple client side re-frame app, but you need a little proxy microservice to front some api calls; is it a common pattern to make that part of the same repository? local dev would be firing up that ring app, and then also firing up a separate cljs+figwheel repl to run the front end?

@chadhs better to have the separate server for the application and launch it seperately from figwheel

the whole application, proxy and the rest of it

figwheel should connect to the running application when launched seperately

@bhauman so in my simple example I’d be better off with a repo for the proxy service and one for my client app

is that a question?

@chadhs is that a statement or a question?

if its a question I'd say not neccessary

@bhauman a question yes

so you are wondering how to run a seperate server?

So proxy server could live in project src/clj and start that separately?

Yessir

@chadhs first do you need a proxy server or can you connect to it directly from your app?

second a proxy server at its simplest is just a clojure namespace that defines a ring-endpoint / middleware

Proxy due to CORS issue

@chadhs let's drill down a bit here what CORS issue specifically?

Yeah true so could live in same project and I start that first

is the service hosted elsewhere on the internets?

My client app is hitting open weather map api every 15 mins and works

Want to use dark sky but they don’t enable CORS

gotcha

Thus the proxy

I’m running this locally on a raspberry pie so I wouldn’t really be leaking an API key but I understand why they don’t allow Cors

coolio

OK so I would use lein-ring to create a server that serves your whole application compiled cljs assets index.html and your api proxy

https://github.com/bhauman/lein-figwheel/tree/master/examples/separate-server

Awesome thnx will try this when back at machine !! 😎