Adds useful debug features to your Electron app
86
{
"context": "This criteria evaluates how well the engineer studied the electron-debug package to understand and replicate its element inspection implementation. The focus is on correctly utilizing the same Electron webContents APIs that electron-debug uses internally for activating the DOM element inspector, handling different DevTools states, and properly coordinating the inspector activation.",
"type": "weighted_checklist",
"checklist": [
{
"name": "DevTools State Check",
"description": "Uses webContents.isDevToolsOpened() to check if DevTools are currently open before attempting inspector activation",
"max_score": 15
},
{
"name": "DevTools Opening",
"description": "Uses webContents.openDevTools() to open DevTools when they are not already open",
"max_score": 15
},
{
"name": "Inspector Activation Method",
"description": "Uses webContents.devToolsWebContents.executeJavaScript() with 'DevToolsAPI.enterInspectElementMode()' to activate the element inspector mode",
"max_score": 35
},
{
"name": "Async Event Handling",
"description": "Uses webContents.once('devtools-opened') event listener to properly coordinate inspector activation when DevTools need to be opened first, ensuring the inspector activates after DevTools finish opening",
"max_score": 25
},
{
"name": "Direct Activation",
"description": "Activates inspector immediately when DevTools are already open, without unnecessary delays or event listeners",
"max_score": 10
}
]
}Install with Tessl CLI
npx tessl i tessl/npm-electron-debugdocs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10