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.
type: 'div',
        },
        type: App,
      }),
    );
  });
  it('can concurrently render context with a "primary" renderer', () => {
    const Context = React.createContext(null);
    const Indirection = React.Fragment;
    const App = () => (
      <Context.Provider>
        <Indirection>
          <Context.Consumer>{() => null}</Context.Consumer>
        </Indirection>
      </Context.Provider>
    );
    ReactNoop.render(<App />);
    expect(Scheduler).toFlushWithoutYielding();
    ReactTestRenderer.create(<App />);
  });
  it('calling findByType() with an invalid component will fall back to "Unknown" for component name', () => {
    const App = () => null;
    const renderer = ReactTestRenderer.create(<App />);
    const NonComponent = {};
    expect(() => {
      renderer.root.findByType(NonComponent);
    }).toThrowError(`No instances found with node type: "Unknown"`);
  });
});