A React tree traversal utility similar to jQuery, which can be useful for making assertions on your components in your tests.
chai-react
was originally built
to help with test assertions of React components. However, it quickly started
adding too much complexity because it was attempting to solve two problems: 1)
making assertions of properties/rendered content and 2) traversing the rendered
React tree to make those assertions.
rquery
is meant to take over the rendered tree traversing responsibility from
chai-react
, which will allow it to be used with any testing framework. It will
also provide convenience wrappers for various common test actions, such as event
dispatching.
The $R
factory method returns a new instance of an rquery
object.
Example:
var $r = $R(component);
An instance of the rquery
class contains an array of components, and provides
an Array
-like interface to directly access each component.
Example:
var $r = $R([component1, component2 /* , componentN */]);
$r.length === 2; // true
$r[0] === component1; // true
$r[1] === component2; // true
find (String selector)
: Returns a newrquery
instace with the components that match the provided selector (see Selector documentation).simulateEvent (String eventName, Object eventData)
: simulates triggering theeventName
DOM event on the component(s) in the rquery object.[eventName] (Object eventData)
: Convenience helper methods to trigger any supported React DOM event. See the React documentation to read about the events that are currently supported.
Example:
$R(component).find('MyComponentName');
$R(component, 'MyButton');
Description:
Traverses the tree to find components based on their displayName
value. NB:
the selector must start with an upper-case letter, to signify a
CompositeComponent vs. a DOM component.
Example:
$R(component).find('div');
$R(component, 'p');
Description:
Traverses the tree to find DOM components based on their tagName
. NB: the
selector must start with a lower-case letter, to signify a CompositeComponent
vs. a DOM component.
Example:
$R(component).find('.button');
$R(component, '.green');
Description:
Traverses the tree to find components with className
s that contain the
specified class.
Example:
$R(component).find('[target]');
$R(component, '[onClick]');
Description:
Traverses the tree to find components that have a value defined for the given property name.
Note: Although these are labeled as attribute selectors, they are really property selectors. In other words, they match properties being passed to a DOM/Composite component, not actual DOM attributes being rendered.
Example:
$R(component).find('[target="_blank"]');
$R(component, '[href=http://www.github.com/]');
Supported Operators:
rquery
supports the [CSS Selectors level 3 spec]
(http://dev.w3.org/csswg/selectors-3/#attribute-selectors):
[att="val"]
: equality[att~="val"]
: whitespace-separated list[att|="val"]
: namespace-prefixed (e.g.val
orval-*
)[att^="val"]
: prefix[att$="val"]
: suffix[att*="val"]
: substring
Description:
Traverses the tree to find components with a property value that matches the given key/value pair.
Note: Although these are labeled as attribute selectors, they are really
property selectors. In other words, they match properties being passed to a
DOM/Composite component, not actual DOM attributes being rendered. For complex
property values (e.g. arrays, objects, etc.), the value matchers are less useful
as rquery
doesn't currently support any complex value matching.
Note: All values must be provided as double-quoted strings. [att="val"]
is
valid, but [att=val]
and [att='val']
are not.
The rquery interface is meant to be generic enough to use with any assertion library/test runner.
Sample usage with Chai BDD style assertions:
expect($R(component).find('MyComponent')).to.have.length(1);