Is there is a way to convert Signal from Signal Builder Block to Test Sequence code?

The MATLAB automatically generate test harness using the signal builder block. i need to convert the all the signals from signal builder block to test sequence code , Please Help

[Pat Canny]

Hi @Anwin Kushal M,

Are you referring to automatically generated tests from Simulink Design Verifier?

Thanks.

@Pat Canny

Answer 1

[Pat Canny]

Assuming you need to use a Signal Builder instead of a Signal Editor (Signal Editor is the recommended approach; look here for a utility to convert from Signal Builder to Signal Editor), you can author a Test Sequence block programmatically.

To do this, try using the following functions:

1. Select the Signal Builder block in the model and use the signalbuilder function to retrieve the signal data for each group in the Signal Builder. Example code:

[time,data,signames,groupnames] = signalbuilder(gcb);

2. Use the sltest.testsequence functions to programmatically create a test sequence.

new_system('example_model')
blockName = 'example_model/Test Sequence';
sltest.testsequence.newBlock(blockName);

3. You can then start creating Test Sequence steps (starting with sltest.testsequence.addStep). The number of steps could be based on the number of elements in the Signal Builder data. Here is just some starter code for one of the signals:

numSteps = numel(data{1})-1; %assumes all signal data vectors are of equal length
numsignals = numel(signames);
for i=1:numsignals
    sltest.testsequence.addSymbol(blockName,...
    signames{i},'Data','Output');
end
actionDesc1 = [signames(1) + " = " + string(data{1}(1)) + ";"]; %just defines Action for first signal
stepNames = "Step" + string(1:numSteps);
sltest.testsequence.addStep(blockName,stepNames(1),'Action',actionDesc1)
% You could then use string concatenation to define Action for all signals in
% Step1
for k=2:numSteps-1
    actionDesc = [signames(1) + " = " + string(data{1}(k)) + ";"]; %just defines Action for first signal
       sltest.testsequence.addStepAfter(blockName,stepNames(k),stepNames(k-1),'Action',actionDesc);
       transitionDuration = time{1}(k) - time{1}(k-1);
       transitionCondition = "after(" + string(transitionDuration)+")";
       sltest.testsequence.addTransition(blockName,stepNames(k-1),transitionCondition,stepNames(k))
end

[Pat Canny]

Just a quick follow-up on my answer: the "Action Description" is just a string. My "starter code" would need to be updated to include data type casting and other considerations. The code above simply sets each signal to a double. My goal was to demonstrate the general workflow and show which functions to consider.

Answer 2

[Anwin Kushal M]

Yes, I am referring automatically generated tests from Simulink Design Verifier

-Thank you.

[Pat Canny]

Hi @Anwin Kushal M,

Thank you for clarifying. We have heard similar requests to yours recently. Would you be interested in working with us (MathWorks) directly to understand your use case for Test Sequence?

Thanks.

• @Pat Canny (Simulink Design Verifier Product Manager)

[Anwin Kushal M]

@Pat Canny ; yes, i am interested

- Thanks

[Pat Canny]

Thanks @Anwin Kushal M! Could you please send me an email at [e-mail] ?