var fooTree = testTree(, {
stub: {
fuz: null
}
});
fooTree.get("bar").click(); // simulates a click
fooTree.getIn(["boz", "biz"]).click(); // simulates a click on a deep node
fooTree.get("baz").length === 2; // collection of nodes
fooTree.get("fuz") === null; // null due to being stubbed out
`

In the above example react-test-tree has recursively built a tree out of the testRef and testRefCollection props, represented as nodes of the tree, which can be retrieved using get() or getIn(). Any names that appear in the stub tree config get replaced or removed.

testRef and testRefCollection

You should be familiar with the ref prop in React. They are used when you need to reference an element in your render function. You can look at the testRef prop like a ref, but purely for testing. It is necessary to distinguish between the two because of their applications; the React team is making it increasingly clear that refs should only be used for very specific purposes, which don't primarily include testing.

As well as the basic testRef prop, react-test-tree makes it possible to retrieve the children of an element by use of refCollection. Declaring testRefCollection on a component will make all it's direct children available on the corresonding tree node as an array:

`jsx
var BarComponent = React.createClass({
render: function () {
return (

Blue
Gold
;
);
}
});

var barTree = testTree();
barTree.get("bar").length === 2;
barTree.get("bar")[0].getAttribute("value") === "blue";
`

__Notes__:
* You can still apply a testRef as well as a testRefCollection if you want to be able to manipulate the parent element too.
* testRefs and testRefCollections may not have the same name.
* Updates to the render tree will not be reflected in the test tree until the next tick. You should defer accessing the tree after causing any updates:

`jsx
var tree = testTree();
tree.get('button').click();
defer(function () {
expect(tree.state.clicked).to.be.true; // passes
});
`

Stubs

It is inevitable that at some point when testing React components you will want to avoid rendering part of a component. Perhaps it might trigger some sideways data loading, or maybe you want to replace it with a mock. react-test-tree allows you to quickly and easily stub out any testRefs in the tree with either null or a replacement component:

`jsx
var MockComponent = React.createClass({
render: function () {
console.log(this.props.aProp);
return