The test itself
config.ini. It can look something like this:
[DOMAssistant 2.6] file = "DOMAssistant.js" modifier = "" function = "$" [Mootools 1.2b2] file = "mootool1.2b2.js" modifier = "" function = "$$"
You then choose what selectors you want to run, in the file called
selectors.list, where you put each selector in its own line:
* body div body div div div
Objections/concerns regarding the test
While most people agree that this is a good addition to swiftly test CSS selectors, the most common objections are:
- Accuracy, If a selector returns a number of nodes, there’s no way to determine if it actually were the correct and/or the right number of nodes.
- It doesn’t put any value into that some selectors are more important to have a better performance for. E.g. an id selector (
#container) needs to be faster than a more uncommon selector, for example:
- The test HTML file doesn’t resemble any real-life scenario.
To reply to the above concerns:
- Absolutely true. However, it does indicate if a selector has totally failed, so you can take that into account.
So please, see the Slickspeed like what its for: a good overall performance indicator and a decent tool for checking accuracy.