端到端测试工作流程
实施端到端测试策略，验证 Electron 桌面应用的完整用户流程与功能
端到端测试工作流程 是 CoddyKit 上的免费 Electron Desktop App Development 课时。 这是第 3 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Electron Desktop App Development 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Electron Desktop App Development 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
What is End-to-End Testing?
End-to-End (E2E) testing simulates real user scenarios to verify that an application works as expected from start to finish. Think of it as putting yourself in the user's shoes!
For Electron apps, E2E tests check if your UI (HTML/CSS/JS) correctly interacts with your backend logic (Node.js) and native OS features.
Why E2E for Electron Apps?
Electron applications are complex, combining web technologies with native desktop capabilities. Unit tests check small parts, but E2E ensures everything works together.
- Real User Flow: Mimics how a user navigates and interacts.
- Integration Checks: Verifies communication between main and renderer processes.
- Catch Regressions: Detects if new changes break existing features.
- Confidence: Gives you peace of mind that your app is stable.
Choosing an E2E Tool
Several tools can perform E2E testing for web applications, and many are adaptable for Electron. Popular choices include:
- Playwright: A modern framework from Microsoft, known for speed and reliability. It has built-in support for Electron.
- Cypress: A developer-friendly tool that runs tests directly in the browser (or Electron's renderer).
- WebDriver (Selenium): A classic choice, though often more complex to set up for Electron specifically.
We'll focus on Playwright due to its strong Electron support.
Setting Up Playwright for Electron
First, you need to install Playwright and its Electron driver in your project. Open your terminal in your Electron app's root directory and run:
npm install --save-dev @playwright/test playwright-electron
This command adds the necessary packages to your development dependencies. Remember, Playwright tests are typically run in a separate test folder.
Our Sample Electron App
To test, let's use a simple Electron app. Create these files in your project root:
package.json:
{ "name": "my-electron-app",
"version": "1.0.0",
"main": "main.js",
"scripts": {
"start": "electron ."
},
"devDependencies": {
"electron": "^28.0.0"
}
}Sample App: Main Process & UI
Next, create the main process file and the user interface:
main.js:
const { app, BrowserWindow } = require('electron');
const path = require('path');
function createWindow () {
const mainWindow = new BrowserWindow({
width: 800,
height: 600,
webPreferences: {
preload: path.join(__dirname, 'preload.js'),
nodeIntegration: false,
contextIsolation: true
}
});
mainWindow.loadFile('index.html');
}
app.whenReady().then(() => {
createWindow();
app.on('activate', () => {
if (BrowserWindow.getAllWindows().length === 0) createWindow();
});
});
app.on('window-all-closed', () => {
if (process.platform !== 'darwin') app.quit();
});Sample App: HTML & Preload
Finally, our simple UI and an empty preload script:
index.html:
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>My Electron App</title>
<style>
body { font-family: sans-serif; text-align: center; padding-top: 50px; }
h1 { color: #333; }
button { padding: 10px 20px; font-size: 16px; cursor: pointer; }
</style>
</head>
<body>
<h1>Hello, CoddyKit!</h1>
<p id="message">Click the button below.</p>
<button id="myButton">Change Message</button>
<script>
document.getElementById('myButton').addEventListener('click', () => {
document.getElementById('message').textContent = 'Message Changed!';
});
</script>
</body>
</html>Writing Your First E2E Test
Create a file named e2e.spec.js in a tests folder. This test launches your Electron app and verifies its title.
tests/e2e.spec.js:
const { test, expect, _electron: electron } = require('@playwright/test');
test('app launches and shows title', async () => {
// Launch the Electron app from the current directory
const electronApp = await electron.launch({ args: ['.'] });
// Get the first window that opens
const window = await electronApp.firstWindow();
// Assert the window title
expect(await window.title()).toBe('My Electron App');
// Close the app after the test
await electronApp.close();
});Interacting & Asserting
Let's expand our test to click the button and verify the message changes. This demonstrates user interaction and making assertions.
Add to tests/e2e.spec.js:
const { test, expect, _electron: electron } = require('@playwright/test');
// ... (previous test)
test('button click changes message', async () => {
const electronApp = await electron.launch({ args: ['.'] });
const window = await electronApp.firstWindow();
// Locate the paragraph and button elements by their IDs
const messageParagraph = window.locator('#message');
const button = window.locator('#myButton');
// Wait for elements to be visible and check initial text
await messageParagraph.waitFor();
await expect(messageParagraph).toHaveText('Click the button below.');
// Click the button
await button.click();
// Assert that the text has changed
await expect(messageParagraph).toHaveText('Message Changed!');
await electronApp.close();
});E2E Workflow Check
Which of the following are key benefits of using End-to-End (E2E) testing for an Electron application?
Recap: E2E Workflows
In this lesson, we explored End-to-End (E2E) testing for Electron applications. We learned that E2E tests simulate full user interactions to ensure all parts of your app work together seamlessly.
- We identified Playwright as a powerful tool for Electron E2E.
- We set up a simple Electron app and wrote tests to launch it, interact with UI elements, and make assertions.
E2E testing is vital for building robust and reliable desktop applications!
常见问题解答
「端到端测试工作流程」课时是免费的吗？
是的 — 「端到端测试工作流程」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Electron Desktop App Development 课程的其余内容，请升级到 CoddyKit PRO。 Electron Desktop App Development 课程共包含 4 节课。
「端到端测试工作流程」这节课中我会学到什么？
实施端到端测试策略，验证 Electron 桌面应用的完整用户流程与功能 你通过在浏览器中直接运行的动手代码来练习 Electron Desktop App Development，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Electron Desktop App Development 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Electron Desktop App Development 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 3 节课，共 4 节。
「端到端测试工作流程」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Electron Desktop App Development 课中编写并运行代码吗？
能。每节 Electron Desktop App Development 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。