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

Fleshing out the Jest mocking config #253

Open
TrentonBlackburn opened this issue Sep 9, 2024 · 1 comment
Open

Fleshing out the Jest mocking config #253

TrentonBlackburn opened this issue Sep 9, 2024 · 1 comment
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@TrentonBlackburn
Copy link
Collaborator

Hey there, we are consuming this SDK for our application, and are now required to flesh out unit testing for it.

I noticed that jest-config.ts seems to exist solely for complying with the package template, but I was curious if there were any plans to flesh it out soon so that us consumers can effectively test our consumption of the package.

Thanks!

@TrentonBlackburn TrentonBlackburn added triage me I really want to be triaged. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Sep 9, 2024
@jokerttu jokerttu added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed triage me I really want to be triaged. labels Sep 10, 2024
@jokerttu
Copy link
Contributor

jokerttu commented Sep 10, 2024

@TrentonBlackburn
Thanks for bringing this up!

You're right—the current jest-config.ts is fairly minimal, and we haven’t fully fleshed it out yet, nor do we have real tests against the example app. We're actively working on building out the testing infrastructure for this package, which will include more detailed Jest configurations and example tests. In addition, we're working on native unit tests for both Android and iOS implementations. Since the project involves native modules, we also plan to focus more on integration tests for the React Native implementation.

You can expect improvements on the testing coverage in the near future.

In the meantime, if you or others in the community have suggestions or would like to contribute, PRs improving the current state are always welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

3 participants