I am exploring Matlab's unit testing framework and I'd like to use it with a project that involves communicating with an external device connected through a serial port.
I currently have a wrapper class that encapsulates the serial interface (and the accompanying protocol implementation). This is a handle class, and contains a serial object as one of its properties. Additionally, the constructor will open the serial connection, and the destructor will close and delete it.
So in general usage I'd do something like:
my_obj = my_class('com1');
Now my question. I'd like to write some unit tests (using the Matlab Testing framework). How can I set these tests up, but specify the com-port external to the test functions/scripts? Is there a way to instantiate my_obj, and then give a set of tests access to the specific my_obj?
- I do not want to hard-code the com-port in any of the test definitions.
- Class-based unit tests don't seem to have conventional constructors (or a way of explicitly instantiating my_obj)
- Function-based tests suggest that you can share information through the TestCase.TestData, but that only seems to be possible within the sub-tests that make up a test file.
- I suppose I could get around this by loading a text/mat configuration file or checking an environment variable in the file fixtures, but that seems inelegant.
Thanks for your help.