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.
return null;
    }
    Validator.propTypes = {dontPassToSeeErrorStack: PropTypes.bool.isRequired};
    expect(() => {
      ReactDOMServer.renderToStaticMarkup(
        <Context.Provider>
          <Context.Consumer>{() => <Validator />}</Context.Consumer>
        </Context.Provider>,
      );
    }).toErrorDev(
      'Warning: Failed prop type: The prop `dontPassToSeeErrorStack` is marked as required in `Validator`, but its value is `undefined`.\n' +
        '    in Validator (at **)',
    );
  });
  it('warns if displayName is set on the consumer type', () => {
    const Context = React.createContext(null);
    expect(() => {
      Context.Consumer.displayName = 'IgnoredName';
    }).toWarnDev(
      'Warning: Setting `displayName` on Context.Consumer has no effect. ' +
        "You should set it directly on the context with Context.displayName = 'IgnoredName'.",
      {withoutStack: true},
    );
    
    Context.Consumer.displayName = 'ADifferentName';
  });
});