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 render(contextValue);
      },
  );
  sharedContextTests('useContext inside forwardRef component', Context =>
    React.forwardRef(function Consumer(props, ref) {
      const observedBits = props.unstable_observedBits;
      let contextValue;
      expect(() => {
        contextValue = useContext(Context, observedBits);
      }).toErrorDev(
        observedBits !== undefined
          ? 'useContext() second argument is reserved for future use in React. ' +
              `Passing it is not supported. You passed: ${observedBits}.`
          : [],
      );
      const render = props.children;
      return render(contextValue);
    }),
  );
  sharedContextTests('useContext inside memoized function component', Context =>
    React.memo(function Consumer(props) {
      const observedBits = props.unstable_observedBits;
      let contextValue;
      expect(() => {
        contextValue = useContext(Context, observedBits);
      }).toErrorDev(
        observedBits !== undefined
          ? 'useContext() second argument is reserved for future use in React. ' +
              `Passing it is not supported. You passed: ${observedBits}.`
          : [],