Add configuration docs

Author: roxblnfk

docs/benchmarks.md

@@ -0,0 +1,5 @@
+# Benchmarks
+
+::: info
+This functionality is provided by the `\Testo\Bench\BenchmarkPlugin` plugin, included in the `SuitePlugins` default set.
+:::

docs/configuration.md

@@ -0,0 +1,171 @@
+# Configuration
+
+By default, if no configuration file is provided, Testo will run tests from the `tests` folder with the default plugin set.
+
+To customize the configuration, create a `testo.php` file in the root of your project. The file must return an `ApplicationConfig` instance:
+
+```php
+<?php
+
+declare(strict_types=1);
+
+use Testo\Application\Config\ApplicationConfig;
+use Testo\Application\Config\SuiteConfig;
+
+return new ApplicationConfig(
+    suites: [
+        new SuiteConfig(
+            name: 'Unit',
+            parallel: true,
+            location: ['tests/Unit'],
+        ),
+        new SuiteConfig(
+            name: 'Feature',
+            location: ['tests/Feature'],
+        ),
+    ],
+);
+```
+
+## ApplicationConfig
+
+The root configuration object:
+
+- `suites` — array of Test Suites. Must contain at least one element — an empty array will cause an error.
+- `src` — location of the project source code. Will be used for code coverage in the future.
+- `plugins` — application-level plugins. Loaded before Test Suites and act globally (see [Plugins](#plugins) section).
+
+All parameters and their default values are described in the class itself — your IDE will show hints.
+
+## SuiteConfig
+
+Configuration for a single Test Suite: name, test location, and plugin set.
+
+```php
+// Simple form — array
+new SuiteConfig(
+    name: 'Unit',
+    location: ['tests/Unit'],
+    plugins: [new NamingConventionPlugin()],
+),
+
+// With customization — FinderConfig and SuitePlugins
+new SuiteConfig(
+    name: 'Unit',
+    location: new FinderConfig(
+        include: ['tests/Unit'],
+        exclude: ['tests/Unit/Stubs'],
+    ),
+    plugins: SuitePlugins::without(BenchmarkPlugin::class),
+),
+```
+
+::: tip
+Arrays in `location` and `plugins` are shorthands for `new FinderConfig(include: ...)` and `SuitePlugins::with(...)`. For more flexible configuration, use `FinderConfig` and `SuitePlugins` directly.
+:::
+
+::: question Can I disable application-level plugins for a specific Test Suite?
+No, application-level plugins are loaded before Test Suites and act globally.
+:::
+
+## FinderConfig
+
+Defines the file search scope — which directories and files to include or exclude. Paths are relative to the project root. Glob patterns and regular expressions are not supported.
+
+```php
+new FinderConfig(
+    include: ['tests'],
+    exclude: ['tests/Fixtures', 'tests/Stubs'],
+)
+```
+
+## Plugins
+
+Testo is built on [plugins](plugins.md) — they define how tests are discovered, executed, and processed. Plugins are registered at two levels:
+
+- **Application level** (`ApplicationConfig::$plugins`) — act globally across all Test Suites
+- **Test Suite level** (`SuiteConfig::$plugins`) — act only within a specific Test Suite
+
+If the `plugins` array is not specified, Testo uses the default plugin set.
+
+::: question Which application plugins are enabled by default?
+- [FilterPlugin](filtering.md)
+- TerminalPlugin
+- TeamcityPlugin
+:::
+
+::: question Which Test Suite plugins are enabled by default?
+- [LifecyclePlugin](lifecycle.md)
+- [InlineTestPlugin](inline-tests.md)
+- [BenchmarkPlugin](benchmarks.md)
+:::
+
+### Managing Plugins
+
+Use the `SuitePlugins` and `ApplicationPlugins` facades to configure plugins (identical API):
+
+::: code-group
+```php [with()]
+// Add NamingConventionPlugin to the default plugins
+// Other Test Suite plugins are preserved
+new SuiteConfig(
+    plugins: SuitePlugins::with(
+        new NamingConventionPlugin(),
+    ),
+)
+```
+```php [without()]
+// Remove BenchmarkPlugin from the default set
+// Other Test Suite plugins are preserved
+new SuiteConfig(
+    plugins: SuitePlugins::without(
+        BenchmarkPlugin::class,
+    ),
+)
+```
+```php [only()]
+// Only LifecyclePlugin — all others are disabled
+// Completely replaces the default set
+new SuiteConfig(
+    plugins: SuitePlugins::only(
+        new LifecyclePlugin(),
+    ),
+)
+```
+```php [Chaining]
+// Add one plugin and remove another
+// Methods can be chained together
+new SuiteConfig(
+    plugins: SuitePlugins::with(new NamingConventionPlugin())
+        ->without(BenchmarkPlugin::class),
+)
+```
+:::
+
+## Monorepo
+
+Since `suites` is a regular PHP array, configurations can be assembled from multiple modules. Each module has its own `testo.php` that works standalone and as a Test Suite source for the root config:
+
+```php
+// modules/billing/testo.php — works standalone
+return new ApplicationConfig(
+    suites: [
+        new SuiteConfig(
+            name: 'Billing',
+            location: ['tests'],
+        ),
+    ],
+);
+```
+
+```php
+// testo.php — root config assembles Test Suites from modules
+return new ApplicationConfig(
+    suites: array_merge(
+        (require 'modules/billing/testo.php')->suites,
+        (require 'modules/shipping/testo.php')->suites,
+    ),
+);
+```
+
+Each module manages its own test configuration independently, while the root config runs everything together.

docs/getting-started.md

@@ -44,16 +44,22 @@ return new ApplicationConfig(
             ),
         ),
         new SuiteConfig(
-            name: 'Source',
+            name: 'Sources',
             location: new FinderConfig(
                 include: ['src'],
             ),
+            plugins: SuitePlugins::only(
+                new InlineTestPlugin(),
+                new BenchmarkPlugin(),
+            ),
         ),
     ],
 );
 ```
 
-In this example we defined two test suites: `Unit` for unit tests located in `tests/Unit`, and `Source` for [inline tests](inline-tests.md) and benchmarks right in the source code in the `src` folder.
+In this example we defined two test suites: `Unit` for unit tests located in `tests/Unit`, and `Sources` for [inline tests](inline-tests.md) and [benchmarks](benchmarks.md) right in the project source code, in the `src` folder.
+
+To learn more about configuration, visit the [Configuration](configuration.md) section.
 
 ## Writing Your First Test
 

docs/lifecycle.md

@@ -4,7 +4,11 @@ llms_description: "#[BeforeEach], #[AfterEach], #[BeforeAll], #[AfterAll] lifecy
 
 # Lifecycle
 
-Lifecycle attributes define setup and teardown methods that run automatically at specific points during test execution.
+Lifecycle attributes let you run code before and after tests — for setting up the environment, cleaning up state, and managing resources.
+
+::: info
+This functionality is provided by the `\Testo\Lifecycle\LifecyclePlugin` plugin, included in the `SuitePlugins` default set.
+:::
 
 ## Class Instantiation
 

docs/writing-tests.md

@@ -4,25 +4,25 @@ llms_description: "Overview of test declaration approaches: methods in classes,
 
 # Writing Tests
 
-Testo doesn't care where a test lives, as long as it can be wrapped in a Closure.
+Testo doesn't care where a test lives, as long as it can be executed.
 
 ## Where to Write Tests
 
 - **In methods** — in regular classes without `TestCase` inheritance.
 - **In functions** — in standalone functions outside classes.
-- **In attributes** — directly on the method being tested. See [Inline Tests](./inline-tests).
+- **In attributes** — directly on the method being tested. See [Inline Tests](inline-tests.md).
 
 ## Test Discovery
 
-Depending on the configuration, Testo can discover tests in several ways:
+Depending on the configured [plugins](plugins.md), Testo can discover tests in several ways:
 
-- **Explicit** — the [#\[Test\] attribute](./test-attribute) marks a method, function, or class.
-- **Conventions** — [naming patterns](./naming-conventions) like `testSomething()` methods or `*Test` classes.
-- **Custom strategies** — you can implement your own test discovery, for example by function-call (like PEST, but without execution) or by class parent, like PHPUnit.
+- **Explicit** — the [#\[Test\] attribute](test-attribute.md) marks a method, function, or class.
+- **Conventions** — [naming patterns](naming-conventions.md) like `testSomething()` methods or `*Test` classes.
+- **Custom strategies** — you can implement your own test discovery, for example by function-call (like PEST) or by class parent, like PHPUnit.
 
 All approaches can be combined in one project or even in one Test Suite.
 
 ## Less Code
 
-- **Parameterization** — instead of copying a test for each data set, write one test and pass it different values via [data providers](./data-providers).
+- **Parameterization** — instead of copying a test for each data set, write one test and pass it different values via [data providers](data-providers.md).
 - **Interceptor attributes** — extract repetitive boilerplate into reusable attributes.

ru/docs/benchmarks.md

@@ -0,0 +1,5 @@
+# Бенчмарки
+
+::: info
+За эту функциональность отвечает плагин `\Testo\Bench\BenchmarkPlugin`, входящий в набор `SuitePlugins` по умолчанию.
+:::