0Pricing
Edge Computing with Cloudflare Workers & Deno · レッスン

エッジ向けテストとCI/CD

エッジアプリケーション向けに包括的なテスト戦略と継続的インテグレーション／継続的デリバリーのパイプラインを実装します

「エッジ向けテストとCI/CD」はCoddyKit上の無料Edge Computing with Cloudflare Workers & Denoレッスンです。 これはレッスン3/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはEdge Computing with Cloudflare Workers & Deno学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Edge Computing with Cloudflare Workers & Denoコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Why Test Edge Applications?

Developing for the edge introduces unique challenges like distributed deployments, varying network conditions, and diverse user locations. Thorough testing is crucial to ensure your edge applications are robust and reliable.

Without proper testing, subtle bugs can lead to inconsistent behavior across different regions, impacting user experience and application stability.

Unit Testing Edge Logic

Unit testing focuses on individual functions or modules in isolation. For Cloudflare Workers, this means testing the core logic of your request handlers or utility functions without deploying them.

  • Cloudflare Workers: Tools like Miniflare allow you to simulate the Worker environment locally, enabling fast unit and integration tests.
  • Deno: Deno has a built-in test runner (deno test) that makes writing and executing unit tests straightforward.

Deno Unit Test Example

Here's a simple Deno module with a function and a corresponding unit test. Deno's test runner can execute tests defined directly within your files or in separate test files.

To run this code: Save as greet.ts, then run deno run greet.ts for the main logic or deno test greet.ts for the tests.

export function greet(name: string): string {
  return `Hello, ${name}!`;
}

// This block runs when executed as a script (deno run)
if (import.meta.main) {
  console.log(greet("CoddyKit Learner"));
}

// Import Deno's built-in assert module for testing
import { assertEquals } from "https://deno.land/std@0.211.0/assert/mod.ts";

// Define a test suite using Deno.test
Deno.test("greet function returns correct greeting", () => {
  // Use assertEquals to check expected outcomes
  assertEquals(greet("World"), "Hello, World!");
  assertEquals(greet("Alice"), "Hello, Alice!");
  assertEquals(greet(""), "Hello, !");
});

Integration Testing Workers

Integration testing verifies that different parts of your edge application work together correctly. This could involve:

  • A Worker interacting with Cloudflare KV for data storage.
  • A Worker communicating with a Durable Object for state management.
  • Multiple Workers chained together via service bindings.

These tests often require a more comprehensive local environment simulation, like that provided by Miniflare for Cloudflare Workers.

End-to-End Testing for Edge Apps

End-to-End (E2E) testing simulates real user scenarios, covering the entire flow from client interaction through your edge application and back. For edge apps, E2E tests are vital to:

  • Verify global routing and caching behavior.
  • Test interactions with external services or APIs.
  • Ensure consistent performance and functionality across different geographic regions.

Tools like Playwright or Cypress can be adapted for E2E testing of edge deployments.

CI/CD Pipelines for Edge

Continuous Integration (CI) and Continuous Deployment (CD) are practices that automate the building, testing, and deployment of code. For edge applications, CI/CD ensures rapid, reliable, and consistent delivery of updates.

  • CI: Automates code integration, running tests, and building artifacts.
  • CD: Automates the deployment of validated code to production or staging environments.

This automation minimizes manual errors and speeds up the release cycle.

CI for Cloudflare Workers

A typical CI pipeline for Cloudflare Workers using tools like GitHub Actions might involve:

  1. Checkout Code: Fetch the repository.
  2. Install Dependencies: Run npm install or yarn install.
  3. Linting: Check code style and potential errors (e.g., ESLint).
  4. Run Tests: Execute unit and integration tests (e.g., using Miniflare or deno test).
  5. Build Worker: Use wrangler build to prepare the Worker for deployment.

If any step fails, the CI pipeline stops, preventing faulty code from progressing.

CD for Cloudflare Workers

After successful CI, the CD pipeline takes over to deploy your Worker. This often involves:

  1. Authenticate: Log in to Cloudflare using API tokens (stored securely as secrets).
  2. Deploy: Use wrangler deploy to push the built Worker to the Cloudflare edge network.
  3. Environment Management: Deploy to a staging environment for further testing before promoting to production.
  4. Rollback: Implement strategies to quickly revert to a previous working version if issues arise post-deployment.

CD ensures your users always get the latest, validated version of your application.

CI/CD for Deno Deploy

Deno Deploy offers a highly streamlined CI/CD experience, often simplifying the process compared to other platforms:

  • GitHub Integration: You can directly link a GitHub repository to Deno Deploy.
  • Automatic Deployments: Every push to a specified branch (e.g., main) automatically triggers a new deployment.
  • Instant Rollback: Deno Deploy keeps a history of deployments, allowing for one-click rollbacks to previous versions.

While simpler, you still integrate your Deno unit and integration tests into your GitHub Actions CI flow before Deno Deploy takes over for CD.

Edge CI/CD Check

Which of the following are key benefits of implementing CI/CD pipelines for edge applications?

Testing & CI/CD Summary

In this lesson, we explored the critical importance of testing and CI/CD for robust edge applications. We covered unit, integration, and E2E testing strategies, and delved into how CI/CD pipelines streamline the development and deployment process for both Cloudflare Workers and Deno Deploy.

By embracing these practices, you can build and deliver high-quality, reliable, and performant edge applications with confidence.

よくある質問

「エッジ向けテストとCI/CD」レッスンは無料ですか？

はい。「エッジ向けテストとCI/CD」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Edge Computing with Cloudflare Workers & Denoコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Edge Computing with Cloudflare Workers & Denoコースには全4レッスンが含まれています。

「エッジ向けテストとCI/CD」で何を学びますか？

エッジアプリケーション向けに包括的なテスト戦略と継続的インテグレーション／継続的デリバリーのパイプラインを実装します ブラウザで直接実行するハンズオンコードでEdge Computing with Cloudflare Workers & Denoを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Edge Computing with Cloudflare Workers & Denoを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのEdge Computing with Cloudflare Workers & Denoは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン3/4です。

「エッジ向けテストとCI/CD」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このEdge Computing with Cloudflare Workers & Denoレッスンでコードを書いて実行できますか？

はい。すべてのEdge Computing with Cloudflare Workers & Denoレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

  1. Deno DeployとCLI
  2. カスタムランタイム環境
  3. エッジ向けテストとCI/CD
  4. Blue-Greenデプロイと段階的ロールアウト
← Edge Computing with Cloudflare Workers & Denoに戻る