{"query":"testing","total":45,"page":1,"results_per_page":10,"results":[{"path":"core/testing/unit_testing_principles.md","title":"Unit Testing Principles: FIRST, the Test Pyramid, and What Makes a Test Good","description":"The pyramid-vs-trophy debate (Fowler/Google vs. Kent C. Dodds) with attribution, Google's small/medium/large size taxonomy and 80/15/5 split, the Luo et al. flaky-test root-cause taxonomy with real percentages, and mutation testing as the actual suite-quality signal coverage isn't.","language":null,"category":"testing_general","difficulty":"beginner","tags":["unit-testing","testing","tdd","test-pyramid","testing-trophy","flaky-tests","mutation-testing","best-practices","pytest"],"score":0.7212},{"path":"core/testing/integration_testing.md","title":"Integration Testing: Real Boundaries, Ephemeral Infrastructure, and Contract Testing","description":"How to test across real system boundaries - databases, HTTP APIs, and message queues - using ephemeral test infrastructure (Testcontainers) and consumer-driven contract testing (Pact-style), with an honest accounting of trade-offs against pure unit tests.","language":null,"category":"testing_general","difficulty":"intermediate","tags":["integration-testing","testing","testcontainers","contract-testing","pact","microservices","database-testing"],"score":0.7201},{"path":"languages/python/testing.md","title":"Python Testing Guide: pytest Ecosystem (2026)","description":"A practical guide to the modern pytest ecosystem: fixtures and scoping, parametrization, coverage.py, Hypothesis property-based testing, pytest-xdist parallelism, and pytest-mock for maintainable, fast test suites.","language":"python","category":"language_testing","difficulty":"intermediate","tags":["testing","pytest","unit-testing","property-based-testing","mocking","coverage","tdd"],"score":0.7171},{"path":"languages/nim/testing.md","title":"Nim Testing: unittest, nimble test, and testament (2026)","description":"Verified guidance on Nim's std/unittest module (check vs require, suites, setup/teardown), nimble test conventions, when testament's compiler-oriented test runner is and is not appropriate for application code, and the honest current state of property-based testing in Nim.","language":"nim","category":"language_testing","difficulty":"intermediate","tags":["testing","unittest","testament","nimble","unit-testing","integration-testing","property-based-testing","tdd"],"score":0.7148},{"path":"core/security/penetration_testing_methodology.md","title":"Penetration Testing Methodology: Lifecycle, Frameworks, and Reporting","description":"The full authorized penetration-testing lifecycle - legal prerequisites, methodology frameworks (PTES, OWASP WSTG, NIST SP 800-115, OSSTMM, MITRE ATT&CK), engagement phases, exploitation frameworks, and coordinated disclosure - tying together OSINT reconnaissance and vulnerability scanning.","language":null,"category":"security_general","difficulty":"advanced","tags":["penetration-testing","red-team","rules-of-engagement","responsible-disclosure","mitre-attack","best-practices","security","vulnerability-management","reporting"],"score":0.7114},{"path":"languages/go/best_practices.md","title":"Go Best Practices","description":"Current idiomatic-vs-outdated verdicts for Go error handling (errors.AsType, errors.Join), concurrency (WaitGroup.Go, testing/synctest, errgroup), and context.Context - backed by named production goroutine-leak research (Uber LeakProf/goleak) and verified Go 1.22-1.26 semantic changes, not restated Go-101 material.","language":"go","category":"language_best_practices","difficulty":"intermediate","tags":["best-practices","error-handling","goroutines","channels","context","concurrency","testing"],"score":0.707},{"path":"core/testing/mocking_strategies.md","title":"Mocking Strategies: Test Doubles, London vs Chicago Schools, and Avoiding Over-Mocking","description":"Precise definitions of dummies, stubs, fakes, spies, and mocks, the London (mockist) vs Chicago (classicist) schools of TDD, and concrete guidance on when mocking makes tests brittle and how to avoid over-mocking.","language":null,"category":"testing_general","difficulty":"intermediate","tags":["mocking","test-doubles","tdd","unit-testing","stubs","fakes","best-practices"],"score":0.703},{"path":"core/security/vulnerability_scanning.md","title":"Vulnerability Scanning: Discovery Methodology, Tooling, and Management","description":"Comprehensive reference on automated vulnerability discovery across network, web application, dependency, container, infrastructure-as-code, and secrets scanning, plus the CVE/CVSS-driven triage and remediation lifecycle, for engineers scanning systems they are authorized to test.","language":null,"category":"security_general","difficulty":"intermediate","tags":["vulnerability-scanning","sca","dependency-scanning","container-scanning","secrets-scanning","cvss","cspm","best-practices","security"],"score":0.6929},{"path":"core/architecture/component_tree_tui_architecture.md","title":"Component Tree Architecture for Terminal User Interfaces","description":"Language-agnostic reference for building DOM-like component trees in TUIs: event bubbling from leaf to root, z-index compositing with dirty tracking, active/focus routing, hit-testing with clipping, animation delegation, and the engineering trade-offs that make this pattern earn its keep versus flat widget lists.","language":null,"category":"software_architecture","difficulty":"advanced","tags":["tui","terminal-ui","component-tree","event-bubbling","compositing","z-index","focus-management","hit-testing","clipping","rendering-pipeline","architecture","best-practices"],"score":0.6926},{"path":"core/security/owasp_top_10.md","title":"OWASP Top 10:2025 Web Application Security Risks","description":"The current OWASP Top 10:2025 web application security risk categories with concrete mitigation guidance and code-level examples for each, grounded in the official OWASP release.","language":null,"category":"security_general","difficulty":"intermediate","tags":["owasp","security","web-security","injection","authentication","access-control","supply-chain-security","best-practices"],"score":0.6906}]}