Leanpub Header

Skip to main content

Filters

Category: "Testing"

Testing

New to Software Testing? Read the Software Testing article

  1. Adversarial Bash
    Adversarial Bash
    Build Your Own Pentest Arsenal — In Bash
    Andrew Ingram

    Most offensive-security books hand you a framework and a flag. This one hands you a terminal prompt and a target. Apex Foundry is a precision-manufacturing company that builds industrial control interfaces, runs a customer-facing web application backed by Postgres, operates an Active Directory domain for its corporate workforce, and recently bolted an AI assistant onto its support portal. It also happens to be running entirely inside your homelab — Docker containers, a virtual AD forest, and a vulnerable web stack you control end to end. Your job is to break it. Your constraint is that every tool you use must be one you wrote yourself, in Bash. Over thirteen chapters you will work through a single, continuous penetration test — from passive reconnaissance through data exfiltration and final reporting. Each chapter adds a link to the attack chain: you will build port scanners with `/dev/tcp`, web crawlers with `curl`, SQL-injection extractors with pipes and string manipulation, a prompt-injection fuzzer with `jq`, a cron-persisted reverse-shell implant, Kerberoasting wrappers, a covert DNS exfiltration channel with `dig`, and a report generator that pulls every finding into a finished deliverable. Every tool is a script you can paste into any Linux terminal with zero dependencies beyond a standard installation. Along the way you will capture twenty flags (format: `APEX{...}`) and document twenty-two findings, building a portfolio that doubles as a real-world pentest report. Why Bash?Python dominates offensive tooling for good reason — it is powerful, readable, and everywhere. Rust compiles to fast, dependency-free binaries. But Bash offers something neither can: - It is already on the target. Every Linux host, every container, every cloud instance ships with a POSIX shell. There is nothing to install, nothing to upload, nothing to compile. Your tool is the terminal.- No forensic footprint. A Bash script leaves no binary on disk, no interpreter to flag, no package manager log. When you pipe commands through a reverse shell, the tool exists only in memory and in process lists.- Living off the land. `curl`, `dig`, `awk`, `grep`, `find`, `openssl`, `base64`, `xxd`, `sqlite3` — standard utilities that defenders expect to see in log files. Using them for offense is indistinguishable from normal administration.- Instant iteration. No compile step, no dependency resolution, no virtual environment. Edit, run, observe. The feedback loop is measured in keystrokes.- Universal skill transfer. Every sysadmin writes Bash. Learning to weaponize it teaches you to defend against the same techniques — because the attacker at the keyboard looks exactly like the admin. This book does not replace your Python toolkit or your compiled Rust binaries. It extends your capabilities into the space where those tools cannot go — the compromised host where you have a shell and nothing else.

  2. Projects, Lifecycle, and Reference
    Projects, Lifecycle, and Reference
    Complete AI applications in Laravel, models across the development lifecycle, and the reference you keep at your desk
    Jeremy Kavuncuoglu

    Eight complete Laravel AI applications, built end to end with every trade-off argued, from a SQL agent that can’t be talked into leaking data to a voice assistant on a latency budget. Then use models to write, test, and review your own code without losing control of quality.

  3. Guía Práctica para Entrevistas de Trabajo en Japonés
    Guía Práctica para Entrevistas de Trabajo en Japonés
    Protocolo, keigo, vestimenta y 112 preguntas de entrevista con respuesta modelo, romaji y traducción al español.
    Joel Almánzar

    Ganar una entrevista en Japón empieza mucho antes de entrar por la puerta: investigación, documentos, horarios y las primeras palabras en recepción.

  4. Nasdanika SDK Runtime - Harness
    Nasdanika SDK Runtime - Harness
    Tests That Leave a Trace
    Pavel Vlasov

    Integration tests whose requests and the server's work are one OpenTelemetry trace, in one JVM, with no collector or backend, recorded as a model you can query.

  5. Nasdanika SDK Runtime - Playwright
    Nasdanika SDK Runtime - Playwright
    Browser Tests That Leave a Picture Book and a Trace
    Pavel Vlasov

    Browser tests that leave a picture book and a trace: Playwright from Java, with each step a span, the server's work under it, and screenshots recorded in the step.

  6. Agentic Engineering: The Scar Table
    Agentic Engineering: The Scar Table
    Agents write the code now. The engineering is in everything around it.
    Labeeb Bappu

    AI agents can write code, pass tests, and still leave you with a broken product. Agentic Engineering: The Scar Table explores the real failures, hard-earned lessons, and engineering principles behind building reliable software with AI agents. Learn how to move beyond code generation toward systems you can verify, trust, and maintain.

  7. LLM evaluation for developers
    LLM evaluation for developers
    Evals, LLM-as-a-judge and regression testing for AI applications, with Python examples and TypeScript notes
    30labs
    No Description Available
  8. AI Across the Testing Pyramid
    AI Across the Testing Pyramid
    A Practitioner's Field Guide to AI-Augmented Quality Engineering
    Santiago Rodríguez Gutiérrez

    A short, tool-agnostic field guide to what AI really changes at the unit, integration and end-to-end levels of testing, and how to adopt it without losing trust in your suite.

  9. Engineering Reliable AI-Assisted Code
    Engineering Reliable AI-Assisted Code
    A Practical Framework for Learning, Ethical Governance, and AGI Preparation
    Phillip Nakata

    Go beyond a plausible patch: trace its impact, choose meaningful tests, and make the merge decision reviewable.

  10. System Design Engineering Handbook
    System Design Engineering Handbook
    A Field Manual for Production Software Architecture
    Fadi Al-Najjar

    Master practical system design with 62 parts covering distributed systems, scalability, databases, security, and production architecture. A comprehensive engineering handbook with real-world examples, diagrams, and decision frameworks.

  11. Toyota Production System Concepts
    Toyota Production System Concepts
    Jidoka: The Secret Behind Toyota’s Smart Automation
    Mohammed Hamed Ahmed Soliman

    Discover how Toyota's century-old innovation can help you build better systems today.

  12. Holistic Testing Deutsche Edition "Holistisches Testmodell"
    Holistic Testing Deutsche Edition "Holistisches Testmodell"
    Qualität integrieren von Anfang an und in jeder Phase
    Janet Gregory, Joachim Decker, and Lisa Crispin

    In diesem Buch geht es um das Holistic Testing Model (Holistische Testmodell) und darum, wie es angewendet werden kann, um eine Qualitäts- und Teststrategie für das gesamte Team zu entwickeln. Es baut auf unserem früheren Mini-Buch auf und behandelt die Themen ausführlicher und anhand weiterer Beispiele.

  13. Agentic QA
    Agentic QA
    Building a Multi-Agent Testing Team with LLMs, Playwright and MCP
    Enrique A. De Coss

    Go from “AI as a copilot” to a team of AI testing agents that analyze, design, run, triage and review tests, with a human test lead making the decisions. Hands-on, in TypeScript, and vendor-agnostic: Claude, GPT, Gemini or a local model, with tools shared through MCP.

  14. PROMPT ENGINEERING BASICS FOR DEVELOPERS
    PROMPT ENGINEERING BASICS FOR DEVELOPERS
    Write Better Prompts with GPT-6
    Anshuman Mishra

    Vague prompts produce vague results. This book shows developers how to write clear, testable prompts for real coding tasks—explanations, functions, debugging, tests, and more—using a simple, repeatable method: state the goal, give the right context, set constraints, define the output, and verify the result.Written for beginners and working developers who want better AI-assisted work without treating model output as automatically correct.

  15. YOUR FIRST 30 DAYS WITH AI CODING ASSISTANTS
    YOUR FIRST 30 DAYS WITH AI CODING ASSISTANTS
    FROM ZERO TO PRODUCTIVE
    Anshuman Mishra

    A practical 30-day plan that turns complete beginners into confident, responsible users of AI coding assistants.Learn how to set clear goals, build a small project, debug with purpose, use Git, write better code, and present your work — all while using AI as a learning partner, not a crutch.