Harness engineering beginner tutorial, from 0 to 1
TypeScript agentagenticagentic-aiaiai-agentai-agentsdshdsh-pluginharnessharness-engineeringharness-frameworkllm
Fix broken Goodreads link for "How Google Tests Software"
sanbuphy2fdc46b20a3d
diff --git a/docs/ar/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/ar/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex 77aadad..8ee7907 100644--- a/docs/ar/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/ar/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -126,7 +126,7 @@ flowchart LR- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — يحدد صراحةً قائمة الميزات باعتبارها "هيكل البيانات الأساسي" للتحكم في نطاق agent- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — يؤكد على مبدأ "إخراج القطع الأثرية إلى الخارج"- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — مبادئ تصميم العقود، الأساس النظري لقوائم الميزات-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — هرم الاختبار وممارسات هندسة المواصفات السلوكية+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — هرم الاختبار وممارسات هندسة المواصفات السلوكية## تمارينdiff --git a/docs/ar/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/ar/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex 59d8a07..c618bed 100644--- a/docs/ar/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/ar/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -144,7 +144,7 @@ FIX: Move file operations to src/preload/file-ops.ts and call via window.api.rea## قراءات إضافية-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — المصدر الكلاسيكي لنموذج هرم الاختبار+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — المصدر الكلاسيكي لنموذج هرم الاختبار- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — ممارسات هندسية للتنفيذ الآلي للقيود المعمارية- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — حقن الأعطال استباقيًا للتحقق من مرونة النظام- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — منهجية اختبار الخصائص، تقع بين اختبار الأمثلة والتحقق الشكليdiff --git a/docs/de/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/de/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex 2b88578..62211e6 100644--- a/docs/de/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/de/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -127,7 +127,7 @@ Quantifiziertes Ergebnis: Projekte mit strukturierten Feature-Listen zeigen eine- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — Identifiziert die Feature-Liste ausdrücklich als "core data structure" zur Kontrolle des Agenten-Scopes- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Betont das Prinzip der "externalizing artifacts"- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — Contract-Design-Prinzipien, theoretische Grundlage von Feature-Listen-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Testpyramide und Praktiken für verhaltensbasierte Spezifikation+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Testpyramide und Praktiken für verhaltensbasierte Spezifikation## Übungendiff --git a/docs/de/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/de/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex d8bc53c..2ff7028 100644--- a/docs/de/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/de/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -144,7 +144,7 @@ Alle 5 Defekte wurden von End-to-End-Tests gefunden, während Unit-Tests keinen## Weiterführende Literatur-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Die klassische Quelle des Testing-Pyramid-Modells+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Die klassische Quelle des Testing-Pyramid-Modells- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Engineering-Praktiken für die automatisierte Ausführung von Architektur-Einschränkungen- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — Proaktives Injizieren von Fehlern zur Überprüfung der Systemresilienz- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — Property-Testing-Methodik, angesiedelt zwischen Beispiel-Testing und formaler Verifikationdiff --git a/docs/en/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/en/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex a1f03b0..f03a8f9 100644--- a/docs/en/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/en/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -131,7 +131,7 @@ Quantified result: projects using structured feature lists show 45% higher featu- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — Explicitly identifies feature list as the "core data structure" for controlling agent scope- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Emphasizes the principle of "externalizing artifacts"- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — Design by contract principles, the theoretical foundation of feature lists-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Test pyramid and behavioral specification engineering practices+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Test pyramid and behavioral specification engineering practices## Exercisesdiff --git a/docs/en/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/en/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex 720f430..65f28b8 100644--- a/docs/en/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/en/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -142,7 +142,7 @@ All 5 defects were caught by end-to-end tests; unit tests caught none. The trade## Further Reading-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — The classic source of the Testing Pyramid model+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — The classic source of the Testing Pyramid model- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Engineering practices for automated enforcement of architectural constraints- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — Proactively injecting failures to verify system resilience- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — Property testing methodology, sitting between example-based testing and formal verificationdiff --git a/docs/es/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/es/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex 2ac67ff..8a6677b 100644--- a/docs/es/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/es/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -127,7 +127,7 @@ Resultado cuantificado: los proyectos que usan listas de funciones estructuradas- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — Identifica explícitamente la lista de funciones como "core data structure" para controlar el alcance del agente- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Enfatiza el principio de "externalizar artefactos"- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — Principios de diseño por contrato, base teórica de las listas de funciones-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Pirámide de tests y prácticas de especificación conductual+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Pirámide de tests y prácticas de especificación conductual## Ejerciciosdiff --git a/docs/es/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/es/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex 17370f0..32bdc83 100644--- a/docs/es/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/es/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -144,7 +144,7 @@ Los 5 defectos fueron detectados por las pruebas end-to-end, mientras que las pr## Lecturas adicionales-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — La fuente clásica del modelo de Pirámide de Testing+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — La fuente clásica del modelo de Pirámide de Testing- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Prácticas de ingeniería para la ejecución automatizada de restricciones arquitectónicas- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — Inyección proactiva de fallas para verificar la resiliencia del sistema- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — Metodología de property testing, situada entre las pruebas de ejemplo y la verificación formaldiff --git a/docs/fr/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/fr/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex fe3da9c..b1e2975 100644--- a/docs/fr/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/fr/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -127,7 +127,7 @@ Résultat quantifié : les projets utilisant des listes de fonctionnalités stru- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — Identifie explicitement la liste de fonctionnalités comme la "core data structure" pour contrôler la portée de l'agent- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Met l'accent sur le principe d'"externalisation des artefacts"- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — Principes de design par contrat, fondation théorique des listes de fonctionnalités-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Pyramide de tests et pratiques d'ingénierie de spécification comportementale+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Pyramide de tests et pratiques d'ingénierie de spécification comportementale## Exercicesdiff --git a/docs/fr/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/fr/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex bb546a2..58a537e 100644--- a/docs/fr/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/fr/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -144,7 +144,7 @@ Les 5 défauts ont été détectés par les tests de bout en bout, tandis que le## Pour aller plus loin-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — La source classique du modèle de pyramide de tests+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — La source classique du modèle de pyramide de tests- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Pratiques d'ingénierie pour l'exécution automatisée des contraintes architecturales- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — Injection proactive de pannes pour vérifier la résilience du système- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — Méthodologie de test par propriétés, entre le test par l'exemple et la vérification formellediff --git a/docs/ja/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/ja/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex 0c7df27..ffa1346 100644--- a/docs/ja/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/ja/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -127,7 +127,7 @@ flowchart LR- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — エージェントのスコープ制御における「中核データ構造」として機能リストを明示- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — 「成果物を外部化する」原則を強調- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — 契約設計の原則、機能リストの理論的基盤-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — テストピラミッドと振る舞い仕様の実践+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — テストピラミッドと振る舞い仕様の実践## 演習diff --git a/docs/ja/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/ja/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex 3c8c7ea..84ff412 100644--- a/docs/ja/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/ja/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -144,7 +144,7 @@ FIX: Move file operations to src/preload/file-ops.ts and call via window.api.rea## 参考資料-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — テスティングピラミッドモデルの古典的出典+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — テスティングピラミッドモデルの古典的出典- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — アーキテクチャ制約の自動実行のためのエンジニアリング実践- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — 能動的に障害を注入してシステムの回復力を検証- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — プロパティテスト手法、例示テストと形式検証の中間に位置するdiff --git a/docs/ko/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/ko/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex 77d1940..225e62b 100644--- a/docs/ko/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/ko/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -126,7 +126,7 @@ flowchart LR- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — 기능 목록을 에이전트 범위 제어를 위한 "핵심 데이터 구조"로 명시적으로 식별- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — "산출물 외부화" 원칙 강조- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — 계약 설계 원칙, 기능 목록의 이론적 기반-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — 테스트 피라미드와 동작 명세 엔지니어링 실천+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — 테스트 피라미드와 동작 명세 엔지니어링 실천## 연습 문제diff --git a/docs/ko/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/ko/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex b4a0e41..4472b4f 100644--- a/docs/ko/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/ko/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -144,7 +144,7 @@ FIX: Move file operations to src/preload/file-ops.ts and call via window.api.rea## 더 읽을거리-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — 테스팅 피라미드 모델의 고전적 원천+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — 테스팅 피라미드 모델의 고전적 원천- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — 아키텍처 제약의 자동화된 실행을 위한 엔지니어링 실천- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — 시스템 복원력 검증을 위한 능동적 장애 주입- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — 예제 테스트와 형식 검증 사이에 위치한 속성 테스팅 방법론diff --git a/docs/pt-BR/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/pt-BR/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex 1589542..a646e7d 100644--- a/docs/pt-BR/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/pt-BR/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -131,7 +131,7 @@ Resultado quantificado: projetos que utilizam listas de funcionalidades estrutur* [Construindo Agentes Eficazes - Anthropic](https://www.anthropic.com/research/building-effective-agents) — Identifica explicitamente a lista de funcionalidades como a "estrutura de dados central" para controlar o escopo do agente.* [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Enfatiza o princípio da "externalização de artefatos".* [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — Princípios de Design by Contract, a base teórica das listas de funcionalidades.-* [Como o Google testa softwares](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Pirâmide de testes e práticas de engenharia de especificação comportamental.+* [Como o Google testa softwares](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Pirâmide de testes e práticas de engenharia de especificação comportamental.## Exercíciosdiff --git a/docs/pt-BR/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/pt-BR/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex b7ac59e..0d729d8 100644--- a/docs/pt-BR/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/pt-BR/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -142,7 +142,7 @@ Todos os 5 defeitos foram detectados pelos testes end-to-end; os testes unitári## Leitura Complementar-- [Como o Google testa softwares - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — A fonte clássica do modelo da Pirâmide de Testes+- [Como o Google testa softwares - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — A fonte clássica do modelo da Pirâmide de Testes- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Práticas de engenharia para aplicação automatizada de restrições arquiteturais- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — Injeção proativa de falhas para verificar a resiliência de sistemas- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — Metodologia de testes baseados em propriedades, posicionada entre testes baseados em exemplos e verificação formaldiff --git a/docs/ru/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/ru/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex 9270d9b..747d700 100644--- a/docs/ru/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/ru/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -126,7 +126,7 @@ flowchart LR- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — явно называет список фич «ключевой структурой данных» для контроля скоупа агента- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — подчёркивает принцип «выноса артефактов наружу»- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — принципы проектирования по контракту, теоретическая основа списков фич-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — пирамида тестирования и инженерные практики поведенческой спецификации+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — пирамида тестирования и инженерные практики поведенческой спецификации## Упражненияdiff --git a/docs/ru/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/ru/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex a4e9513..4d6707a 100644--- a/docs/ru/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/ru/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -144,7 +144,7 @@ FIX: Перенесите файловые операции в src/preload/file-## Дополнительное чтение-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Классический источник модели тест-пирамиды+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Классический источник модели тест-пирамиды- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Инженерные практики для автоматизированного выполнения архитектурных ограничений- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — Проактивное внедрение отказов для проверки устойчивости системы- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — Методология property-тестирования, расположенная между примерным тестированием и формальной верификациейdiff --git a/docs/tr/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/tr/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex 900eb58..306dc3c 100644--- a/docs/tr/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/tr/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -126,7 +126,7 @@ Nicel sonuç: yapılandırılmış özellik listeleri kullanan projeler serbest- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — Özellik listesini ajan kapsamını kontrol etmek için "temel veri yapısı" olarak açıkça tanımlar- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — "Artefaktları dışsallaştırma" ilkesini vurgular- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — Sözleşme tasarım ilkeleri, özellik listelerinin teorik temeli-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Test piramidi ve davranışsal spesifikasyon mühendislik uygulamaları+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Test piramidi ve davranışsal spesifikasyon mühendislik uygulamaları## Alıştırmalardiff --git a/docs/tr/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/tr/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex 0916f7e..b13f4b4 100644--- a/docs/tr/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/tr/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -144,7 +144,7 @@ Kod incelemesi sırasında yeni bir ajan hatası türü bulunduğunda, onu otoma## Daha fazla okuma-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Test Piramidi modelinin klasik kaynağı+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Test Piramidi modelinin klasik kaynağı- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Mimari kısıtlamaların otomatik yürütülmesi için mühendislik uygulamaları- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — Sistem dayanıklılığını doğrulamak için proaktif olarak başarısızlık enjekte etmek- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — Özellik testi metodolojisi, örnek testi ile resmi doğrulama arasındadiff --git a/docs/uk/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/uk/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex 071d7c0..57d792b 100644--- a/docs/uk/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/uk/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -131,7 +131,7 @@ E-commerce платформа з 10 функціями. Порівняння д- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — явно визначає список функціональності як «ключову структуру даних» для контролю обсягу агента- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — підкреслює принцип «екстерналізації артефактів»- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — принципи проєктування за контрактом, теоретична основа списків функціональності-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — піраміда тестування та інженерні практики поведінкової специфікації+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — піраміда тестування та інженерні практики поведінкової специфікації## Вправиdiff --git a/docs/uk/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/uk/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex c243879..fde1332 100644--- a/docs/uk/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/uk/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -142,7 +142,7 @@ FIX: Move file operations to src/preload/file-ops.ts and call via window.api.rea## Додаткова література-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Класичне джерело моделі Testing Pyramid+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Класичне джерело моделі Testing Pyramid- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Інженерні практики автоматизованого забезпечення архітектурних обмежень- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — Проактивне введення збоїв для верифікації стійкості системи- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — Методологія тестування властивостей, що знаходиться між тестуванням на прикладах та формальною верифікацієюdiff --git a/docs/uz/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/uz/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex 3393e5a..13e5cb8 100644--- a/docs/uz/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/uz/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -126,7 +126,7 @@ Miqdoriy natija (Quantified result): Strukturalangan funksiyalar roʻyxatidan (s- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — Funksiyalar roʻyxatini (feature list) agent skoupini (scope) boshqarish uchun “asosiy maʼlumotlar strukturasi” ekanligini aniq koʻrsatib beradi.- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — "artefaktlarni tashqariga chiqarish" (externalizing artifacts) tamoyilini alohida taʼkidlaydi.- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — Shartnoma dizayni tamoyillari (Contract design principles), funksiyalar roʻyxatining nazariy asosi.-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Test piramidasi (Test pyramid) va xulq-atvor (behavioral) spetsifikatsiyasi muhandislik amaliyotlari.+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Test piramidasi (Test pyramid) va xulq-atvor (behavioral) spetsifikatsiyasi muhandislik amaliyotlari.## Mashqlardiff --git a/docs/uz/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/uz/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex 8005772..e249589 100644--- a/docs/uz/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/uz/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -144,7 +144,7 @@ Yuqoridagi 5 muammoni E2E tutilganida, unit testlarning birontasi ushlab qola ol## Qoʻshimcha oʻqish uchun-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Testlash Piramidasining klassik va ommaviy asosi+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Testlash Piramidasining klassik va ommaviy asosi- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Arxitektura cheklovlarini avtomatik bajarish boʻyicha muhandislik amaliyotlari- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — Tizim bardoshliligini tekshirish uchun ataylab xatoliklarni kiritish- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — Property testing metodikasi: misol-testlash va formal verifikatsiya orasidagi yondashuvdiff --git a/docs/vi/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/vi/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex 7c68a47..8cefbe9 100644--- a/docs/vi/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/vi/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -131,7 +131,7 @@ Kết quả định lượng: các dự án dùng feature list có cấu trúc- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — Xác định rõ feature list là "cấu trúc dữ liệu cốt lõi" để kiểm soát phạm vi agent- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Nhấn mạnh nguyên tắc "đưa artifact ra ngoài"- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — Nguyên tắc thiết kế theo hợp đồng, nền tảng lý thuyết của feature list-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Tháp kiểm thử và thực hành kỹ thuật đặc tả hành vi+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Tháp kiểm thử và thực hành kỹ thuật đặc tả hành vi## Bài tậpdiff --git a/docs/vi/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/vi/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex bf7b1d3..8fa069b 100644--- a/docs/vi/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/vi/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -142,7 +142,7 @@ Cả 5 khiếm khuyết đều bị end-to-end test bắt, unit test không bắ## Đọc thêm-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — Nguồn gốc kinh điển của mô hình Tháp kiểm thử+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — Nguồn gốc kinh điển của mô hình Tháp kiểm thử- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — Thực hành kỹ thuật cho việc thực thi tự động ràng buộc kiến trúc- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — Chủ động cấy lỗi để xác minh độ bền hệ thống- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — Phương pháp property testing, nằm giữa example testing và kiểm chứng hình thứcdiff --git a/docs/zh-TW/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/zh-TW/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex 875393e..b30533c 100644--- a/docs/zh-TW/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/zh-TW/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -131,7 +131,7 @@ agent 不能直接把狀態改成 `passing`。它只能提交驗證請求,harn- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — 明確指出功能清單是控制 agent 執行範圍的「核心資料結構」- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — 強調「將工件外部化」的原則- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — 契約式設計原則,功能列表的理論基礎-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — 測試金字塔和行為規格的工程實踐+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — 測試金字塔和行為規格的工程實踐## 練習diff --git a/docs/zh-TW/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/zh-TW/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex 3f62fc8..593af3f 100644--- a/docs/zh-TW/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/zh-TW/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -144,7 +144,7 @@ FIX: Move file operations to src/preload/file-ops.ts and call via window.api.rea## 延伸閱讀-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software),測試金字塔模型的經典來源+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y),測試金字塔模型的經典來源- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/),架構約束自動化執行的工程實踐- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237),主動注入故障驗證系統彈性- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf),屬性測試方法,介於示例測試和形式化驗證之間diff --git a/docs/zh/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md b/docs/zh/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.mdindex d576adb..640a15e 100644--- a/docs/zh/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md+++ b/docs/zh/lectures/lecture-08-why-feature-lists-are-harness-primitives/index.md@@ -131,7 +131,7 @@ agent 不能直接把状态改成 `passing`。它只能提交验证请求,harn- [Building Effective Agents - Anthropic](https://www.anthropic.com/research/building-effective-agents) — 明确指出功能列表是控制 agent 执行范围的"核心数据结构"- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — 强调"将工件外部化"的原则- [Design by Contract - Bertrand Meyer](https://www.goodreads.com/book/show/130439.Object_Oriented_Software_Construction) — 契约式设计原则,功能列表的理论基础-- [How Google Tests Software](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — 测试金字塔和行为规格的工程实践+- [How Google Tests Software](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — 测试金字塔和行为规格的工程实践## 练习diff --git a/docs/zh/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md b/docs/zh/lectures/lecture-10-why-end-to-end-testing-changes-results/index.mdindex d119f8f..6d8c31f 100644--- a/docs/zh/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md+++ b/docs/zh/lectures/lecture-10-why-end-to-end-testing-changes-results/index.md@@ -142,7 +142,7 @@ FIX: Move file operations to src/preload/file-ops.ts and call via window.api.rea## 延伸阅读-- [How Google Tests Software - Whittaker et al.](https://www.goodreads.com/book/show/13563030-how-google-tests-software) — 测试金字塔模型的经典来源+- [How Google Tests Software - Whittaker et al.](https://books.google.dk/books/about/How_Google_Tests_Software.html?id=VrAx1ATf-RoC&redir_esc=y) — 测试金字塔模型的经典来源- [Harness Engineering - OpenAI](https://openai.com/index/harness-engineering/) — 架构约束自动化执行的工程实践- [Chaos Engineering - Netflix (Basiri et al.)](https://ieeexplore.ieee.org/document/7466237) — 主动注入故障验证系统弹性- [QuickCheck - Claessen & Hughes](https://www.cs.tufts.edu/~nr/cs257/archive/john-hughes/quick.pdf) — 属性测试方法,介于示例测试和形式化验证之间