Just about every time I set up a new `Context.Provider`, I end up accidentally specifying a `values` prop rather than `value`.  While it's a minor error, generally I build the container in which the provider resides and commit it to the code base before I ever use it.  It's only later when I go to use it that I realize I did it again.  Since the `Context.Provider` seems pretty much useless without a `value` prop specified, I'd love it if there was a prop error if it is missing... especially if another prop is defined on the `Context.Provider` instead.
render() {
        return null;
      }
    }
    const renderer = ReactTestRenderer.create(<Foo />);
    const tree = renderer.toTree();
    expect(tree.instance).toBeInstanceOf(Foo);
    cleanNodeOrArray(tree);
    expect(tree).toEqual({
      type: Foo,
      nodeType: 'component',
      props: {},
      instance: null,
      rendered: null,
    });
  });
  it('toTree() handles simple components that return arrays', () => {
    const Foo = ({children}) => children;
    const renderer = ReactTestRenderer.create(
      <Foo>
        <div>One</div>
        <div>Two</div>
      </Foo>,