Tests fail on Android ExpoExample
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 42/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- android, react-native, typescript
- Área
- mobile-dev, testing-qa
Línea de trabajo
Comienza en ExpoExample/tests/App.owl.tsx y reproduce el problema con yarn && cd ExpoExample && yarn, seguido de yarn owl:build:android y yarn owl:test:android. Comprueba cómo el comando de pruebas de Android resuelve la importación de react-native-owl y compara el informe de Jest con la salida del fallo. Se considera terminado cuando la suite de pruebas de Android de ExpoExample se ejecuta sin el fallo de resolución de módulos y muestra sus resultados de forma consistente.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Is there an existing issue for this?
- I have searched the existing issues
Code of Conduct
- I agree to follow this project's Code of Conduct
Code Sandbox link
No response
Bug report
Tried to run tests in react-native-owl/ExpoExample on Android.
May be a known issue:
https://github.com/FormidableLabs/react-native-owl/issues/139#issuecomment-1526473064
Steps to reproduce:
1. Clone react-native-owl
2. yarn && cd ExpoExample && yarn
3. yarn owl:build:android
4. yarn owl:test:android
Error:
yarn run v1.22.22
$ yarn owl test --platform android
$ node ../dist/cli/index.js test --platform android
[OWL - CLI] Starting websocket server.
[OWL - CLI] Running tests on android.
Performing Streamed Install
[OWL - WebSocket] Listening on port 8123.
Success
bash arg: -p
bash arg: com.ExpoExample
bash arg: -c
bash arg: android.intent.category.LAUNCHER
bash arg: 1
args: [-p, com.ExpoExample, -c, android.intent.category.LAUNCHER, 1]
arg: "-p"
arg: "com.ExpoExample"
arg: "-c"
arg: "android.intent.category.LAUNCHER"
arg: "1"
data="com.ExpoExample"
data="android.intent.category.LAUNCHER"
Events injected: 1
## Network stats: elapsed time=13ms (0ms mobile, 0ms wifi, 13ms not connected)
[OWL - WebSocket] The server received a message: OWL Client Connected!
[OWL - CLI] (Tests mode) Will compare latest images with the baseline.
[OWL - CLI] Will set the jest root to /Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/ExpoExample.
FAIL __tests__/App.owl.tsx
● Test suite failed to run
Cannot find module 'react-native-owl' from '__tests__/App.owl.tsx'
> 1 | import {
| ^
2 | takeScreenshot,
3 | press,
4 | toExist,
at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:306:11)
at Object.<anonymous> (__tests__/App.owl.tsx:1:1)
Test Suites: 1 failed, 1 total
Tests: 0 total
Snapshots: 0 total
Time: 0.46 s, estimated 19 s
Ran all test suites.
Test results written to: .owl/report/jest-report.json
(node:72810) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[OWL - CLI] Generating Report
[OWL - CLI] Report was built at /Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/ExpoExample/.owl/report/index.html
[OWL - CLI] Tests completed on android.
Error: Command failed with exit code 1: jest --testMatch="**/?(*.)+(owl).[jt]s?(x)" --verbose --roots=/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/ExpoExample --runInBand --globals='{"OWL_CLI_ARGS":{"_":["test"],"platform":"android","p":"android","config":"./owl.config.json","c":"./owl.config.json","update":false,"u":false,"$0":"../dist/cli/index.js"}}' --json --outputFile=/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/ExpoExample/.owl/report/jest-report.json
at makeError (/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/node_modules/execa/lib/error.js:60:11)
at module.exports.sync (/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/node_modules/execa/index.js:194:17)
at module.exports.commandSync (/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/node_modules/execa/index.js:235:15)
at /Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/dist/cli/run.js:211:54
at step (/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/dist/cli/run.js:33:23)
at Object.next (/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/dist/cli/run.js:14:53)
at fulfilled (/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/dist/cli/run.js:5:58) {
shortMessage: `Command failed with exit code 1: jest --testMatch="**/?(*.)+(owl).[jt]s?(x)" --verbose --roots=/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/ExpoExample --runInBand --globals='{"OWL_CLI_ARGS":{"_":["test"],"platform":"android","p":"android","config":"./owl.config.json","c":"./owl.config.json","update":false,"u":false,"$0":"../dist/cli/index.js"}}' --json --outputFile=/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/ExpoExample/.owl/report/jest-report.json`,
command: `jest --testMatch="**/?(*.)+(owl).[jt]s?(x)" --verbose --roots=/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/ExpoExample --runInBand --globals='{"OWL_CLI_ARGS":{"_":["test"],"platform":"android","p":"android","config":"./owl.config.json","c":"./owl.config.json","update":false,"u":false,"$0":"../dist/cli/index.js"}}' --json --outputFile=/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/ExpoExample/.owl/report/jest-report.json`,
escapedCommand: `jest "--testMatch=\\"**/?(*.)+(owl).[jt]s?(x)\\"" --verbose "--roots=/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/ExpoExample" --runInBand "--globals='{\\"OWL_CLI_ARGS\\":{\\"_\\":[\\"test\\"],\\"platform\\":\\"android\\",\\"p\\":\\"android\\",\\"config\\":\\"./owl.config.json\\",\\"c\\":\\"./owl.config.json\\",\\"update\\":false,\\"u\\":false,\\"$0\\":\\"../dist/cli/index.js\\"}}'" --json "--outputFile=/Users/pablogomez-echegaray/Documents/GitHub/react-native-owl/ExpoExample/.owl/report/jest-report.json"`,
exitCode: 1,
signal: undefined,
signalDescription: undefined,
stdout: undefined,
stderr: undefined,
failed: true,
timedOut: false,
isCanceled: false,
killed: false
}
Specify --help for available options
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Interestingly, the report seems to say all the test passed and failed at the same time.
- Lenguaje dominante
- TypeScript
- Estrellas
- 693
- Forks
- 27
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de FormidableLabs/react-native-owl
-
Actively Maintained ?Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 5/100
FormidableLabs/react-native-owl#194 · 3 comentarios · 1 reacción ·
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 42/100
FormidableLabs/react-native-owl#191 · 3 reacciones ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 30/100
FormidableLabs/react-native-owl#190 · 1 comentario · 1 reacción ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
FormidableLabs/react-native-owl#188 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 30/100
FormidableLabs/react-native-owl#186 · 1 comentario · 1 reacción ·
Todos los issues de FormidableLabs/react-native-owl
Issues similares
-
Area/Cloud Needs Triage Type/Bug
Dificultad 1/5 1-3 horas Aptitud para principiantes 86/100
wso2/product-integrator#2847 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
bluesky-social/social-app#12118 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
heygen-com/hyperframes#6021 ·
Los mantenedores suelen responder en 1 día
-
Edit: Tele Posadas HDAbiertocheck:passed streams:edit
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día