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

RFC: Testing ReactXP? #1233

Open
fbartho opened this issue Aug 9, 2020 · 1 comment
Open

RFC: Testing ReactXP? #1233

fbartho opened this issue Aug 9, 2020 · 1 comment

Comments

@fbartho
Copy link
Contributor

fbartho commented Aug 9, 2020

I've been thinking about how we can start getting more of these persnickety bugs squashed / make it easier for people to demonstrate how bugs occur.

I've seen tickets that have code snippets in them, and it would be awesome if we could have those snippets converted to a PR that contributes a unit-test demonstrating the expected behavior.

If so, we'd need some way to test the code on each platform, what tools should we use?

On iOS/Android:

On Web:

Do people have any further recommendations?

@mikehardy
Copy link
Contributor

I'm doing something similar in the react-native-firebase repo, this is my next project there: invertase/react-native-firebase#4058

As part of that https://cavy.app was mentioned as a possible tool. Why? Detox is out-of-app testing, so it's sort of like simulating touch events - more black-box style, Cavy allows your test code to run in-app so you can probe more deeply or decompose functionality to true unit test like tests (but running on device) as opposed to just simulating touches

If I undestand that correctly it would allow for the RXPTest application to be run as a list of tests directly by test harness, non-interactively with per-test status reporting (while still being used as an interactive human-inspection app I suppose). The react-native-firebase test app is similar to RXPTest in that it has a large library of needs-to-run-in-app tests but they run non-interactively which is nice - just using a custom framework (jet: https://github.com/invertase/jet) which won't be maintained going forward unless I/we really have to

This is maybe not actionable but it's an RFC, so there you go :-)

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

No branches or pull requests

2 participants