jaredLunde / jaredLunde/exploration

Difficulty rendering for Testing Library test

Open
#30 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
60
Forks
4
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
I am unable to render any nodes for the purpose of automated testing.

**To Reproduce**
https://codesandbox.io/s/basic-example-forked-rx85dd?file=/src/App.test.js

**Expected behavior**
Nodes should eventually render yet no amount of delay or async trickery in the test causes them to appear.

**Additional context**
https://testing-library.com/docs/react-testing-library/intro/ is quite common though there are plenty of other options. I know this repo has loads of tests for the underlying functionality but I did not see any e2e test from which to adapt my own test.

Thank you for creating this package. The level of detail is super impressive.

Contributor guide

Open the contributing guide

Research direction

Reproduce the problem using the linked CodeSandbox and inspect src/App.test.js first. Compare the test setup with the React Testing Library introduction, then review this repository’s existing tests for a relevant example. Done means the nodes render reliably in the automated test without additional delay or async workarounds.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.