Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better app call test options. #304

Open
Del-S opened this issue Jun 22, 2023 · 0 comments
Open

Better app call test options. #304

Del-S opened this issue Jun 22, 2023 · 0 comments

Comments

@Del-S
Copy link

Del-S commented Jun 22, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant