From react blog, 16.3 introduced deprecation notices for componentWillRecieveProps.

As a workaround, you would use the method

static getDerivedStateFromProps(nextProps, prevState)

therefore

componentWillReceiveProps(props){
    let total = props.results.length;
    let pass  = props.results.filter(r => r.status == 'pass').length;
    let fail  = total - pass;
    let passp = (pass/(total || 1) *100).toFixed(2);
    let failp = (fail/(total || 1) *100).toFixed(2);
    this.setState({total, pass, fail, passp, failp});
}

becomes

static getDerivedStateFromProps(nextProps, prevState) {
  if (nextProps.total !== prevState.total) {
    return ({ total: nextProps.total }) // <- this is setState equivalent
  }
  return null
}

You can perhaps add an additional field to Redux Store which would convey information that a new action from user happened, such as timestamp of clicking the search button, or a UUID, and then compare in componentDidUpdate with that.

this.props in componentDidUpdate will be the same as nextProps in componentWillReceiveProps, so you could use that.

// componentWillReceiveProps(nextProps) {
//   if (nextProps.someProp !== this.props.someProp) {
//     doSomething();
//   }
// }

componentDidUpdate(prevProps) {
  if (this.props.someProp !== prevProps.someProp) {
    doSomething();
  }
}