@gsarma, good points.
One thing is that the short-time objective of our testing framework is what is discussed in openworm/muscle_model#30. After having this, it could be extended to cover more curves and parameters usually exists in similar studies (such as I/t, V/t, activation/inactivation rates, etc). Just saying to keep in mind the big picture, and that it's not going to cover just I/V curves, as you pointed out.
This generalization is the same as for digitization and fitting processes, which finally their outputs would be inputs of the testing framework.