that doesn't give us multi browser though does it?
i thought we wanted to get a broader coverage
@flyboarder i think i'll look around a bit too, seems like things have changed a fair bit since i last looked into it
i'm not really up to date any more 😛
multi-browser needs a wrapper (test-runner) between the boot project and the browser, id rather write multiple test runners as first class boot tasks using boot-exec, so boot-puppeteer will be the first, maybe look at a firefox version after
yeah i don't see why not
puppeteer looks pretty selenium-y, do you think we can run unit tests through it easily as well?
the test runners and wrappers do always seem to come with their own set of bugs and conventions, so going lower level might help with that
yeah I dont see unit tests being a problem
@flyboarder so i think i've come across a need for your higher order attributes that you added in 7.1
could you give me a high level summary of how i should implement
@thedavidmeister this should really have it’s own blog post (wip), but basically, the
elem! multimethod, sidesteps attribute handling, so you can implement
:myattr/* and have it do whatever you’d like, it uses the same
dispatcher all of the multi-methods use and does a fallback to the value based dispatching we use for every thing else.