@libredb/studio 0.9.7 → 0.9.13

package/docs/medium-koyeb-article-en.md

@@ -1,215 +0,0 @@
-# Zero-Cost SaaS: How I Deployed My Project with Koyeb.com
-
-*A side-project developer's serverless discovery journey*
-
-**Tags:** #SaaS #CloudComputing #Koyeb #Startup #WebDevelopment #FreeTier #Serverless
-
----
-
-## I Had an Idea and Was Looking for the Right Tool
-
-Every developer has that moment: the idea is ready, the code is ready, everything works perfectly on localhost. Then the question comes — "Where do I deploy this?"
-
-Sound familiar?
-
-I've been actively using platforms like AWS, Azure, GCP, DigitalOcean, Heroku, Render, Railway, and Fly.io for years, and I continue to use many of them. Each has its strengths — AWS's flexibility, Azure's enterprise integrations, DigitalOcean's simplicity, Fly.io's edge computing approach... I love these platforms and run most of my projects on them.
-
-But this time I had a different need. For a SaaS application I was building as a side project, I was looking for a **free web service and database**, **quick setup**, and a **clean interface**. Something that didn't require heavy configuration, had no complex billing model, and could go live in minutes.
-
-That's when I came across Koyeb. I created an account, connected my GitHub repo, and within minutes my project — database included — was live. And my bill? Zero.
-
-In this post, I'll share my experience with Koyeb.com, what the platform offers, and why it's a great option for side projects and MVPs.
-
----
-
-## What Is Koyeb?
-
-Koyeb is a serverless Platform-as-a-Service (PaaS) built for developers who want to run applications without dealing with infrastructure management. In the simplest terms, it offers two paths:
-
-> **Push to GitHub, let Koyeb deploy it. Or provide a Docker image, and it runs.**
-
-First path: you connect your GitHub repo, and with every push, Koyeb automatically builds and deploys. Second path: you provide a Docker image from your container registry — like `ghcr.io/user/project:latest` — and Koyeb pulls and runs it directly. No server setup, no nginx configuration, no SSL certificates to manage... None of that. Automatic build, automatic deploy, automatic HTTPS.
-
-What really surprised me was the **deployment speed**. Even on the first deploy, it was incredibly fast. You provide the image, and within seconds the service is ready. I've waited minutes for builds and provisioning on other platforms — on Koyeb, it was done in the blink of an eye.
-
-What truly sets Koyeb apart is a major development from February 2026: **its acquisition by Mistral AI**. This was the French AI giant's first-ever acquisition, and it sends a strong signal of confidence in Koyeb's future. Mistral is positioning Koyeb as a core component of its AI cloud infrastructure. This means the platform won't just survive — it will grow with serious investment behind it.
-
-Who is Koyeb for?
-
-- **Indie hackers**: Those who want to validate ideas quickly
-- **Startup founders**: Those who want to launch an MVP at zero cost
-- **Students**: Those who want to host portfolio projects
-- **Side project developers**: Those who keep saying "I'll deploy it someday"
-- **AI developers**: Those who want to run GPU-powered inference workloads
-
----
-
-## The Power of the Free Plan
-
-The first thing that drew me to Koyeb was the value of the Starter plan.
-
-Koyeb's Starter plan is **$0** and includes:
-
-- **1 web service** (512MB RAM, 0.1 vCPU, 2GB SSD)
-- **1 managed PostgreSQL database** (1GB storage)
-- **No time limit** — there's no trial period
-- **Commercial use allowed** — even if your side project generates revenue
-- **Custom domain support** — you can connect up to 5 domains
-- **100GB monthly bandwidth** — included
-
-This is more than enough for an MVP or side project. My SaaS project ran smoothly with these resources.
-
-> *I entered my credit card during registration. A small amount was charged and refunded for verification — I didn't see any charges on my statement.*
-
-### What Makes Koyeb Stand Out for Side Projects?
-
-Every platform has its strengths. AWS and Azure are indispensable for enterprise projects, DigitalOcean is great for its simplicity, Fly.io excels at edge computing, and Railway and Render have made serious strides in developer experience. I actively use most of these platforms across different projects.
-
-What made Koyeb different for me was that it **offers both a web service and a PostgreSQL database together on the free plan**, with an extremely clean interface. Instead of setting up separate services and managing accounts across different platforms for a side project, I could handle everything from one place.
-
----
-
-## 5 Features That Impressed Me
-
-The free plan is nice, but what really kept me on Koyeb was the user experience. Here are the 5 features that impressed me the most:
-
-### 1. Two Easy Deploy Paths: Git Push or Docker Image
-
-Koyeb offers two deployment paths, both extremely simple:
-
-**Path A — Git Push:**
-1. Connect your GitHub repo
-2. Select a branch, confirm build settings
-3. Deploy — every `git push` now triggers an automatic deployment
-
-**Path B — Docker Image:**
-1. Enter your container registry and image name (e.g., `ghcr.io/user/project:latest`)
-2. Set port and environment variables
-3. Deploy — Koyeb pulls the image and runs it
-
-I chose the Docker image path for my project. I provided my image from GitHub Container Registry, entered my environment variables, and hit deploy. You can also integrate with GitHub Actions or your own CI/CD pipeline, but for a simple side project, this level of simplicity is exactly right.
-
-My first deploy? It was live within **a few minutes** of providing the image. No exaggeration — the startup speed genuinely surprised me.
-
-### 2. Scale-to-Zero: Pay Only for What You Use
-
-This is, in my opinion, Koyeb's strongest feature. When your project isn't receiving traffic, the instance automatically goes to sleep. When a request comes in, it wakes up automatically. (Hugging Face Spaces and Render work similarly, but Koyeb still wins on simplicity and speed.)
-
-Koyeb does this in two tiers:
-
-- **Light Sleep**: The instance stays in memory, waking up within 200ms. Users feel no delay. (On other platforms, you really notice the cold start.)
-- **Deep Sleep**: The instance shuts down completely, waking up in 1-5 seconds. For longer idle periods.
-
-This is especially great for side projects. Why consume resources when your project isn't getting traffic at 3 AM? With Scale-to-Zero, you only pay for actual usage. On the free plan, you're already paying nothing — but when you move to paid plans, this means real savings.
-
-### 3. Managed PostgreSQL
-
-If you're building a SaaS project, you almost certainly need a database. Koyeb provides one out of the box. (This became my favorite feature. Yugabyte, Neon, Supabase, Heroku, and MongoDB Atlas all offer free tiers too — but having everything in one place is wonderful.)
-
-You get your connection string, paste it into your app, done.
-
-### 4. Clean and Modern Dashboard
-
-Koyeb's dashboard is clean, intuitive, and modern. You can view real-time logs, track deployment history, and easily manage environment variables. (You can copy-paste your .env file — no need to enter variables one by one.) Larger cloud platforms naturally have more comprehensive dashboards because they offer a much wider range of services. Koyeb, by focusing on a narrower scope, keeps its interface extremely clean. I found exactly the information I needed, right where I needed it, for managing a side project.
-
----
-
-## Koyeb's Future: The Mistral AI Effect
-
-In February 2026, Mistral AI announced its acquisition of Koyeb. This was Mistral's **first-ever acquisition**. Koyeb's 13-person team and three co-founders joined Mistral's engineering team, led by CTO Timothée Lacroix.
-
-Why does this matter?
-
-**Strategic positioning**: Mistral is moving beyond being just an LLM company to become a full-stack AI cloud provider. The Mistral Compute platform announced in June 2025 will be accelerated by Koyeb's infrastructure.
-
-**AI-focused infrastructure**: Koyeb's serverless GPU support (L4, L40S, V100) aligns perfectly with Mistral's AI inference needs. We can expect more powerful GPU options and AI-native features in the future.
-
-**European AI independence**: Mistral is part of Europe's vision to build alternatives to US tech giants. Combined with its $1.4 billion data center investment in Sweden, Koyeb's European-based infrastructure carries strategic value.
-
-**Platform continuity commitment**: Koyeb's blog post made it clear — the existing platform and free plan will continue. The acquisition means growth, not shutdown.
-
----
-
-## Pricing: Pay as You Grow
-
-Koyeb's free Starter plan offers 1 web service + 1 PostgreSQL. If your project grows, there are Pro ($29/month), Scale ($299/month), and Enterprise options — but at the side project stage, you don't need to think about any of that.
-
-What mattered to me was this: no commitment, no hidden costs. You can start without thinking "What if it doesn't take off?" — because if it doesn't, it costs you absolutely nothing.
-
----
-
-## Practical Deploy Flow
-
-I want to show how easy it is to get a project live on Koyeb. Both paths take just a few steps:
-
-### With GitHub:
-
-**Step 1** — Go to [koyeb.com](https://www.koyeb.com), sign up.
-
-**Step 2** — Select "Create Web Service" > "GitHub", connect your repo.
-
-**Step 3** — Confirm branch and build settings. Koyeb auto-detects popular frameworks like Next.js, Node.js, Python, Go, and Rust.
-
-**Step 4** — Add your environment variables, hit "Deploy".
-
-### With Docker Image:
-
-**Step 1** — Select "Create Web Service" > "Docker".
-
-**Step 2** — Enter your image address, e.g.: `ghcr.io/user/project:latest`
-
-**Step 3** — Set port, environment variables, and health check settings, hit "Deploy".
-
-With both paths, your project is live at `xxx.koyeb.app` within minutes. Want to add PostgreSQL? One click from the dashboard via "Create Database". The connection string is auto-generated. That's it.
-
----
-
-## Is Koyeb Perfect? An Honest Assessment
-
-Every platform has strengths and weaknesses. I want to be honest while praising Koyeb:
-
-**Things to keep in mind:**
-
-- **Free tier resources are limited**: 512MB RAM and 0.1 vCPU aren't enough for heavy traffic. But it's free — ideal for MVPs and prototypes.
-- **PostgreSQL uptime**: The free database goes to sleep when idle. If you need an always-on DB, you may need to upgrade to a paid plan.
-- **Region limitations (free)**: On the free plan, you can only choose Frankfurt or Washington D.C.
-- **Younger ecosystem**: It doesn't yet have as wide a service range as platforms that have been around for many years. But it's rapidly growing with Mistral's backing.
-
-**Standout strengths:**
-
-- Zero-cost start (web service + DB together)
-- Remarkably simple deploy process
-- Smart resource management with Scale-to-Zero
-- Clean and focused dashboard
-- Secure future with Mistral AI backing
-
----
-
-## Conclusion: The Right Tool for the Right Job
-
-Platforms like AWS, Azure, and GCP remain indispensable for my larger projects. But for a side project, for a quick and free start, Koyeb was exactly what I was looking for.
-
-I deployed my project at zero cost, in minutes. I didn't have to get my database from a separate service. All I needed was my code and my GitHub repo. And my bill reflected nothing.
-
-In 2026, cloud platform options are so rich that there's a solution for every need. Koyeb is a great option, especially for side projects, MVPs, and rapid prototyping. With its free web service and database bundled together, its clean interface, and easy setup, it's tailor-made for those "let me try this live" moments.
-
-If you have an idea, if you have an unfinished project, if you have code that works on localhost but has never gone live — **give it a shot**. It's free to try.
-
-And who knows, maybe the next big SaaS story will be yours.
-
----
-
-*This post is not sponsored. There are no discount codes or referral links. I used Koyeb for my own project and wanted to share my experience. As someone who loves open source: a thank you to Koyeb, and a roadmap for you.*
-
----
-
-## Resources
-
-- [Koyeb Official Site](https://www.koyeb.com/)
-- [Koyeb Pricing](https://www.koyeb.com/pricing)
-- [Koyeb Docs](https://www.koyeb.com/docs)
-- [Koyeb Scale-to-Zero](https://www.koyeb.com/docs/run-and-scale/scale-to-zero)
-- [Mistral AI + Koyeb (TechCrunch)](https://techcrunch.com/2026/02/17/mistral-ai-buys-koyeb-in-first-acquisition-to-back-its-cloud-ambitions/)
-- [Koyeb Blog: Joining Mistral AI](https://www.koyeb.com/blog/koyeb-is-joining-mistral-ai-to-build-the-future-of-ai-infrastructure)
-- [Scale-to-Zero with Light Sleep](https://www.koyeb.com/blog/avoid-cold-starts-with-scale-to-zero-light-sleep)
-- [Koyeb Regions](https://www.koyeb.com/docs/reference/regions)

package/docs/plans/test-plans.md

@@ -1,445 +0,0 @@
-# LibreDB Studio — Kapsamlı Test Altyapısı Planı
-
-## Bağlam
-
-LibreDB Studio enterprise-grade, open-source bir SQL IDE'dir. ~146 kaynak dosya, ~36,000+ satır kod var ve test altyapısı neredeyse sıfır (tek bir `postgres.test.ts` dosyası `bun:test` kullanıyor). Yeni katılımcıların güvenle geliştirme yapabilmesi ve production-ready kaliteyi korumak için kapsamlı bir test altyapısı şart.
-
-**Yaklaşım:** Coverage-first değil, **risk-first + coverage floor** modeli. Coverage tek başına kaliteyi temsil etmez — branch coverage, critical-path zorunluluğu ve E2E akış başarı oranı birlikte kalite kapılarını oluşturur.
-
----
-
-## Kalite Kapıları (Quality Gates)
-
-### Katman Bazlı Eşikler — CI'da Enforce Edilir
-
-| Katman | Line Coverage | Branch Coverage | Zorunluluk |
-|--------|-------------|----------------|------------|
-| `src/lib/` (Unit) | ≥ %95 | ≥ %90 | PR merge blocker |
-| `src/app/api/` (API) | ≥ %90 | ≥ %85 | PR merge blocker |
-| `src/hooks/` (Hooks) | ≥ %85 | ≥ %80 | PR merge blocker |
-| `src/components/` (UI) | ≥ %80 | ≥ %70 | Warning (soft gate) |
-| **Toplam Proje** | ≥ %90 | ≥ %85 | PR merge blocker |
-
-### E2E Kalite Kapısı (Bağımsız Metrik)
-
-E2E testler `bun test --coverage` lcov çıktısına katkı **YAPMAZ** — Playwright ayrı bir süreçte tarayıcıda çalışır. E2E metrikleri ayrı takip edilir:
-
-| Metrik | Eşik | Açıklama |
-|--------|-------|----------|
-| Kritik akış başarı oranı | %100 | Login, query execution, connection management |
-| Toplam E2E pass oranı | ≥ %95 | Flaky tolerance: max %5 |
-| Flaky test retry | ≤ 2 retry | CI'da `retries: 2`, 3. denemede de başarısızsa gerçek hata |
-
-### Gelecek İyileştirmeler (Phase 2 sonrası değerlendirilecek)
-
-- **Mutation Testing**: Stryker.js entegrasyonu — testlerin gerçekten hataları yakalayıp yakalamadığını ölçer
-- **SonarCloud Quality Gate**: Coverage + duplication + complexity birleşik kontrol
-- **PR Coverage Delta**: Yeni eklenen kodun coverage'ı mevcut ortalamadan düşük olamaz
-
----
-
-## Faz 0: Altyapı Kurulumu
-
-### 0.1 — Bağımlılıkları Yükle
-
-```bash
-bun add -d @testing-library/react @testing-library/jest-dom @testing-library/user-event happy-dom @playwright/test
-```
-
-### 0.2 — `bunfig.toml` Oluştur (Yeni dosya)
-
-```toml
-[test]
-preload = ["./tests/setup.ts"]
-
-[test.coverage]
-enabled = true
-reporter = ["lcov", "text"]
-```
-
-### 0.3 — `tests/setup.ts` Oluştur (Yeni dosya)
-
-- `process.env.JWT_SECRET`, `ADMIN_PASSWORD`, `USER_PASSWORD` test değerleri
-- `globalThis.localStorage` in-memory mock (SSR ortamı için)
-- `afterEach` → `localStorage.clear()` cleanup
-
-### 0.4 — Test Fixture'ları Oluştur
-
-| Dosya | İçerik |
-|-------|--------|
-| `tests/fixtures/connections.ts` | Her DB tipi için mock `DatabaseConnection` objeleri (postgres, mysql, sqlite, mongodb, redis, oracle, mssql) |
-| `tests/fixtures/schemas.ts` | Mock `TableSchema[]` objeleri |
-| `tests/fixtures/query-results.ts` | Mock `QueryResult` objeleri |
-| `tests/fixtures/masking-configs.ts` | Mock `MaskingConfig` objeleri |
-
-### 0.5 — Test Helper'ları Oluştur
-
-| Dosya | İçerik |
-|-------|--------|
-| `tests/helpers/mock-provider.ts` | `createMockProvider()` — tüm `DatabaseProvider` metodlarını mock'layan factory |
-| `tests/helpers/mock-next.ts` | `createMockRequest()`, `createMockCookies()` — Next.js API test helper'ları |
-| `tests/helpers/mock-fetch.ts` | Global `fetch` mock helper |
-| `tests/helpers/mock-monaco.ts` | Monaco Editor'ü `<textarea>` olarak mock'la |
-| `tests/helpers/render-with-providers.tsx` | Component test wrapper (theme, toast, router provider) |
-
-### 0.6 — `package.json` Script'leri Ekle
-
-```json
-{
-  "test": "bun test",
-  "test:unit": "bun test tests/unit",
-  "test:integration": "bun test tests/integration",
-  "test:hooks": "bun test tests/hooks",
-  "test:api": "bun test tests/api",
-  "test:components": "bun test tests/components",
-  "test:e2e": "bunx playwright test",
-  "test:coverage": "bun test --coverage --coverage-reporter=lcov --coverage-dir=coverage"
-}
-```
-
-### 0.7 — `playwright.config.ts` Oluştur (Yeni dosya)
-
-- `testDir: './e2e'`, `baseURL: 'http://localhost:3000'`
-- Chromium projesi, `webServer` → `bun run build && bun start`
-- CI'da `retries: 2`, `workers: 1`
-
-### 0.8 — Mevcut Test Dosyası Taşı
-
-- `src/lib/db/providers/sql/postgres.test.ts` → `tests/integration/db/postgres-provider.test.ts`
-
-### 0.9 — `.github/workflows/ci.yml` Güncelle
-
-Mevcut `lint-and-build` job korunur. Eklenenler:
-
-**Yeni `test` job:**
-```yaml
-test:
-  name: Unit & Integration Tests
-  runs-on: ubuntu-latest
-  steps:
-    - uses: actions/checkout@v6
-    - uses: oven-sh/setup-bun@v2
-      with:
-        bun-version: latest
-    - run: bun install --frozen-lockfile
-    - run: bun test --coverage --coverage-reporter=lcov --coverage-dir=coverage
-      env:
-        JWT_SECRET: test-secret-for-ci-build-only-32ch
-        ADMIN_PASSWORD: test-admin
-        USER_PASSWORD: test-user
-    - uses: actions/upload-artifact@v4
-      with:
-        name: coverage
-        path: coverage/lcov.info
-```
-
-**Yeni `e2e` job (lint-and-build'e bağımlı):**
-```yaml
-e2e:
-  name: E2E Tests
-  needs: [lint-and-build]
-  runs-on: ubuntu-latest
-  steps:
-    - uses: actions/checkout@v6
-    - uses: oven-sh/setup-bun@v2
-    - run: bun install --frozen-lockfile
-    - run: bunx playwright install --with-deps chromium
-    - run: bunx playwright test
-      env:
-        JWT_SECRET: test-secret-for-ci-build-only-32ch
-        ADMIN_PASSWORD: test-admin
-        USER_PASSWORD: test-user
-    - uses: actions/upload-artifact@v4
-      if: always()
-      with:
-        name: playwright-report
-        path: playwright-report/
-```
-
-**`sonarcloud` job güncelleme:**
-```yaml
-sonarcloud:
-  name: SonarCloud Analysis
-  needs: [test]  # coverage artifact'ını bekle
-  runs-on: ubuntu-latest
-  steps:
-    - uses: actions/checkout@v6
-      with:
-        fetch-depth: 0
-    - uses: actions/download-artifact@v4
-      with:
-        name: coverage
-        path: coverage
-    - uses: SonarSource/sonarqube-scan-action@v6
-      env:
-        SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
-```
-
-### 0.10 — `sonar-project.properties` Güncelle
-
-```properties
-sonar.projectKey=libredb_libredb-studio
-sonar.organization=libredb
-
-sonar.projectName=libredb-studio
-sonar.projectVersion=0.6.18
-
-sonar.sources=src
-sonar.tests=tests,e2e
-sonar.test.inclusions=tests/**/*.test.ts,tests/**/*.test.tsx,e2e/**/*.spec.ts
-
-# Sadece runtime/generate edilmiş kodu hariç tut, test dosyalarını DEĞİL
-sonar.exclusions=**/node_modules/**,**/.next/**,**/build/**,**/out/**,src/components/ui/**
-
-sonar.javascript.lcov.reportPaths=coverage/lcov.info
-sonar.typescript.tsconfigPath=tsconfig.json
-sonar.sourceEncoding=UTF-8
-```
-
-**Önemli:** `tests/**` ve `e2e/**` artık `sonar.exclusions` içinde DEĞİL. Bunlar `sonar.tests` olarak tanımlanır → SonarCloud bunları test kodu olarak algılar, coverage hesaplamasından hariç tutar ama analiz eder.
-
----
-
-## Faz 1: Unit Testler — Saf Fonksiyonlar
-
-**En yüksek ROI:** Saf fonksiyonlar, sıfır mocking, en kritik iş mantığı.
-
-| # | Test Dosyası | Kaynak Dosya | ~Test | Açıklama |
-|---|---|---|---|---|
-| 1 | `tests/unit/sql/statement-splitter.test.ts` | `src/lib/sql/statement-splitter.ts` | 40 | Tek/çoklu statement, `''` string literal, `"identifiers"`, `--` ve `/* */` yorumlar, `$$dollar-quote$$`, unterminated string, boş input, `isMultiStatement()` |
-| 2 | `tests/unit/lib/connection-string-parser.test.ts` | `src/lib/connection-string-parser.ts` | 45 | `postgres://`, `mysql://`, `mongodb://`, `mongodb+srv://`, `redis://`, `oracle://`, `mssql://`, `sqlserver://`, ADO.NET `Server=`, URL encoding, özel karakter, eksik parça, `detectConnectionStringType()` |
-| 3 | `tests/unit/lib/data-masking.test.ts` | `src/lib/data-masking.ts` | 60 | 10 mask tipi, `maskByType()`, `detectSensitiveColumnsFromConfig()`, `shouldMask()` RBAC, `canToggleMasking()`, `canReveal()`, `applyMaskingToRows()`, null/undefined edge case |
-| 4 | `tests/unit/db/query-limiter.test.ts` | `src/lib/db/utils/query-limiter.ts` | 50 | `analyzeQuery()` tüm query tipleri, LIMIT/OFFSET tespiti, MySQL `LIMIT x,y`, Oracle `FETCH FIRST`, MSSQL `TOP N`, `ROWNUM`, UNION, CTE, subquery, `applyQueryLimit()`, `forceLimit` |
-| 5 | `tests/unit/db/errors.test.ts` | `src/lib/db/errors.ts` | 35 | 6 error class, `toJSON()`, 5 type guard, `isRetryableError()`, `mapDatabaseError()` pattern matching, Oracle ORA-*, MSSQL pattern |
-| 6 | `tests/unit/sql/alias-extractor.test.ts` | `src/lib/sql/alias-extractor.ts` | 30 | FROM/JOIN alias, CTE, schema.table, `resolveAlias()`, `getAliasSchema()`, comment/string içindeki SQL |
-| 7 | `tests/unit/schema-diff/diff-engine.test.ts` | `src/lib/schema-diff/diff-engine.ts` | 25 | Eklenen/silinen/değiştirilen tablo ve kolon, index diff, FK diff, aynı schema, boş schema |
-| 8 | `tests/unit/schema-diff/migration-generator.test.ts` | `src/lib/schema-diff/migration-generator.ts` | 20 | CREATE/DROP/ALTER TABLE her dialect (PG, MySQL, SQLite, Oracle, MSSQL), identifier escaping |
-| 9 | `tests/unit/lib/query-generators.test.ts` | `src/lib/query-generators.ts` | 12 | `generateTableQuery()` SQL/JSON/Oracle/MSSQL, `generateSelectQuery()`, `shouldRefreshSchema()` DDL pattern |
-| 10 | `tests/unit/lib/storage.test.ts` | `src/lib/storage.ts` | 20 | CRUD: connections, history (max limit), saved queries, schema snapshots (max 50), charts, active connection ID, bozuk JSON handling |
-| 11 | `tests/unit/lib/time-series-buffer.test.ts` | `src/lib/time-series-buffer.ts` | 15 | push, getAll, getRange, getLast, clear, circular overflow, size |
-| 12 | `tests/unit/lib/audit.test.ts` | `src/lib/audit.ts` | 15 | RingBuffer push/getAll/getRecent/filter/clear/size/toJSON/loadFrom, max size |
-| 13 | `tests/unit/lib/monitoring-thresholds.test.ts` | `src/lib/monitoring-thresholds.ts` | 12 | `evaluateThreshold()` above/below, healthy/warning/critical, `getThresholdColor()`, `getThresholdBadgeVariant()` |
-| 14 | `tests/unit/db/pool-manager.test.ts` | `src/lib/db/utils/pool-manager.ts` | 20 | `mergePoolConfig()`, `validatePoolConfig()`, `withTimeout()`, `formatBytes()`, `formatDuration()`, `escapeIdentifier()` per dialect |
-| 15 | `tests/unit/llm/config.test.ts` | `src/lib/llm/utils/config.ts` | 20 | `resolveConfig()`, `validateConfig()` her provider, `requiresApiKey()`, `requiresApiUrl()`, `getSafeConfigForLogging()` |
-| 16 | `tests/unit/llm/retry.test.ts` | `src/lib/llm/utils/retry.ts` | 10 | `withRetry()` ilk seferde başarı, retry+başarı, tüm retry tükenme, non-retryable error |
-| 17 | `tests/unit/llm/streaming.test.ts` | `src/lib/llm/utils/streaming.ts` | 10 | `encodeText()`/`decodeText()`, `createSSEParser()`, `[DONE]`, malformed JSON, `createErrorStream()` |
-
-**Faz 1 Toplam:** 17 test dosyası, ~409 test case
-**Beklenen line coverage (bun test):** ~%30
-
----
-
-## Faz 2: API Route Testleri
-
-Route handler fonksiyonları doğrudan import edilip mock `NextRequest` ile çağrılır.
-
-**Mock Stratejisi:**
-- `mock.module('@/lib/db')` → `getOrCreateProvider()` mock provider döndürür
-- `mock.module('@/lib/auth')` → `getSession()` kontrol edilir (admin/user/null)
-- Her HTTP metod, başarı/hata path'i, validasyon, status code test edilir
-
-| # | Test Dosyası | Kaynak Dosya | ~Test |
-|---|---|---|---|
-| 1 | `tests/api/auth/login.test.ts` | `src/app/api/auth/login/route.ts` | 8 |
-| 2 | `tests/api/auth/me.test.ts` | `src/app/api/auth/me/route.ts` | 4 |
-| 3 | `tests/api/auth/logout.test.ts` | `src/app/api/auth/logout/route.ts` | 3 |
-| 4 | `tests/api/db/query.test.ts` | `src/app/api/db/query/route.ts` | 12 |
-| 5 | `tests/api/db/multi-query.test.ts` | `src/app/api/db/multi-query/route.ts` | 10 |
-| 6 | `tests/api/db/schema.test.ts` | `src/app/api/db/schema/route.ts` | 6 |
-| 7 | `tests/api/db/health.test.ts` | `src/app/api/db/health/route.ts` | 6 |
-| 8 | `tests/api/db/test-connection.test.ts` | `src/app/api/db/test-connection/route.ts` | 8 |
-| 9 | `tests/api/db/transaction.test.ts` | `src/app/api/db/transaction/route.ts` | 12 |
-| 10 | `tests/api/db/cancel.test.ts` | `src/app/api/db/cancel/route.ts` | 6 |
-| 11 | `tests/api/db/maintenance.test.ts` | `src/app/api/db/maintenance/route.ts` | 8 |
-| 12 | `tests/api/db/monitoring.test.ts` | `src/app/api/db/monitoring/route.ts` | 6 |
-| 13 | `tests/api/db/provider-meta.test.ts` | `src/app/api/db/provider-meta/route.ts` | 6 |
-| 14 | `tests/api/db/pool-stats.test.ts` | `src/app/api/db/pool-stats/route.ts` | 4 |
-| 15 | `tests/api/db/profile.test.ts` | `src/app/api/db/profile/route.ts` | 8 |
-| 16 | `tests/api/db/schema-snapshot.test.ts` | `src/app/api/db/schema-snapshot/route.ts` | 6 |
-| 17 | `tests/api/ai/chat.test.ts` | `src/app/api/ai/chat/route.ts` | 10 |
-| 18 | `tests/api/ai/nl2sql.test.ts` | `src/app/api/ai/nl2sql/route.ts` | 8 |
-| 19 | `tests/api/ai/explain.test.ts` | `src/app/api/ai/explain/route.ts` | 8 |
-| 20 | `tests/api/ai/query-safety.test.ts` | `src/app/api/ai/query-safety/route.ts` | 8 |
-| 21 | `tests/api/ai/autopilot.test.ts` | `src/app/api/ai/autopilot/route.ts` | 6 |
-| 22 | `tests/api/ai/index-advisor.test.ts` | `src/app/api/ai/index-advisor/route.ts` | 6 |
-| 23 | `tests/api/ai/impact.test.ts` | `src/app/api/ai/impact/route.ts` | 6 |
-| 24 | `tests/api/ai/describe-schema.test.ts` | `src/app/api/ai/describe-schema/route.ts` | 4 |
-| 25 | `tests/api/admin/fleet-health.test.ts` | `src/app/api/admin/fleet-health/route.ts` | 6 |
-| 26 | `tests/api/admin/audit.test.ts` | `src/app/api/admin/audit/route.ts` | 6 |
-| 28 | `tests/api/middleware.test.ts` | `src/middleware.ts` | 15 |
-
-**Faz 2 Toplam:** 28 test dosyası, ~207 test case
-**Beklenen kümülatif line coverage (bun test):** ~%55
-
----
-
-## Faz 3: Provider Integration Testleri
-
-Her provider'ın native DB client'ı `mock.module()` ile mock'lanır. Mevcut `postgres.test.ts` pattern'i takip edilir.
-
-**Test edilen metodlar:** `connect()`, `disconnect()`, `query()`, `getSchema()`, `getHealth()`, `runMaintenance()`, `prepareQuery()`, `getCapabilities()`, `getLabels()`, error mapping.
-
-| # | Test Dosyası | Kaynak Dosya | Mock Target | ~Test |
-|---|---|---|---|---|
-| 2 | `tests/integration/db/postgres-provider.test.ts` | `src/lib/db/providers/sql/postgres.ts` | `pg` → mock Pool | 20 |
-| 3 | `tests/integration/db/mysql-provider.test.ts` | `src/lib/db/providers/sql/mysql.ts` | `mysql2/promise` | 18 |
-| 4 | `tests/integration/db/sqlite-provider.test.ts` | `src/lib/db/providers/sql/sqlite.ts` | `better-sqlite3` | 15 |
-| 5 | `tests/integration/db/mongodb-provider.test.ts` | `src/lib/db/providers/document/mongodb.ts` | `mongodb` → mock MongoClient | 18 |
-| 6 | `tests/integration/db/redis-provider.test.ts` | `src/lib/db/providers/keyvalue/redis.ts` | `ioredis` | 15 |
-| 7 | `tests/integration/db/oracle-provider.test.ts` | `src/lib/db/providers/sql/oracle.ts` | `oracledb` | 18 |
-| 8 | `tests/integration/db/mssql-provider.test.ts` | `src/lib/db/providers/sql/mssql.ts` | `mssql` | 18 |
-| 9 | `tests/unit/db/factory.test.ts` | `src/lib/db/factory.ts` | Dynamic imports + SSH tunnel | 15 |
-| 10 | `tests/unit/db/base-provider.test.ts` | `src/lib/db/base-provider.ts` | Concrete mock impl | 12 |
-
-**Faz 3 Toplam:** 10 test dosyası, ~164 test case
-**Beklenen kümülatif line coverage (bun test):** ~%70
-
----
-
-## Faz 4: React Hook Testleri
-
-`@testing-library/react` `renderHook` + `act` kullanılır. `globalThis.fetch` mock'lanır.
-
-| # | Test Dosyası | Kaynak Dosya | ~Test |
-|---|---|---|---|
-| 1 | `tests/hooks/use-auth.test.ts` | `src/hooks/use-auth.ts` | 8 |
-| 2 | `tests/hooks/use-connection-manager.test.ts` | `src/hooks/use-connection-manager.ts` | 15 |
-| 3 | `tests/hooks/use-tab-manager.test.ts` | `src/hooks/use-tab-manager.ts` | 12 |
-| 4 | `tests/hooks/use-query-execution.test.ts` | `src/hooks/use-query-execution.ts` | 20 |
-| 5 | `tests/hooks/use-transaction-control.test.ts` | `src/hooks/use-transaction-control.ts` | 8 |
-| 6 | `tests/hooks/use-inline-editing.test.ts` | `src/hooks/use-inline-editing.ts` | 10 |
-| 7 | `tests/hooks/use-connection-form.test.ts` | `src/hooks/use-connection-form.ts` | 15 |
-| 8 | `tests/hooks/use-provider-metadata.test.ts` | `src/hooks/use-provider-metadata.ts` | 8 |
-| 9 | `tests/hooks/use-monitoring-data.test.ts` | `src/hooks/use-monitoring-data.ts` | 12 |
-| 10 | `tests/hooks/use-ai-chat.test.ts` | `src/hooks/use-ai-chat.ts` | 10 |
-| 11 | `tests/hooks/use-mobile.test.ts` | `src/hooks/use-mobile.ts` | 4 |
-| 12 | `tests/hooks/use-toast.test.ts` | `src/hooks/use-toast.ts` | 4 |
-
-**Faz 4 Toplam:** 12 test dosyası, ~126 test case
-**Beklenen kümülatif line coverage (bun test):** ~%80
-
----
-
-## Faz 5: Component Testleri
-
-`happy-dom` ortamı, `@testing-library/react`, heavy dependency mock'ları.
-
-**Mock Stratejisi:**
-- `@monaco-editor/react` → `<textarea data-testid="mock-monaco-editor">`
-- `recharts` → basit `<div>` wrapper'ları
-- `@xyflow/react` → `<div>` wrapper
-- `framer-motion` → children pass-through (animasyonsuz)
-
-| # | Test Dosyası | Kaynak Dosya | ~Test |
-|---|---|---|---|
-| 1 | `tests/components/ConnectionModal.test.tsx` | `src/components/ConnectionModal.tsx` | 15 |
-| 2 | `tests/components/ResultsGrid.test.tsx` | `src/components/ResultsGrid.tsx` | 12 |
-| 3 | `tests/components/Studio.test.tsx` | `src/components/Studio.tsx` | 10 |
-| 4 | `tests/components/CommandPalette.test.tsx` | `src/components/CommandPalette.tsx` | 8 |
-| 5 | `tests/components/QueryEditor.test.tsx` | `src/components/QueryEditor.tsx` | 8 |
-| 6 | `tests/components/sidebar/Sidebar.test.tsx` | `src/components/sidebar/Sidebar.tsx` | 8 |
-| 7 | `tests/components/sidebar/ConnectionItem.test.tsx` | `src/components/sidebar/ConnectionItem.tsx` | 6 |
-| 8 | `tests/components/sidebar/ConnectionsList.test.tsx` | `src/components/sidebar/ConnectionsList.tsx` | 6 |
-| 9 | `tests/components/QueryHistory.test.tsx` | `src/components/QueryHistory.tsx` | 8 |
-| 10 | `tests/components/DataCharts.test.tsx` | `src/components/DataCharts.tsx` | 10 |
-| 11 | `tests/components/SchemaDiagram.test.tsx` | `src/components/SchemaDiagram.tsx` | 8 |
-| 12 | `tests/components/SchemaDiff.test.tsx` | `src/components/SchemaDiff.tsx` | 8 |
-| 13 | `tests/components/MaskingSettings.test.tsx` | `src/components/MaskingSettings.tsx` | 8 |
-| 14 | `tests/components/DataProfiler.test.tsx` | `src/components/DataProfiler.tsx` | 6 |
-| 15 | `tests/components/schema-explorer/SchemaExplorer.test.tsx` | `src/components/schema-explorer/SchemaExplorer.tsx` | 6 |
-| 16 | `tests/components/admin/AdminDashboard.test.tsx` | `src/components/admin/AdminDashboard.tsx` | 8 |
-| 17 | `tests/components/admin/OverviewTab.test.tsx` | `src/components/admin/tabs/OverviewTab.tsx` | 8 |
-| 18 | `tests/components/admin/OperationsTab.test.tsx` | `src/components/admin/tabs/OperationsTab.tsx` | 6 |
-| 19 | `tests/components/admin/SecurityTab.test.tsx` | `src/components/admin/tabs/SecurityTab.tsx` | 6 |
-| 20 | `tests/components/admin/AuditTab.test.tsx` | `src/components/admin/tabs/AuditTab.tsx` | 6 |
-| 21 | `tests/components/monitoring/MonitoringDashboard.test.tsx` | `src/components/monitoring/MonitoringDashboard.tsx` | 8 |
-| 22 | `tests/components/studio/BottomPanel.test.tsx` | `src/components/studio/BottomPanel.tsx` | 6 |
-| 23 | `tests/components/studio/QueryToolbar.test.tsx` | `src/components/studio/QueryToolbar.tsx` | 6 |
-| 24 | `tests/components/studio/StudioTabBar.test.tsx` | `src/components/studio/StudioTabBar.tsx` | 6 |
-
-**Faz 5 Toplam:** 24 test dosyası, ~187 test case
-**Beklenen kümülatif line coverage (bun test):** ~%90-92
-
----
-
-## Faz 6: E2E Testler (Playwright)
-
-Tam tarayıcı testleri, çalışan Next.js server'a karşı. **Bu testler `bun test --coverage` lcov'a katkı YAPMAZ** — bağımsız kalite kapısı olarak izlenir.
-
-| # | Test Dosyası | Senaryo | Kritiklik |
-|---|---|---|---|
-| 1 | `e2e/login.spec.ts` | Admin/user login, yanlış şifre, redirect, logout | Kritik |
-| 3 | `e2e/connection-management.spec.ts` | Connection ekle/düzenle/sil, test connection | Kritik |
-| 4 | `e2e/query-execution.spec.ts` | Query yaz, çalıştır, sonuç gör, cancel | Kritik |
-| 5 | `e2e/tab-management.spec.ts` | Tab ekle/kapat/yeniden adlandır/değiştir | Normal |
-| 6 | `e2e/export.spec.ts` | CSV/JSON/SQL export | Normal |
-| 7 | `e2e/admin-dashboard.spec.ts` | Admin erişim, tab'lar, fleet health | Normal |
-
-**Faz 6 Toplam:** 7 test dosyası, ~40 test case
-**E2E kritik akış başarı oranı hedefi:** %100
-
----
-
-## Toplam Özet
-
-| Faz | Kapsam | Dosya | Test Case | Bun Coverage (lcov) |
-|-----|--------|-------|-----------|---------------------|
-| 0 | Altyapı + CI/CD | 12 (setup) | 0 | — |
-| 1 | Saf Fonksiyonlar | 17 | ~409 | ~%30 |
-| 2 | API Routes | 28 | ~207 | ~%55 |
-| 3 | DB Providers | 10 | ~164 | ~%70 |
-| 4 | React Hooks | 12 | ~126 | ~%80 |
-| 5 | Components | 24 | ~187 | ~%90-92 |
-| 6 | E2E (ayrı metrik) | 7 | ~40 | N/A |
-| **Toplam** | | **110** | **~1,133** | **≥%90 line + ≥%85 branch** |
-
-Faz 5 sonrası lcov raporundan kalan uncovered branch'ler tespit edilip ek edge-case testleri yazılarak %95+ hedefine ulaşılır.
-
----
-
-## Framework Seçim Gerekçesi
-
-| Katman | Araç | Neden |
-|--------|------|-------|
-| Unit/Integration | `bun:test` | Mevcut pattern, sıfır ek bağımlılık, native TS, Jest-uyumlu API, lcov desteği |
-| Component/Hook | `@testing-library/react` + `happy-dom` | React standartı, `renderHook`, Bun ESM uyumlu, jsdom'dan hızlı |
-| E2E | `@playwright/test` | Multi-browser, Next.js App Router desteği, HTML reporter, retries |
-| Coverage | `bun test --coverage` | Built-in lcov reporter → SonarCloud entegrasyonu |
-
----
-
-## Doğrulama Planı
-
-Her faz sonunda:
-1. `bun test` — tüm testler geçmeli (exit code 0)
-2. `bun test --coverage` — line ve branch coverage eşikler kontrol edilmeli
-3. `bun run lint` — test dosyaları lint'ten geçmeli
-4. `bun run typecheck` — type hatası olmamalı
-5. Faz 6 için: `bunx playwright test` — kritik akışlar %100 pass
-6. CI pipeline'da tüm job'lar başarılı olmalı
-
----
-
-## Değiştirilecek Mevcut Dosyalar
-
-| Dosya | Değişiklik |
-|-------|-----------|
-| `package.json` | Test script'leri eklenir |
-| `.github/workflows/ci.yml` | `test`, `e2e` job eklenir, `sonarcloud` güncellenir |
-| `sonar-project.properties` | `sonar.tests`, `sonar.test.inclusions`, `sonar.exclusions` düzenlenir |
-
-## Oluşturulacak Yeni Dosyalar
-
-| Dosya | Amaç |
-|-------|------|
-| `bunfig.toml` | Bun test runner config |
-| `playwright.config.ts` | Playwright E2E config |
-| `tests/setup.ts` | Global test setup |
-| `tests/fixtures/*.ts` (4 dosya) | Mock veri objeleri |
-| `tests/helpers/*.ts` (5 dosya) | Test utility'leri |
-| `tests/unit/**/*.test.ts` (17 dosya) | Unit testler |
-| `tests/api/**/*.test.ts` (28 dosya) | API route testleri |
-| `tests/integration/**/*.test.ts` (8 dosya) | Provider testleri |
-| `tests/hooks/**/*.test.ts` (12 dosya) | Hook testleri |
-| `tests/components/**/*.test.tsx` (24 dosya) | Component testleri |
-| `e2e/**/*.spec.ts` (7 dosya) | E2E testler |