You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I was expecting the output.md file to report a "Significant Changes to Duration" for a <Card> component I purposefully slowed down after doing a baseline on it.
To Reproduce
Steps to reproduce the behavior:
Go to any component under test, and add this evil bit of code...
I'm running this with my RN 0.72.10 app with yarn 3.6.4, Reassure 1.0.0-rc.4 (introduces yarn 3.x and 4.x support), and using Jest ^29.7.0 with "@testing-library/react-native ^12.5.0. I'm using all of Reassure's defaults.
The idea behind this "evil" is to see what the report looks like when a component has degraded in performance. All part of evaluating introduction of Reassure to our project.
The text was updated successfully, but these errors were encountered:
Hi @jkoutavas, I've done a simple repro in our test app by adding your slow down code and it worked correctly. I had to reduce the loop count from 100 000 to 100, as otherwise the test was running too long for my patience:
I think you might have something that optimizes your code in a way that removes console.log calls. Do you see your 'Delay execution no. n' messages in the logs?
Could you either post a simplified example so I can re-create your issue (you can use one of our examples as a quick setup).
Describe the bug
I was expecting the
output.md
file to report a "Significant Changes to Duration" for a<Card>
component I purposefully slowed down after doing a baseline on it.To Reproduce
Steps to reproduce the behavior:
Go to any component under test, and add this evil bit of code...
Then run
yarn reassure
and look at theoutput.md
. In my case, the<Card>
component jumped up dramatically when I added the evil code:...
Where evil was added:
Expected behavior
I would expect Card to be mentioned here (and it isn't)
Additional context
My
Card.perf-test.tsx
:I'm running this with my RN 0.72.10 app with yarn 3.6.4, Reassure 1.0.0-rc.4 (introduces yarn 3.x and 4.x support), and using Jest ^29.7.0 with "@testing-library/react-native ^12.5.0. I'm using all of Reassure's defaults.
The idea behind this "evil" is to see what the report looks like when a component has degraded in performance. All part of evaluating introduction of Reassure to our project.
The text was updated successfully, but these errors were encountered: