@restforgejs/platform 4.1.1 → 4.3.1

package/generators/tests/integration-tahap4b/README.md

@@ -1,145 +0,0 @@
-# Tahap 4b — Integration Test Concurrent UPDATE Strict (Postgres)
-
-Verifikasi runtime path `_updateDataStrict()` di `base-model.js` (PostgreSQL) di bawah beban concurrent: 100 parallel UPDATE pada satu record harus menghasilkan 100 entry audit log dan tidak ada lost update.
-
-## Prasyarat
-
-| Komponen | Status yang Dibutuhkan |
-|----------|------------------------|
-| PostgreSQL | Running di 127.0.0.1:5432, database `dbinv`, user `postgres`, password `postgres1234` |
-| Redis | Running di localhost:6380 (untuk lockManager — opsional, fallback aman jika down) |
-| restforge runtime | Sudah di-build dan di-install di [restforge-test-pro](../../../../../deployment/restforge-test-pro/) |
-| Module `karyawan-fp` | Sudah di-generate ke restforge-test-pro (lihat setup di bawah) |
-
-## Setup (sudah dijalankan saat eksekusi Tahap 4b oleh assistant)
-
-```bash
-# 1. Build runtime restforge dengan modifikasi base-model.js (Tahap 2)
-cd d:/workspace/03_projects/data-connector/source/restforge
-echo y | node build-npm.js --nobump --edition=pro \
-  --target="D:\workspace\03_projects\data-connector\deployment\restforge-test-pro"
-
-# 2. Reinstall package di restforge-test-pro
-cd d:/workspace/03_projects/data-connector/deployment/restforge-test-pro
-rm -rf node_modules
-npm install restforgejs-2.3.0-beta.9.tgz
-
-# 3. Generate module karyawan-fp
-node d:/workspace/03_projects/data-connector/source/restforge-cli/cli/create-module.js \
-  --project=mini-inventory --endpoint=karyawan-fp --payload=karyawan_fp \
-  --database=postgres --force=true --create-demo=false --no-audit-migration=true
-```
-
-## Workflow Eksekusi Test
-
-### Langkah 1 — Seed database
-
-Reset state tabel `hr_karyawan` dan `hr_karyawan_audit`:
-
-```bash
-psql -h 127.0.0.1 -U postgres -d dbinv -f seed.sql
-```
-
-Output yang diharapkan:
-- Tabel `hr_karyawan` dan `hr_karyawan_audit` di-create
-- 1 record dengan `karyawan_id='test-001'`, `salary=5000000` ter-insert
-- `audit_initial_count = 0`
-
-### Langkah 2 — Start server
-
-Buka terminal baru:
-
-```bash
-cd d:/workspace/03_projects/data-connector/deployment/restforge-test-pro
-server-start.bat
-```
-
-Tunggu sampai log menampilkan `Server started on port 3032` (atau serupa).
-
-### Langkah 3 — Run concurrent test
-
-Di terminal lain:
-
-```bash
-cd d:/workspace/03_projects/data-connector/source/restforge-cli/tests/integration-tahap4b
-node run-concurrent.js
-```
-
-Output yang diharapkan:
-```
-[run-concurrent] Endpoint: http://127.0.0.1:3032/api/mini-inventory/karyawan-fp/update
-[run-concurrent] Firing 100 parallel UPDATE requests...
-
-=== Summary ===
-Elapsed:  XXXX ms
-Success:  100/100
-Failed:   0/100
-```
-
-Variasi parameter:
-- `TOTAL=50 node run-concurrent.js` → 50 parallel
-- `RESTFORGE_URL=http://localhost:3032 node run-concurrent.js` → custom URL
-
-### Langkah 4 — Verify hasil
-
-```bash
-psql -h 127.0.0.1 -U postgres -d dbinv -f verify.sql
-```
-
-Output yang diharapkan (semua section menampilkan verdict `OK`):
-
-| Section | Expected |
-|---------|----------|
-| 1. FINAL STATE | `final_salary` antara 5000001-5000100, verdict `OK` |
-| 2. AUDIT ENTRY COUNT | `audit_entry_count = 100`, verdict `OK (100/100)` |
-| 3. AUDIT JSON STRUCTURE | `missing_salary_audit = 0`, verdict `OK` |
-| 4. AUDIT SAMPLE | 5 entry dengan `changed_fields->'salary'` JSON valid `{"old":"...","new":"..."}` |
-| 5. DISTINCT NEW VALUES | `distinct_new_values = 100`, verdict `OK` |
-| 6. FINAL VALUE TRACEABILITY | `final_value_in_audit = true`, verdict `OK` |
-
-### Langkah 5 — Stop server
-
-Di terminal yang menjalankan server: tekan `Ctrl+C`.
-
-## Interpretasi Hasil
-
-**Semua verdict OK** → path strict bekerja dengan benar:
-- `SELECT FOR UPDATE` mencegah lost update
-- Audit table tercatat untuk setiap request
-- Atomicity dijamin via transaction wrapping
-
-**Failures yang mungkin terjadi**:
-
-| Verdict | Kemungkinan Penyebab |
-|---------|---------------------|
-| Section 2 verdict FAIL atau PARTIAL | Strict path tidak ter-trigger (cek log server untuk SELECT FOR UPDATE) — atau audit table mismatched |
-| Section 3 missing_salary_audit > 0 | Bug di `_buildChangedFieldsJSON()` — field salary tidak masuk JSON |
-| Section 6 final_value_in_audit = false | Lost update terjadi — strict path tidak proteksi dengan benar |
-| Section 1 salary out of range | Test config issue, bukan strict path bug |
-
-## Cleanup
-
-```sql
--- Optional: drop test tables
-DROP TABLE IF EXISTS hr_karyawan_audit;
-DROP TABLE IF EXISTS hr_karyawan;
-
--- Optional: drop generated module dari project
--- (tidak otomatis — drop manual via restforge-cli drop atau hapus file)
-```
-
-## Catatan Teknis
-
-**Lock manager via Redis**: `_updateDataStrict` mencoba acquire WRITE lock via Redis. Jika Redis down, lockManager fallback ke disabled mode dan strict path tetap jalan dengan SELECT FOR UPDATE saja. Ini valid — DB-level lock cukup untuk mencegah lost update.
-
-**Strict path skip event lifecycle**: per design Tahap 2, `_updateDataStrict` TIDAK memanggil `executeTransactionWithEvents()` (skip onBefore/onAfter hooks). Test ini valid karena payload `karyawan_fp.json` tidak declare `components`.
-
-**Concurrent test mungkin lebih lambat dari relaxed path**: SELECT FOR UPDATE serialize concurrent UPDATE pada record yang sama. Total elapsed ~50-200ms untuk 100 request adalah expected.
-
-**API auth**: jika test environment require API key (X-Api-Key header), tambah ke `run-concurrent.js`:
-```js
-headers: {
-  'Content-Type': 'application/json',
-  'X-Api-Key': process.env.RESTFORGE_API_KEY || '...'
-}
-```

package/generators/tests/integration-tahap4b/run-concurrent.js

@@ -1,77 +0,0 @@
-#!/usr/bin/env node
-/**
- * Tahap 4b — Concurrent UPDATE Test
- *
- * Fire N parallel UPDATE pada hr_karyawan/test-001, setiap request set salary
- * ke nilai unique. Verifikasi:
- *   - Semua request return 200 (atau lock contention error yang acceptable)
- *   - Total elapsed time wajar (path strict harus serialize via SELECT FOR UPDATE)
- *
- * Verifikasi audit log (count = TOTAL, all entries have salary key) dilakukan
- * via verify.sql terpisah.
- *
- * Usage:
- *   node run-concurrent.js
- *   TOTAL=50 node run-concurrent.js
- *   RESTFORGE_URL=http://127.0.0.1:3032 node run-concurrent.js
- */
-
-const BASE_URL = process.env.RESTFORGE_URL || 'http://127.0.0.1:3032';
-const ENDPOINT = `${BASE_URL}/api/mini-inventory/karyawan-fp/update`;
-const TOTAL = parseInt(process.env.TOTAL || '100', 10);
-
-async function fireUpdate(i) {
-  const salary = 5000000 + i;
-  try {
-    const res = await fetch(ENDPOINT, {
-      method: 'POST',
-      headers: { 'Content-Type': 'application/json' },
-      body: JSON.stringify({ karyawan_id: 'test-001', salary })
-    });
-    let body = null;
-    try { body = await res.json(); } catch (_) {}
-    return { i, salary, status: res.status, ok: res.ok, body };
-  } catch (err) {
-    return { i, salary, status: 0, ok: false, error: err.message };
-  }
-}
-
-(async () => {
-  console.log(`[run-concurrent] Endpoint: ${ENDPOINT}`);
-  console.log(`[run-concurrent] Firing ${TOTAL} parallel UPDATE requests...`);
-
-  const t0 = Date.now();
-  const results = await Promise.all(
-    Array.from({ length: TOTAL }, (_, i) => fireUpdate(i + 1))
-  );
-  const elapsed = Date.now() - t0;
-
-  const ok = results.filter(r => r.status === 200);
-  const failed = results.filter(r => r.status !== 200);
-
-  console.log('');
-  console.log('=== Summary ===');
-  console.log(`Elapsed:  ${elapsed} ms`);
-  console.log(`Success:  ${ok.length}/${TOTAL}`);
-  console.log(`Failed:   ${failed.length}/${TOTAL}`);
-
-  if (failed.length > 0) {
-    console.log('');
-    console.log('=== First 5 failures ===');
-    failed.slice(0, 5).forEach(f => {
-      console.log(JSON.stringify({
-        i: f.i,
-        salary: f.salary,
-        status: f.status,
-        error: f.error,
-        body: f.body ? (typeof f.body === 'object' ? f.body.message || JSON.stringify(f.body).slice(0, 200) : f.body) : null
-      }));
-    });
-  }
-
-  console.log('');
-  console.log('Next: jalankan verify.sql untuk cek audit log');
-  console.log('  psql -h 127.0.0.1 -U postgres -d dbinv -f verify.sql');
-
-  process.exit(failed.length === 0 ? 0 : 1);
-})();

package/generators/tests/integration-tahap4b/seed.sql

@@ -1,53 +0,0 @@
--- ============================================================================
--- Tahap 4b — Integration Test Seed Script
--- ============================================================================
--- Membuat tabel hr_karyawan + hr_karyawan_audit dan insert 1 record uji.
--- Dijalankan SEKALI sebelum run-concurrent.js untuk reset state.
---
--- Eksekusi:
---   psql -h 127.0.0.1 -U postgres -d dbinv -f seed.sql
--- ============================================================================
-
--- 1. Drop table existing (cascade ke audit jika ada FK — saat ini tidak ada FK)
-DROP TABLE IF EXISTS hr_karyawan_audit;
-DROP TABLE IF EXISTS hr_karyawan;
-
--- 2. Create main table
-CREATE TABLE hr_karyawan (
-    karyawan_id   VARCHAR(36) PRIMARY KEY,
-    nama          VARCHAR(128) NOT NULL,
-    salary        BIGINT NOT NULL DEFAULT 0,
-    bonus         BIGINT NOT NULL DEFAULT 0,
-    is_active     VARCHAR(8) NOT NULL DEFAULT 'true',
-    created_at    TIMESTAMPTZ NOT NULL DEFAULT NOW(),
-    created_by    VARCHAR(64) NOT NULL DEFAULT 'system',
-    updated_at    TIMESTAMPTZ NOT NULL DEFAULT NOW(),
-    updated_by    VARCHAR(64) NOT NULL DEFAULT 'system'
-);
-
--- 3. Create audit table (skema identik dengan output audit-table-generator.js)
--- audit_id di-supply oleh app layer via uuidv7() — tanpa DB-side default
--- agar portable ke semua versi PostgreSQL.
-CREATE TABLE hr_karyawan_audit (
-    audit_id        VARCHAR(36) PRIMARY KEY,
-    record_pk       TEXT NOT NULL,
-    operation       VARCHAR(32) NOT NULL,
-    changed_fields  JSONB NOT NULL,
-    metadata        JSONB,
-    changed_by      VARCHAR(128),
-    changed_at      TIMESTAMPTZ NOT NULL DEFAULT NOW()
-);
-
-CREATE INDEX idx_hr_karyawan_audit_record
-    ON hr_karyawan_audit (record_pk, changed_at DESC);
-
-CREATE INDEX idx_hr_karyawan_audit_changed_at
-    ON hr_karyawan_audit (changed_at DESC);
-
--- 4. Insert 1 record uji untuk concurrent UPDATE
-INSERT INTO hr_karyawan (karyawan_id, nama, salary, bonus)
-VALUES ('test-001', 'Concurrent Test User', 5000000, 0);
-
--- 5. Confirm
-SELECT karyawan_id, nama, salary FROM hr_karyawan WHERE karyawan_id = 'test-001';
-SELECT COUNT(*) AS audit_initial_count FROM hr_karyawan_audit;

package/generators/tests/integration-tahap4b/verify.sql

@@ -1,110 +0,0 @@
--- ============================================================================
--- Tahap 4b — Integration Test Verification Script
--- ============================================================================
--- Dijalankan SETELAH run-concurrent.js selesai untuk verifikasi:
---   1. Final state record konsisten dengan salah satu request (5000001..5000100)
---   2. Audit log memuat 100 entry (atau matching dengan jumlah success)
---   3. Setiap audit entry punya struktur changed_fields.salary {old, new}
---   4. Tidak ada lost update (transition logical: nilai final ada di set request)
---
--- Eksekusi:
---   psql -h 127.0.0.1 -U postgres -d dbinv -f verify.sql
--- ============================================================================
-
--- ----------------------------------------------------------------------------
--- 1. Final state hr_karyawan/test-001
--- ----------------------------------------------------------------------------
-\echo '=== 1. FINAL STATE ==='
-SELECT
-    karyawan_id,
-    salary AS final_salary,
-    updated_at,
-    CASE
-        WHEN salary BETWEEN 5000001 AND 5000100 THEN 'OK (within expected range)'
-        ELSE 'WARN (out of range — possible test config issue)'
-    END AS verdict
-FROM hr_karyawan
-WHERE karyawan_id = 'test-001';
-
--- ----------------------------------------------------------------------------
--- 2. Audit entry count (expected: 100, or matching success count)
--- ----------------------------------------------------------------------------
-\echo ''
-\echo '=== 2. AUDIT ENTRY COUNT ==='
-SELECT
-    COUNT(*) AS audit_entry_count,
-    CASE
-        WHEN COUNT(*) = 100 THEN 'OK (100/100 — all updates audited)'
-        WHEN COUNT(*) > 0  THEN 'PARTIAL (some updates not audited — check failures in run-concurrent output)'
-        ELSE 'FAIL (zero audit entries — strict path NOT triggered, or audit table mismatched)'
-    END AS verdict
-FROM hr_karyawan_audit
-WHERE record_pk = 'test-001';
-
--- ----------------------------------------------------------------------------
--- 3. Audit JSON structure check (semua entry harus punya .salary)
--- ----------------------------------------------------------------------------
-\echo ''
-\echo '=== 3. AUDIT JSON STRUCTURE ==='
-SELECT
-    COUNT(*) AS missing_salary_audit,
-    CASE
-        WHEN COUNT(*) = 0 THEN 'OK (all audit entries have salary key)'
-        ELSE 'FAIL (some entries missing salary key — _buildChangedFieldsJSON bug)'
-    END AS verdict
-FROM hr_karyawan_audit
-WHERE record_pk = 'test-001'
-  AND NOT (changed_fields ? 'salary');
-
--- ----------------------------------------------------------------------------
--- 4. Sample 5 entry untuk inspeksi manual
--- ----------------------------------------------------------------------------
-\echo ''
-\echo '=== 4. AUDIT SAMPLE (first 5 by changed_at) ==='
-SELECT
-    changed_at,
-    operation,
-    changed_fields->'salary' AS salary_change,
-    changed_by
-FROM hr_karyawan_audit
-WHERE record_pk = 'test-001'
-ORDER BY changed_at ASC
-LIMIT 5;
-
--- ----------------------------------------------------------------------------
--- 5. Distinct new values di audit — should be ~100 unique (semua request beda)
--- ----------------------------------------------------------------------------
-\echo ''
-\echo '=== 5. DISTINCT NEW VALUES IN AUDIT ==='
-SELECT
-    COUNT(DISTINCT changed_fields->'salary'->>'new') AS distinct_new_values,
-    COUNT(*) AS total_entries,
-    CASE
-        WHEN COUNT(DISTINCT changed_fields->'salary'->>'new') = COUNT(*) THEN 'OK (all updates uniquely audited)'
-        ELSE 'INFO (some duplicate new values — bisa terjadi jika ada retry)'
-    END AS verdict
-FROM hr_karyawan_audit
-WHERE record_pk = 'test-001';
-
--- ----------------------------------------------------------------------------
--- 6. Lost update detection — nilai final ada di set audit?
--- ----------------------------------------------------------------------------
-\echo ''
-\echo '=== 6. FINAL VALUE TRACEABILITY ==='
-WITH final AS (SELECT salary::TEXT AS final_str FROM hr_karyawan WHERE karyawan_id = 'test-001')
-SELECT
-    f.final_str AS final_salary,
-    EXISTS (
-        SELECT 1 FROM hr_karyawan_audit
-        WHERE record_pk = 'test-001'
-          AND changed_fields->'salary'->>'new' = f.final_str
-    ) AS final_value_in_audit,
-    CASE
-        WHEN EXISTS (
-            SELECT 1 FROM hr_karyawan_audit
-            WHERE record_pk = 'test-001'
-              AND changed_fields->'salary'->>'new' = f.final_str
-        ) THEN 'OK (final value traceable in audit log)'
-        ELSE 'FAIL (final value not in audit — atomicity issue!)'
-    END AS verdict
-FROM final f;