meliorence / meliorence/react-native-snap-carousel
Jest testing in bitbucket pipelines
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.5k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
Is this a bug report, a feature request, or a question?
This is bug report
Have you followed the required steps before opening a bug report?
- I have read the guidelines regarding bug report.
- I have reviewed the documentation in its entirety, including the dedicated documentations 📚.
- I have searched for existing issues and made sure that the problem hasn't already been reported.
- I am using the latest plugin version.
- I am following the issue template closely in order to produce a useful bug report.
Have you made sure that it wasn't a React Native bug?
Yes
Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
The library works well on these platforms, but break pipelines
Is the bug reproductible in a production environment (not a debug one)?
This problem is reproduced in the debugging environment
Environment
Environment:
React: 18.0.0
React native: 0.69.1
react-native-snap-carousel: 3.9.1
jest: 28.1.3
@testing-library/jest-native: 4.0.4,
@testing-library/react-hooks: 8.0.0,
@testing-library/react-native: 10.1.1,
Target Platform:
Android (6.0)
iOS (10.3)
Expected Behavior
After creating a test for a component that uses a snap-carousel and writing text for it, the test running in pipelines in a bitbucket should show the same result that was when the test was run locally
Actual Behavior
I get this error in pipelines, but it is not there when running the test locally

Reproducible Demo
Steps to Reproduce
- Download the library
- Use it in any component
- Write a working test for this file that uses a carousel
- Push changes to the bitbucket
- To see that testing in pipelines failed
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the component test that uses react-native-snap-carousel in a Bitbucket pipeline, then compare its output and environment with the local run. The issue is resolved when the pipeline produces the same test result as the local execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- ci-cd, mobile-dev, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100