As we refine the parser and package, it would be useful to have some functional end-to-end tests to ensure that changes/refactors do not affect the ability to serialize and deserialize the current QASM specification. These tests will likely make use of the qdata.load(s) and qdata.dump(s) functions, and compare their output vs. the expected output, for specific test data.
Note that this is separate to adding/extending the unit tests. While there should be a single PR adding functional end-to-end tests, unit tests should also be added in parallel as new features/code changes are implemented, to ensure that atomic units are functioning as expected.
As we refine the parser and package, it would be useful to have some functional end-to-end tests to ensure that changes/refactors do not affect the ability to serialize and deserialize the current QASM specification. These tests will likely make use of the
qdata.load(s)andqdata.dump(s)functions, and compare their output vs. the expected output, for specific test data.Note that this is separate to adding/extending the unit tests. While there should be a single PR adding functional end-to-end tests, unit tests should also be added in parallel as new features/code changes are implemented, to ensure that atomic units are functioning as expected.