Why we need to be able to call a component instance method on some occasions during test

Example.js

import React, {Component} from 'react';
import Child from './Child'

class Example extends Component {
  a() {
    //do some stuff 
    this.c();
  }
  
  b() {
    //do some different stuff
    this.c()
  }
  
  c() {
    //do some common stuff
  }
  
  render() {
   return(
    <div>
      <Child doA={this.a.bind(this)} doB={this.b.bind(this)} />
    </div>
   ) 
  }
  }
}

Test.js

import Child from './Child'
import Example from './Example'

describe('Example', () => {
  describe('a', () => {
    it('should do some stuff', () => {
      component = createComponent.interleaved(<Example />);
      child = component.findByComponent(Child)[0];
      assert(child.props.doA())
    });
  });
  
  describe('b', () => {
    it('should do some different stuff', () => {
      component = createComponent.interleaved(<Example />);
      child = component.findByComponent(Child)[0];
      assert(child.props.doB())
    });
  });
  
  describe('c', () => {
    it('should do some common stuff', () => {
      component = createComponent.interleaved(<Example />);
      //FIXME How do I test 'C' without first calling 'A' or 'B'
    })
  });  
})

I think this is a scenario where we may need to have access to the instance methods of the component. Otherwise we cant test method c without first calling a or b.

Utils!

Utils would work if c was static.

Putting it into a real life context..

  focusOnInput() { //c
    this.setState({ inputFocused: true });
  }

  searchAddTerm(term)  { //a
    this.props.searchActions.searchAddTerm(term);
    this.focusOnInput();
  }

  searchRemoveTerm(term)  { //b
    this.props.searchActions.searchRemoveTerm(term);
    this.focusOnInput();
  }