How to simulate output ports in Unit testing

[Gonta01]

Let's consider the following component:

active component MyComponent {
async input port run: Svc.Sched
output port getData1: Drv.Data.GetData
output port getData2: Drv.Data.GetData
output port getData3: Drv.Data.GetData
guarded input port getAveragedData: Drv.Data.GetAveragedData
}

Ports are defined as follows:
module Drv {
module Data {
enum Status : U8 {
SUCCESS = 0
FAILED = 1
}
port GetData(ref data: F32) -> Status
port GetAveragedData(ref averagedData: F32)
}
}

Implementation:
void MyComponent::getAveragedData_handler(NATIVE_INT_TYPE portNum, F32& averagedData) {
averagedData= result;
}

void MyComponent::run_handler(NATIVE_INT_TYPE portNum, NATIVE_UINT_TYPE context) {
auto status = this->getData1(0, data1); // data1 is private member of MyComponent class
status = this->getData2(0, data2); // data2 is private member of MyComponent class
status = this->getData3(0, data3); // data3 is private member of MyComponent class
result = (data1 + data2 + data3) / 3;
}

Started to write unit test:

void MyComponent::
testAveraging()
{
/*
* How to write down what should output ports return?
* For example I want that getData1 will modify data1 to be 2, getData2 will modify data2 to be 3 and getData3 will modify data3 to
* be 10. What should be done?
*/
this->invoke_to_run(0, 0);
F32 averagingData;
this->invoke_to_getSensorData(0, averagingData);
ASSERT_FLOAT_EQ(averagingData, 5);
}

My question is in testAveraging comment above.

[Gonta01]

I understood how to mock output ports getData1, getData2 and getData3. Just needed to implement automatically generated functions: from_getData1_handler, from_getData2_handler, from_getData3_handler.

The next problem is that this->invoke_to_run(0, 0); seems to not invoke run_handler logic

[Gonta01]

It seems that run handler is not invoked because it async port... Because if I change it to sync, test runs properly.

What should be done to handle async ports?

[Gonta01]

Got it! It was needed to call this->component.doDispatch(); just after run port invocation

[LeStarch]

Precisely. Good catch!