| { | |
| "Typescript default React component": { | |
| "prefix": "rfcd", | |
| "body": [ | |
| "import React, { FC } from 'react'", | |
| "", | |
| "interface ${TM_FILENAME_BASE/(.*)/${1:/pascalcase}/g}Props {", | |
| " $1", | |
| "}", | |
| "", |
| import fs from 'fs' | |
| // 转化Data URI scheme to image file | |
| const typeToExtName: Record<string, string> = { | |
| 'jpeg': '.jpeg', | |
| 'jpg': '.jpg', | |
| 'png': '.png', | |
| 'svg+xml': '.svg', | |
| 'gif': '.gif', | |
| 'webp': '.webp' |
| // 获取所有pages的截图以便确认是否页面还有用 | |
| // 1. 安装 npm i miniprogram-automator jest -D | |
| // 2. 项目根目录 node跑本文件 | |
| // 3. 最好package.json加入test命令 | |
| /* eslint-env jest */ | |
| const automator = require('miniprogram-automator'); | |
| const path = require('path'); |
As the web component specs continue to be developed, there has been little information on how to test them.
In particular the /deep/ combinator has been deprecated in Shadow DOM 1.0. This is particularly painful since
most end-to-end testing frameworks rely on elements being discoverable by XPath or calls to querySelector.
Elements in Shadow DOM are selectable by neither.
Webdriver.io has the standard actions by selectors, but also allows browser executable scripts to return an element
