Class-Based Unit Tests: Running Specific Methods With Arguments
3 views (last 30 days)
Show older comments
I have a simple class:
MyTest < matlab.unittest.TestCase
I know that I can test specific methods of the class with the following:
runtests({'MyTest/method1', 'MyTest/method2'}) % etc
However, I want to run these specific tests with some kind of input parameter, e.g. an options struct. Ideally, I'd make "options" a property of MyTest (whether it's a static property or a property of an instance of MyTest) and set its value at runtime. I'd also be okay with passing the struct as an input to each of these methods.
How can I accomplish this? I read some stuff about TestParameterDefinition, but it didn't seem to give an example close enough to what I'm trying to do.
0 Comments
Accepted Answer
Dave B
on 30 Sep 2021
Edited: Dave B
on 30 Sep 2021
In your previous question I suggested runtests, but if you look at the other answer @Steven Lord provided a more complex alternative which is to create a matlab.unittest.TestSuite.
Using the TestSuite object let's you add external parameters, via the ExternalParameters Property. There's an example here: https://www.mathworks.com/help/matlab/matlab_prog/use-external-parameters-in-parameterized-test.html
10 Comments
Walter Roberson
on 4 Oct 2021
Over the years, we have had multiple people claim that it is "rude" to reply anything other than the code to accomplish exactly the task asked about -- including it being "rude" to ask questions about what the task actually is . Most of the time in such cases, information is missing, but the posters have claimed that it was "rude" for people to have replied with code that accomplished what the volunteers felt was most likely the actual question: that the only acceptable answer was code that perfectly accomplished the task the poster had in mind (and failed to convey.)
So given that there are people for whom anything other than perfect code responses are perceived as "rude", and given that we cannot predict ahead of time who will feel that way, is the conclusion that we should draw that the volunteers should never reply with anything other than exact code, in case the poster might be of the opinion that anything else is rude?
But if so... then what to do about the posters who consider plain code responses that do not have explanation / discussion, to be rude ?
Doesn't it follow that in order to satisfy everyone, that we should shut the site down ?
More Answers (0)
See Also
Categories
Find more on Loops and Conditional Statements in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!