How use cljsjs react bootstrap? https://github.com/cljsjs/packages/tree/master/react-bootstrap I have added it to dependencies, web page mention Foreign Libs, what should I put there?

is there a good tutorial about writing externs?

@edbond: you add the require to your ns cljsjs.react-bootstrap and then use it via js interop

eg. (js/ReactBootstrap.Alert #js {} "alert-msg")

https://github.com/omcljs/om/wiki/Applying-Property-Based-Testing-to-User-Interfaces

@dnolen great example, thanks!

@dnolen: very interesting article, that is only one step to recording user behaviours and using them as your testing data, instead/in_addition to randomly generated actions

something like this: when app error is thrown beta version could ask user to submit recorded workflow back as a test case

@darwin: recording user interactions is completely inferior to this approach

that’s like recording programs to test that Clojure’s data structures are OK

in any case I didn’t have time to explain the theory of property based testing.

maybe I’m missing something, but IMO when you want to model user behaviour the hard part is to write those random generators to model a user properly

I suggest reading up on that (if you haven’t) before assuming anything I may be talking about.

you provided nice tooling and decoupling of code pieces so those test can be executed nicely, but the hard part is still writing those generators

ok

the whole point of property based testing is to make writing generators feasible

and the whole reason why the grammar for Om Next query expressions is trivial

if property testing can find bugs in Clojure datastructures after multi hours runs

I guarantee what I’m saying can be done reasonably well for user interfaces

and in no way claiming this is the only thing

but reliance on recorded UI interactions, QA, etc. this stuff isn’t working

good points, I see

Thanks, @thheller . I figured out how to use that in rum, it's a verbose way.

@dnolen: I’ve had this idea kicking around for awhile, love the way you’ve made it work

@sgrove: it great when stuff like this doesn't actually require any integration :)

Okay, so I finally remedied my ignorance about Om Next; or at least, I watched the videos and read the words. The principles are still seeping into my brain. It seems that Om Next is intended to work very nicely with Datomic, but it does not seem to be strictly tied to it. It seems entirely reasonable to build an Om Next app on a traditional REST API; you'd just need to get an abstraction around it. And you'd still get many or most of the benefits of the system.

That's right