This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-21
Channels
- # announcements (2)
- # aws (1)
- # beginners (172)
- # boot (3)
- # calva (19)
- # cider (18)
- # clj-kondo (5)
- # cljsrn (18)
- # clojure (47)
- # clojure-europe (9)
- # clojure-finland (7)
- # clojure-italy (3)
- # clojure-nl (15)
- # clojure-spec (20)
- # clojure-sweden (2)
- # clojure-uk (72)
- # clojurescript (45)
- # cursive (42)
- # datomic (6)
- # duct (4)
- # emacs (4)
- # expound (48)
- # figwheel-main (7)
- # fulcro (64)
- # graphql (8)
- # hoplon (9)
- # hyperfiddle (1)
- # jackdaw (8)
- # jobs (4)
- # jobs-discuss (61)
- # klipse (5)
- # leiningen (6)
- # off-topic (72)
- # pathom (2)
- # planck (11)
- # re-frame (1)
- # reagent (3)
- # reitit (16)
- # remote-jobs (17)
- # ring-swagger (3)
- # shadow-cljs (49)
- # spacemacs (12)
- # sql (3)
- # tools-deps (124)
- # vim (64)
- # xtdb (4)
@UJCC6CE9E i get a popup asking for a host and port
@UJCC6CE9E don't know if this makes a difference, but i have a symlink from ~/.atom/packages/chlorine to a cloned (and setup) repository of atom-chlorine -- i'm not running a version that's installed via atom -- if you aren't doing that and want to try, check out the "How to contribute?" at the bottom of the README.md in the atom-chlorine repository. my atom version is: 1.36.1 and i also have the ink package for atom installed.
My atom version is 1.37.0, also got ink installed. I'm running chlorine installed via atom. I'll try 🙂
ah, if you haven't restarted atom since installing various packages, it's possible that might help
i don't know if any relevant info will show up, but if you ctrl+shift+i (developer console?) in atom, it's possible there might be something there
it's unfortunate that atom and vscode both seem rather quiet from the perspective of debug info
i usually use emacs, though with a custom repl -- i prefer atom to vscode philosophically, but frankly, vscode works better atm
well, vim keybindings aren't a problem, it's the decades of emacs-related wiring in my brain 🙂
oh, heheheh. I started using emacs some weeks ago, I was getting used to some of the keybindings but they weren't very intuitive
it seems there are some interesting vim-based clojure tooling options coming into existence, is vim possibly worth considering? there's a #vim channel here too
for emacs, i tend to use helm so i haven't had to learn too many odd keybindings recently
I'm so used to Intellij. I know cursive exists but I want to use emacs / atom / maybe vim?
one thing cursive has over everything else is its debugger though -- cider also has a debugger of sorts, but last i checked it's not as nice as cursive's
fwiw, if you aren't familiar with it, here's a vid w/ the cursive author discussing the debugger in cursive: https://www.youtube.com/watch?v=ql77RwhcCK0
unfortunately, proto-repl development has stagnated...chlorine appears to be somewhat of a forked / continuation of sorts, iiuc
perhaps you'll get some helpful responses from mauricio.szabo or seancorfield before too long
Interesting: "Since it is strongly normalising, it is decidable whether or not a simply typed lambda calculus program halts: in fact, it always halts. We can therefore conclude that the language is not Turing complete." https://en.wikipedia.org/wiki/Simply_typed_lambda_calculus#General_observations
Yeah, the connection with programming and the foundations of mathematics is really incredible. There are just a ton of connections. It is one of the things that make programming so beautiful to me.
Thoughts on Cucumber as testing tool?
If you are interested in doing it in clojure look at https://github.com/FundingCircle/jukebox
I was not very impressed last time I tried to use cucumber (which at the time meant spending a lot of work just trying to get it working)
the idea of writing tests in that style is very constraining, and it seems like will require maintenance of basically an adhoc parser
Cucumber is like clojure.test/are for English. (Over simplification, but true enough)
I think cucumber is based on the assumption that making tests/testing available to wider/non-technical audience is valuable. And trades off things to try and make that happen.
The problem is the initial assumption is almost always wrong, no one wants to read your tests, so the painstaking effort required to make them readable is almost always waste
I have found the Given/When/Then format helpful even without automating in Cucumber tests. Depends a lot on stakeholders
The other alternative I’m considering is record actions->play them back->verify results in DB. The app I’m testing is a tangled mess of a desktop app, but I can tap into the logs and infer actions from that, which could then be used to generate API calls to “play back” the actions again.
Personally I use the following, it gives me the 80% of what meatier DSLs would
(defmacro context
{:style/indent 1}
[s & body]
`(clojure.test/testing ~s ~@body))
(defmacro it
{:style/indent 1}
[s & body]
`(clojure.test/testing ~s ~@body))
testing == given
context == when
it == thenI think the best case scenario would to record actions to generate the base case, and then identify variables based on our model, so we can check all the many permutations, as we really have to exhaustively check everything to know anything for certain.
Like maybe a macro-recorder for Gherkin syntax.
Our manual test suite is a big deal in our company, and it’s written in pseudo-Gherkin.
you are describing a process so far entirely about machines doing things, why would you record results in a not very expressive poorly defined language designed to be readable by non-technical people
The reasons are mainly political, not technical. I think people would be very happy to see plain-english stuff they could read and understand.
I try not to mention math or logic at work. People don’t always respond well 😕
I love those videos though, they’re great.