You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So is there an option to have Call as an interface and have Actual implementation and Test implementation? Actual would work as the Call works currently. Test implementation would not actually create a call but it would only set proper states and have convinient functions so the apps using this lib could be easily tested.
Test functions could be for example:
targetCanceledCall - which would send CallState.Done and SocketMethod.BYE as a real call does.
targetAcceptedCall - which would send CallState.Active, SocketMethod.Answer or both.
This would allow app developer to test the call before it can be tested on production.
That would also allow to have the Call as non-nullable. It is kinda weird to have Call nullable in production just because of testing. This adds additional edge cases to the app.
The text was updated successfully, but these errors were encountered:
So is there an option to have Call as an interface and have Actual implementation and Test implementation? Actual would work as the Call works currently. Test implementation would not actually create a call but it would only set proper states and have convinient functions so the apps using this lib could be easily tested.
Test functions could be for example:
CallState.Done
andSocketMethod.BYE
as a real call does.CallState.Active
,SocketMethod.Answer
or both.This would allow app developer to test the call before it can be tested on production.
That would also allow to have the Call as non-nullable. It is kinda weird to have Call nullable in production just because of testing. This adds additional edge cases to the app.
The text was updated successfully, but these errors were encountered: