Utilities to help you test hiccup-markup generating functions.
Add this to your project.clj:
Find nodes matching a query:
(ns my.stuff-test (:require [hiccup-find.core :refer :all])) (fact (hiccup-find [:p.image] [:html [:body [:p.img "No"] [:p.image "Yes 1"] [:p.images "No"] [:div.image [:p.image "Yes 2"]]]]) => (list [:p.image "Yes 1"] [:p.image "Yes 2"]))
Queries support tag names, classes, ids and parent/child relationships.
[:.some-class] ; Match elements with this class [:h2.heading] ; Match elements with tag name h2 and class heading [:p.important.pitch] ; Match elements with tagname p and the ; two classes "important", and "pitch", in any order.
[:#main] ; Match elements with this id [:h2#main-heading] ; Match elements with tag name h2 and id main-heading [:h2#main-heading.important] ; Match element with tagname, class and id
[:#main h2] ; Find all h2s in an element with id "main"
To avoid having tests become overly coupled to details in the markup (such as OOCSS classes, which basically couple markup with visual appearance), sometimes asserting on the text content is good enough.
(hiccup-text [:html [:body [:h1 "Welcome, earthling"] [:p "Hope you " [:strong "enjoy"] " your stay"]]]) ;; => "Welcome, earthling\nHope you enjoy your stay\n")
hiccup-text appends a newline after each block element.
For a textual representation that reveals even fewer details about the
underlying structure, try
hiccup-string. It works just like
except it returns a string with newlines replaced by space characters, and all
consecutive spaces condensed to one.
Test hiccup-find in Clojure and ClojureScript with
PhantomJS is a prerequisite, since that's where the ClojureScript tests are run.
Copyright © 2014 Magnar Sveen and Christian Johansen
Distributed under the Eclipse Public License either version 1.0 or (at your option) any later version.