Remove namespaces from samples

Author: roxblnfk

docs/data-providers.md

@@ -7,9 +7,6 @@ Data providers let you run one test with different sets of input data. Each set
 The simplest way — specify data directly above the method:
 
 ```php
-use Testo\Attribute\Test;
-use Testo\Attribute\DataSet;
-
 #[Test]
 #[DataSet([1, 1, 2])]
 #[DataSet([2, 3, 5])]
@@ -38,9 +35,6 @@ public function testSum(int $a, int $b, int $expected): void { ... }
 For large amounts of data or dynamic generation, use `DataProvider`. It accepts a method or callable that returns test data:
 
 ```php
-use Testo\Attribute\Test;
-use Testo\Sample\DataProvider;
-
 #[Test]
 #[DataProvider('userDataProvider')]
 public function testUserValidation(string $email, bool $expected): void

docs/events.md

@@ -17,9 +17,6 @@ Event characteristics:
 Register listeners via `EventListenerCollector` interface in your plugins. See [plugins](./plugins.md) for plugin development.
 
 ```php
-use Testo\Config\EventListenerCollector;
-use Testo\Test\Event\Test\TestFinished;
-
 class MyPlugin
 {
     public function configure(EventListenerCollector $events): void
@@ -133,8 +130,6 @@ Since events are classes, you can listen to parent classes or interfaces to hand
 ### Listen to All Test Events
 
 ```php
-use Testo\Test\Event\Test\TestEvent;
-
 $events->addListener(TestEvent::class, function (TestEvent $event) {
     // Fires for: TestStarting, TestFinished, TestRetrying, TestBatchStarting, etc.
     $this->logger->debug("Test event: " . get_class($event));
@@ -144,8 +139,6 @@ $events->addListener(TestEvent::class, function (TestEvent $event) {
 ### Listen to All Events with Results
 
 ```php
-use Testo\Test\Event\Test\TestResultEvent;
-
 $events->addListener(TestResultEvent::class, function (TestResultEvent $event) {
     // Fires for: TestFinished, TestBatchFinished, TestPipelineFinished
     if ($event->testResult->isFailed()) {
@@ -157,8 +150,6 @@ $events->addListener(TestResultEvent::class, function (TestResultEvent $event) {
 ### Listen to All Test Case Events
 
 ```php
-use Testo\Test\Event\TestCase\TestCaseEvent;
-
 $events->addListener(TestCaseEvent::class, function (TestCaseEvent $event) {
     // Fires for all TestCase* events (test case level)
     $this->trackCase($event->caseInfo);

docs/filtering.md

@@ -11,8 +11,6 @@ Testo provides a flexible filtering system that operates in multiple stages to p
 The `Testo\Common\Filter` class is an immutable DTO containing test filtering criteria:
 
 ```php
-use Testo\Common\Filter;
-
 $filter = new Filter(
     suites: ['Unit', 'Integration'],
     names: ['UserTest::testLogin', 'testAuthentication'],
@@ -47,9 +45,6 @@ $filter = new Filter(
 The `Filter` object can be passed to `Application::run()`:
 
 ```php
-use Testo\Application;
-use Testo\Common\Filter;
-
 $app = Application::createFromInput(/* ... */);
 
 $filter = new Filter(

docs/getting-started.md

@@ -27,9 +27,9 @@ To customize the configuration, create a `testo.php` file in the root of your pr
 
 declare(strict_types=1);
 
-use Testo\Config\ApplicationConfig;
-use Testo\Config\SuiteConfig;
-use Testo\Config\FinderConfig;
+use Testo\Application\Config\ApplicationConfig;
+use Testo\Application\Config\SuiteConfig;
+use Testo\Application\Config\FinderConfig;
 
 return new ApplicationConfig(
     suites: [
@@ -55,9 +55,9 @@ declare(strict_types=1);
 namespace Tests;
 
 use Testo\Assert;
-use Testo\Attribute\Test;
-use Testo\Attribute\RetryPolicy;
-use Testo\Attribute\ExpectException;
+use Testo\Assert\ExpectException;
+use Testo\Application\Attribute\Test;
+use Testo\Retry\RetryPolicy;
 
 final class CalculatorTest
 {

docs/inline-tests.md

@@ -3,8 +3,6 @@
 Inline tests let you write test cases directly on the method being tested using the `#[TestInline]` attribute. No separate test class needed.
 
 ```php
-use Testo\Sample\TestInline;
-
 #[TestInline([1, 1], 2)]
 #[TestInline([40, 2], 42)]
 #[TestInline([-5, 5], 0)]
@@ -80,8 +78,6 @@ private function calculateFinalPrice(
 For complex checks, pass a closure as the second parameter:
 
 ```php
-use Testo\Assert;
-
 #[TestInline([10, 3], fn($r) => Assert::greaterThan(3, $r))]
 public function divide(int $a, int $b): float
 {
@@ -109,8 +105,6 @@ public function createUser(string $email): User
 In PHP 8.6 this becomes even more elegant with [partial application](https://wiki.php.net/rfc/partial_function_application_v2):
 
 ```php
-use Testo\Assert;
-
 #[TestInline([10, 3], Assert::greaterThan(3, ?))]
 public function divide(int $a, int $b): float
 {

docs/lifecycle.md

@@ -67,12 +67,6 @@ AfterAll (once)
 ## Basic Example
 
 ```php
-use Testo\Attribute\Test;
-use Testo\Attribute\BeforeEach;
-use Testo\Attribute\AfterEach;
-use Testo\Attribute\BeforeAll;
-use Testo\Attribute\AfterAll;
-
 final class DatabaseTest
 {
     private static Connection $connection;

ru/docs/data-providers.md

@@ -7,9 +7,6 @@
 Самый простой способ — указать данные прямо над методом:
 
 ```php
-use Testo\Attribute\Test;
-use Testo\Attribute\DataSet;
-
 #[Test]
 #[DataSet([1, 1, 2])]
 #[DataSet([2, 3, 5])]
@@ -38,9 +35,6 @@ public function testSum(int $a, int $b, int $expected): void { ... }
 Для большого количества данных или динамической генерации используйте `DataProvider`. Он принимает метод или вызываемый объект, который возвращает тестовые данные:
 
 ```php
-use Testo\Attribute\Test;
-use Testo\Sample\DataProvider;
-
 #[Test]
 #[DataProvider('userDataProvider')]
 public function testUserValidation(string $email, bool $expected): void

ru/docs/events.md

@@ -17,9 +17,6 @@ Testo генерирует события на протяжении всего 
 Регистрируйте слушателей через интерфейс `EventListenerCollector` в ваших плагинах. См. [плагины](./plugins.md) для разработки плагинов.
 
 ```php
-use Testo\Config\EventListenerCollector;
-use Testo\Test\Event\Test\TestFinished;
-
 class MyPlugin
 {
     public function configure(EventListenerCollector $events): void
@@ -133,8 +130,6 @@ TestPipelineFinished           # После перехватчиков тест
 ### Слушать все события теста
 
 ```php
-use Testo\Test\Event\Test\TestEvent;
-
 $events->addListener(TestEvent::class, function (TestEvent $event) {
     // Срабатывает для: TestStarting, TestFinished, TestRetrying, TestBatchStarting, и т.д.
     $this->logger->debug("Test event: " . get_class($event));
@@ -144,8 +139,6 @@ $events->addListener(TestEvent::class, function (TestEvent $event) {
 ### Слушать все события с результатами
 
 ```php
-use Testo\Test\Event\Test\TestResultEvent;
-
 $events->addListener(TestResultEvent::class, function (TestResultEvent $event) {
     // Срабатывает для: TestFinished, TestBatchFinished, TestPipelineFinished
     if ($event->testResult->isFailed()) {
@@ -157,8 +150,6 @@ $events->addListener(TestResultEvent::class, function (TestResultEvent $event) {
 ### Слушать все события Test Case
 
 ```php
-use Testo\Test\Event\TestCase\TestCaseEvent;
-
 $events->addListener(TestCaseEvent::class, function (TestCaseEvent $event) {
     // Срабатывает для всех событий TestCase* (уровень Test Case)
     $this->trackCase($event->caseInfo);

ru/docs/filtering.md

@@ -11,8 +11,6 @@ Testo предоставляет гибкую систему фильтраци
 Класс `Testo\Common\Filter` представляет собой неизменяемый DTO, содержащий критерии фильтрации тестов:
 
 ```php
-use Testo\Common\Filter;
-
 $filter = new Filter(
     suites: ['Unit', 'Integration'],
     names: ['UserTest::testLogin', 'testAuthentication'],
@@ -47,9 +45,6 @@ $filter = new Filter(
 Объект `Filter` может быть передан в `Application::run()`:
 
 ```php
-use Testo\Application;
-use Testo\Common\Filter;
-
 $app = Application::createFromInput(/* ... */);
 
 $filter = new Filter(

ru/docs/getting-started.md

@@ -26,9 +26,9 @@ composer require --dev testo/testo
 
 declare(strict_types=1);
 
-use Testo\Config\ApplicationConfig;
-use Testo\Config\SuiteConfig;
-use Testo\Config\FinderConfig;
+use Testo\Application\Config\ApplicationConfig;
+use Testo\Application\Config\SuiteConfig;
+use Testo\Application\Config\FinderConfig;
 
 return new ApplicationConfig(
     suites: [
@@ -54,9 +54,9 @@ declare(strict_types=1);
 namespace Tests;
 
 use Testo\Assert;
-use Testo\Attribute\Test;
-use Testo\Attribute\RetryPolicy;
-use Testo\Attribute\ExpectException;
+use Testo\Assert\ExpectException;
+use Testo\Application\Attribute\Test;
+use Testo\Retry\RetryPolicy;
 
 final class CalculatorTest
 {