renomeia e2e para integration

Author: edvaldoszy

compose.e2e.yml compose.integration.ymlcompose.e2e.yml renamed to compose.integration.yml

@@ -21,8 +21,8 @@
 		"build": "run-s clean build:app",
 		"test:unit": "vitest --run --project unit",
     "test:unit:watch": "vitest --project unit",
-		"test:e2e": "vitest --run --project e2e",
-		"test:e2e:watch": "vitest --project e2e",
+		"test:integration": "vitest --run --project integration",
+    "test:integration:watch": "vitest --project integration",
 		"test:coverage": "vitest --run --project unit --coverage",
 		"prepare": "husky",
 		"audit": "npm audit --audit-level=moderate",

package.json

@@ -13,7 +13,7 @@ starting the container and applying migrations before running the tests.**
 ### 1. Start the test database
 
 ```bash
-docker compose -f compose.e2e.yml up -d
+docker compose -f compose.integration.yml up -d
 ```
 
 This starts a PostgreSQL container on port **5433** using the credentials in `.env`.
@@ -45,7 +45,7 @@ npm run test:integration:watch
 ## Stopping the database
 
 ```bash
-docker compose -f compose.e2e.yml down
+docker compose -f compose.integration.yml down
 ```
 
 Since the container uses `tmpfs`, all data is lost when it stops. Start fresh

test/e2e/README.md test/integration/README.mdtest/e2e/README.md renamed to test/integration/README.md

@@ -43,7 +43,7 @@ export async function setup(): Promise<void> {
     throw new Error(
       `Cannot connect to the test database (${PG_HOST}:${PG_PORT}/${PG_DATABASE}). `
       + 'Start the container and apply the schema before running e2e tests — '
-      + 'see test/e2e/README.md'
+      + 'see test/integration/README.md'
     )
   } finally {
     await knex.destroy().catch(() => undefined)