Feature/pauli string test

[stand-by]

PR with test coverage around python bindings

[jamesETsmith]

A couple of things here:

• The directory names approvals and bindings are a bit ambiguous. I've spent the past few minutes pondering how to break up these different classes of bindings and can't come up with anything I'm excited about. The best I can come up with is cpp, py, and py_cpp, where those directories test the cpp code for correctness, the python code for correctness, and consistency between the cpp and python versions. Even as I write it, that sounds like a lot of duplicate code, but let's talk offline about a way to reuse as much code as possible.
• There are some tests with three or four analogous tests with different hard coded numbers, I think we can reduce the LOC in those tests by using pytest.mark.parameterize.

[jamesETsmith]

Also let's update the CI to run all these tests (through make)

[stand-by]

A couple of things here:

• The directory names approvals and bindings are a bit ambiguous. I've spent the past few minutes pondering how to break up these different classes of bindings and can't come up with anything I'm excited about. The best I can come up with is cpp, py, and py_cpp, where those directories test the cpp code for correctness, the python code for correctness, and consistency between the cpp and python versions. Even as I write it, that sounds like a lot of duplicate code, but let's talk offline about a way to reuse as much code as possible.
• There are some tests with three or four analogous tests with different hard coded numbers, I think we can reduce the LOC in those tests by using pytest.mark.parameterize.

I agree on a lot of points from your comment. I'll do a pass over tests and try to parametrize quick&easy cases. Also see my comment highlighting similar concerns.
As discussed, I've put together an asana ticket with desired test structure that we should benefit from and have as little code duplication as possible

[jamesETsmith]

LGTM @stand-by. I added an Asana ticket to track the unification of the test infrastructure here