sites/SYSTEM
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(agile): properly state nuxt4 in tech-stack.md, define test/unit directory in testing-requirements.md

Browse Source
This commit is contained in:
h
2025-09-03 02:16:10 +03:00
parent fcbae5a4c5
commit bd9775af3f
2 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/architecture/tech-stack.md
View File

@@ -1,9 +1,9 @@
# 3. Tech Stack (Revised)
| Category | Technology | Version | Purpose & Rationale |
| :--- | :--- | :--- | :--- |
| **Fullstack Framework**| **Nuxt** | `^4.0.3` | Core framework for both frontend and backend (server routes). |
| **Database ORM** | **Prisma** | `latest` | Next-generation ORM for type-safe database access and automated migrations. |
| **Database** | **PostgreSQL** | `latest` | Robust, reliable SQL database managed by Prisma. |
| **Deployment** | **Docker Compose**| `latest` | For containerizing and managing the application stack. |
| ... | *(rest of the stack remains the same)* | ... | ... |
| Category | Technology | Version | Purpose & Rationale |
| :--- | :--- | :--- |:---------------------------------------------------------------------------------------------------------------|
| **Fullstack Framework**| **Nuxt** | `^4.0.3` | Core framework for both frontend and backend (server routes). Note that its structure differs from Nuxt 3 and you should check context7 for details |
| **Database ORM** | **Prisma** | `latest` | Next-generation ORM for type-safe database access and automated migrations. |
| **Database** | **PostgreSQL** | `latest` | Robust, reliable SQL database managed by Prisma. |
| **Deployment** | **Docker Compose**| `latest` | For containerizing and managing the application stack. |
| ... | *(rest of the stack remains the same)* | ... | ... |

2
docs/architecture/testing-requirements.md
View File

@@ -3,5 +3,5 @@
Testing is critical for ensuring the integrity of the system.
* **Unit Tests:** We will use **Vitest** for unit testing. Every composable and service function must have unit tests covering its logic.
* **Component Tests:** We will use **`@vue/test-utils`** to test individual Vue components. Tests should verify that components render correctly based on props and that they emit events when interacted with.
* **Test Location:** All test files will be located alongside the file they are testing, with a `.spec.ts` extension (e.g., `useLedger.spec.ts`).
* **Test Location:** All test files will be located alongside the file they are testing, with a `.spec.ts` extension (e.g., `useLedger.spec.ts`). Server tests will be located in the `test/unit` directory.