-
Notifications
You must be signed in to change notification settings - Fork 121
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
Support for cypress #15
Comments
MemLab can analyze heap snapshots taken from V8. In your case, write scripts to take heap snapshots from Cypress (if Cypress supports taking heap snapshots from browser) and put them into disk in the format that can be processed by MemLab. Here is what the MemLab output files look like (only To get examples of those meta files, run a random MemLab test scenario and view those files under this directory: When the files are ready, create a result reader: const reader = BrowserInteractionResultReader.from(directory); Then find memory leaks with the reader and this MemLab API: |
Can't find a way for cypress to take heap snapshots, embarrassing. |
@Levix I've never used Cypress before, but it seems Cypress supports Chrome DevTools Protocol, which could be used to get JS heap snapshots from Chromium. Here is the code pointer of how memlab uses puppeteer to collect the heap snapshots from Chromium. |
Here is an article written in Chinese on how to take heap snapshots. |
…ing frameworks Summary: This diff adds a new documentation page for how to integrate E2E testing framework with MemLab. In case anyone wants to detect memory leaks by running tests in other E2E testing frameworks such as Playwright or Cypress etc. Related to #35, #15, #14 Reviewed By: tulga1970 Differential Revision: D47247084 fbshipit-source-id: 0620defa7114bf77e3248472b424541f8cec481b
Hello,
I would like to know if memlab can work with Cypress. We have a large test suite of Cypress based tests, it would be nice to use memlabs with those tests rather than creating new ones with pupeteer.
The text was updated successfully, but these errors were encountered: