Ndb jest or ndb mocha (or npx ndb jest / npx ndb mocha)ĭebug your test inside chromium like a boss! Npm install -g ndb (or even better, use npx!)Īdd a debugger to your Puppeteer (node) codeĪdd ndb (or npx ndb) before your test command. This example filters out all Network domain messagesĮnv DEBUG="puppeteer:*" env DEBUG_COLORS=true node script.js 2>&1 | grep -v '"Network'ĭebug your Puppeteer (node) code easily, using ndb
Will be logged via the debug module under the puppeteer namespace. Now your debugger will be hit and you can debug in the test browserĮnable verbose logging - internal DevTools protocol traffic In the newly opened test browser, type F8 to resume test execution In Chrome open chrome://inspect/#devices and click inspect Run node -inspect-brk, eg node -inspect-brk node_modules/.bin/jest tests The method launch(options) is just a slightly changed puppeteer launch function to start puppeteer in headful mode with this extension.Debugger await page. videoConstraints: įor a detailed documentation of the mimeType, audioBitsPerSecond, videoBitsPerSecond, bitsPerSecond, frameSize properties have a look at the HTML5 MediaRecorder Options and for the videoConstraints and audioConstraints properties have a look at the MediaTrackConstraints. If this is specified along with one or the other of the above properties, this will be used for the one that isn't specified.įrameSize?: number // The number of milliseconds to record into each packet.
This can be specified instead of the above two properties. VideoBitsPerSecond?: number // The chosen bitrate for the video component of the media.īitsPerSecond?: number // The chosen bitrate for the audio and video components of the media. "audio/webm" or "video/webm"ĪudioBitsPerSecond?: number // The chosen bitrate for the audio component of the media. MimeType?: string // optional mime type of the stream, e.g. Video: boolean // whether or not to enable video Audio: boolean // whether or not to enable audio
0 kommentar(er)
