create-webpack-starter 0.2.3 → 0.2.4

package/CHANGELOG.md

@@ -1,5 +1,25 @@
 # Changelog
 
+## [0.2.4] - 2026-02-07
+
+### Added
+- End-to-end (E2E) test suite for CLI behavior
+- Tests for:
+  - basic project creation
+  - template selection
+  - `--dry-run` mode
+  - invalid template handling
+- Temporary directory management with automatic cleanup
+- Internal testing documentation (`docs/testing.md`)
+
+### Changed
+- Improved CLI test reliability by aligning tests with real user usage patterns
+
+### Notes
+- No changes to CLI runtime behavior
+- This release focuses on test stability and maintainability
+
+
 ## [0.2.3] - 2026-02-06
 
 ### Added

package/README.md

@@ -46,6 +46,7 @@ Detailed documentation is available in the `/docs` directory:
 - [Templates](https://github.com/Razerspine/webpack-starter-monorepo/blob/main/packages/create-webpack-starter/docs/templates.md)
 - [webpack-core](https://github.com/Razerspine/webpack-starter-monorepo/blob/main/packages/create-webpack-starter/docs/webpack-core.md)
 - [FAQ](https://github.com/Razerspine/webpack-starter-monorepo/blob/main/packages/create-webpack-starter/docs/faq.md)
+- [Testing](https://github.com/Razerspine/webpack-starter-monorepo/blob/main/packages/create-webpack-starter/docs/testing.md)
 
 The documentation explains:
 - how the CLI works internally

package/docs/testing.md

@@ -0,0 +1,74 @@
+# Testing
+
+This project uses **end-to-end (E2E) tests** to verify real CLI behavior.
+
+The goal of these tests is to simulate how a real user interacts with
+`create-webpack-starter` via `npx`, including file system side effects.
+
+---
+
+## Test structure
+
+```md
+e2e/
+├── basic.test.js # Basic project creation
+├── template.test.js # Explicit template selection
+├── dry-run.test.js # --dry-run behavior
+├── invalid-template.test.js # Invalid template handling
+├── constants/
+│ └── temp-prefix.js # Prefix for temp directories
+├── helpers/
+│ ├── run-cli.js # Spawns CLI process
+│ ├── temp-dir.js # Creates isolated temp directory
+│ └── cleanup.js # Cleans up old temp directories
+└── package.json
+```
+
+
+---
+
+## Key principles
+
+- Tests invoke the CLI **exactly as a user would**  
+  (no direct imports of internal modules).
+- CLI arguments always represent **project names**, not absolute paths.
+- The working directory (`cwd`) controls where the project is created.
+- Each test runs in an isolated temporary directory.
+- All temporary directories share a common prefix.
+
+---
+
+## Temporary directories
+
+All test-created directories use the prefix: `create-webpack-starter`
+A cleanup script removes stale directories from `/tmp` before and after tests.
+
+---
+
+## Running tests
+
+```bash
+npm run test:e2e
+```
+
+#### This command:
+* Cleans up old temp directories 
+* Runs all E2E tests sequentially
+* Cleans up again after completion
+
+#### You can also run cleanup manually:
+
+```bash
+npm run test:cleanup
+```
+
+---
+
+## Why E2E only?
+
+Since this is a CLI tool, behavior matters more than internal structure.
+E2E tests ensure that:
+* prompts work
+* files are created correctly
+* flags behave as expected
+* real-world usage remains stable over time

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-webpack-starter",
-  "version": "0.2.3",
+  "version": "0.2.4",
   "description": "Create a webpack starter with Pug, SCSS, TS and more",
   "bin": {
     "create-webpack-starter": "bin/index.js"
@@ -25,6 +25,8 @@
   ],
   "scripts": {
     "build": "tsc",
+    "test:cleanup": "node e2e/helpers/cleanup.js",
+    "test:e2e": "npm run test:cleanup && (node e2e/basic.test.js && node e2e/template.test.js && node e2e/dry-run.test.js && node e2e/invalid-template.test.js); npm run test:cleanup",
     "dev": "ts-node src/index.ts",
     "prepublishOnly": "npm run build"
   },