How do I use matlab.uitest.TestCase to open my app once and perform multple function tests?

Question

Avnet 2023-1-26

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1901305-how-do-i-use-matlab-uitest-testcase-to-open-my-app-once-and-perform-multple-function-tests

评论： Avnet 2023-2-8

I'm using matlab.uitest.TestCase to test my app. I'm looking for a way to launch my app only once and then perform a variety of tests defined under methods (Test)

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Steven Lord 2023-1-26

1
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1901305-how-do-i-use-matlab-uitest-testcase-to-open-my-app-once-and-perform-multple-function-tests#answer_1157100

You could do this by opening your app in a TestClassSetup method and storing a handle to it in a property of your test class, but this could lead to your tests violating the "Keep Tests Independent" principle.

Suppose you had two buttons, A and B. You want to unit test both buttons. So you write one test method named testA that clicks button A and another named testB that clicks button B. But the code that executes when you click button A disables button B. Depending on the order in which testA and testB run and whether or not they restore the state of the app back to how it was before they ran, testB may or may not fail. And if you tried to reproduce the failure (to investigate the root cause) by just running testB it would pass.

Heisenbugs are highly annoying to investigate.

7 个评论
显示 5更早的评论隐藏 5更早的评论

Steven Lord 2023-1-26

在 MATLAB Online 中打开

tplus.m

The (very, very basic) test file tplus.m has two Test methods, onePlusOne and twoPlusTwo, but as you can see from the detailed output and the test results only one Test method ran. If twoPlusTwo had depended on some setup from onePlusOne it would have failed. But since they're independent I can run either or both with no problem.

runtests("tplus.m", ...

ProcedureName="twoPlusTwo", ...

OutputDetail="Detailed", ...

LoggingLevel="Detailed")

Running tplus Setting up tplus Done setting up tplus in 0 seconds Running tplus/twoPlusTwo Done tplus/twoPlusTwo in 0.011796 seconds Tearing down tplus Done tearing down tplus in 0 seconds Done tplus in 0.011796 seconds __________

ans =

TestResult with properties: Name: 'tplus/twoPlusTwo' Passed: 1 Failed: 0 Incomplete: 0 Duration: 0.0118 Details: [1×1 struct] Totals: 1 Passed, 0 Failed, 0 Incomplete. 0.011796 seconds testing time.

If I omit the ProcedureName argument you'll see both Test methods run.

runtests("tplus.m", ...

OutputDetail="Detailed", ...

LoggingLevel="Detailed")

Running tplus Setting up tplus Done setting up tplus in 0 seconds Running tplus/onePlusOne Done tplus/onePlusOne in 0.003262 seconds Running tplus/twoPlusTwo Done tplus/twoPlusTwo in 0.002463 seconds Tearing down tplus Done tearing down tplus in 0 seconds Done tplus in 0.005725 seconds __________

ans =

1×2 TestResult array with properties: Name Passed Failed Incomplete Duration Details Totals: 2 Passed, 0 Failed, 0 Incomplete. 0.005725 seconds testing time.

Steven Lord 2023-1-27

This documentation page has an example of using shared test fixtures. The example runs two tests that each need to have a certain directory on the MATLAB search path. Instead of having each test add the directory to the path and restore the path afterwards they use a shared test fixture to add it to the path before either test runs and restore the path after both tests have run.

Another example where you might want to use a shared test fixture is to create or read a large data set to be used in multiple test files. Imagine the example on this documentation page but with a large matrix instead of a short user name.

You could have a shared test fixture that opens your app for multiple test files to use, but remember to Keep Tests Independent.

Avnet 2023-2-8