Run any Skill in Manus with one click

overview-drn-testing

Stars20

Forks3

UpdatedJune 12, 2026 at 19:52

DTT (Duran's Testing Technique) philosophy - choosing unit, integration, API, or performance tests and routing to canonical DRN.Framework.Testing guidance. Keywords: testing-philosophy, dtt, test-strategy, unit-testing, integration-testing, performance-testing

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

duranserkan

duranserkan/DRN-Project

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	overview-drn-testing
description	DTT (Duran's Testing Technique) philosophy - choosing unit, integration, API, or performance tests and routing to canonical DRN.Framework.Testing guidance. Keywords: testing-philosophy, dtt, test-strategy, unit-testing, integration-testing, performance-testing
last-updated	"2026-06-12T00:00:00.000Z"
difficulty	basic
tokens	~0.7K

DRN Testing Overview

DTT favors honest feedback with the least necessary test machinery. The canonical attribute/context matrix lives in drn-testing.

DTT Principles

Principle	Practice
Security first	Avoid leaking secrets in fixtures, logs, snapshots, and generated data
Correctness over speed	Prefer real dependencies when mocks would hide behavior
Clarity over cleverness	One readable flow beats many tiny duplicate tests
Simplicity	Use `[Fact]` when no data, generation, or context is needed
Performance with proof	Benchmark only when a performance question is explicit

Test Type Selection

Change	Default test type	Why
Pure utility, domain invariant, deterministic branch logic	Unit	No container value; use `DataInlineUnit` when data/generation helps
Attribute DI registration or isolated service behavior	Unit	`DrnTestContextUnit` validates wiring without Docker
Repository, EF mapping, query, transaction, concurrency	Integration DB	Real PostgreSQL is the useful signal
Controller, endpoint, auth, middleware, serialization	API integration	Full request pipeline via `ApplicationContext`
External HTTP client behavior	Integration/API	Use `FlurlHttpTest` against outbound URL patterns
Throughput, allocation, latency, load	Performance	BenchmarkDotNet/K6 only with explicit user intent

Project Shape

DRN.Test.Unit/         # isolated logic and service validation
DRN.Test.Integration/  # Testcontainers, repositories, API/E2E
DRN.Test.Performance/  # BenchmarkDotNet and K6

Context names:

DrnTestContextUnit: unit context, no containers
DrnTestContext: integration context with ContainerContext, ApplicationContext, and FlurlHttpTest
ApplicationContext: WebApplicationFactory wrapper for app/API tests

Routing

Need exact attribute/context rules or MTP commands: drn-testing
Writing isolated tests: test-unit
Choosing API vs DB integration: test-integration
Endpoint behavior: test-integration-api
Repository/database behavior: test-integration-db
Performance work: test-performance

More from this repository

same repository

drn-entityframework

duranserkan/DRN-Project

DRN.Framework.EntityFramework - DrnContext, migrations, entity lifecycle tracking, Npgsql configuration, repositories, and named repository cancellation scopes. Keywords: drncontext, ef-core, migrations, database, postgresql, npgsql, repository-implementation, repository-cancellation, cancellation-scope, entity-tracking, dbcontext-configuration, prototype-mode, testcontainers

2026-07-1520

drn-sharedkernel

duranserkan/DRN-Project

DRN.Framework.SharedKernel - Foundational domain primitives, exception hierarchy, repository contracts and cancellation semantics, pagination, JSON conventions, app constants, and shared extensions. Keywords: entity, aggregate-root, domain-event, repository, repository-cancellation, cancellation, pagination, exception, json, domain-modeling, source-known-id, entity-type, appconstants, path-extensions

2026-07-1520

drn-utils

duranserkan/DRN-Project

DRN.Framework.Utils - Attribute-based dependency injection, IAppSettings configuration, app data roots, logging, scoped cancellation, validators, extension methods, and core utilities. Keywords: dependency-injection, di, service-registration, configuration, appsettings, appdata, logging, scoped-log, cancellation, cancellation-scope, validators, attributes, scoped, singleton, transient, config, extensions, http-client

2026-07-1520

overview-skill-index

duranserkan/DRN-Project

Use when choosing which repository skills to load for a task, mapping work to skill families, finding related skills, or updating skill routing after skills change.

2026-07-1520

basic-agentic-development

duranserkan/DRN-Project

Agentic development standards - Silent Partner Protocol, context economy, development loop (discovery, planning, execution, verification), and anti-patterns for efficient autonomous development. Keywords: agentic, ai-agent, development-loop, context-economy, autonomous, discovery, planning, execution, verification, anti-patterns, silent-partner

2026-07-0720

basic-documentation

duranserkan/DRN-Project

Documentation standards - README structure, ROADMAP patterns, skill documentation format (YAML frontmatter), markdown conventions, security documentation, API docs, and best practices. Guidelines for creating and maintaining all project documentation. Keywords: documentation, readme, roadmap, markdown, documentation-standards, yaml-frontmatter, technical-writing, api-documentation, changelog

2026-07-0720

name	overview-drn-testing
description	DTT (Duran's Testing Technique) philosophy - choosing unit, integration, API, or performance tests and routing to canonical DRN.Framework.Testing guidance. Keywords: testing-philosophy, dtt, test-strategy, unit-testing, integration-testing, performance-testing
last-updated	"2026-06-12T00:00:00.000Z"
difficulty	basic
tokens	~0.7K

DRN Testing Overview

DTT favors honest feedback with the least necessary test machinery. The canonical attribute/context matrix lives in drn-testing.

DTT Principles

Principle	Practice
Security first	Avoid leaking secrets in fixtures, logs, snapshots, and generated data
Correctness over speed	Prefer real dependencies when mocks would hide behavior
Clarity over cleverness	One readable flow beats many tiny duplicate tests
Simplicity	Use `[Fact]` when no data, generation, or context is needed
Performance with proof	Benchmark only when a performance question is explicit

Test Type Selection

Change	Default test type	Why
Pure utility, domain invariant, deterministic branch logic	Unit	No container value; use `DataInlineUnit` when data/generation helps
Attribute DI registration or isolated service behavior	Unit	`DrnTestContextUnit` validates wiring without Docker
Repository, EF mapping, query, transaction, concurrency	Integration DB	Real PostgreSQL is the useful signal
Controller, endpoint, auth, middleware, serialization	API integration	Full request pipeline via `ApplicationContext`
External HTTP client behavior	Integration/API	Use `FlurlHttpTest` against outbound URL patterns
Throughput, allocation, latency, load	Performance	BenchmarkDotNet/K6 only with explicit user intent

Project Shape

DRN.Test.Unit/         # isolated logic and service validation
DRN.Test.Integration/  # Testcontainers, repositories, API/E2E
DRN.Test.Performance/  # BenchmarkDotNet and K6

Context names:

DrnTestContextUnit: unit context, no containers
DrnTestContext: integration context with ContainerContext, ApplicationContext, and FlurlHttpTest
ApplicationContext: WebApplicationFactory wrapper for app/API tests

Routing

Need exact attribute/context rules or MTP commands: drn-testing
Writing isolated tests: test-unit
Choosing API vs DB integration: test-integration
Endpoint behavior: test-integration-api
Repository/database behavior: test-integration-db
Performance work: test-performance