Added more integration tests

Author: coolwednesday

store/README.md

@@ -20,8 +20,9 @@ go install gofr.dev/cli/gofr@latest
    ```
    This creates:
    - `stores/store.yaml` — central configuration template
+   - `stores/all.go` — store registry factory (auto-generated)
    - `stores/user/interface.go` — initial interface stub
-   - `stores/user/user.go` — initial implementation stub
+   - `stores/user/user.go` — initial implementation stub (editable)
 
 2. **Edit `stores/store.yaml`** with your models and queries (see Configuration Reference below).
 
@@ -57,16 +58,27 @@ gofr store generate -config=custom-store.yaml
 
 ### Project Structure
 
-After generation, your project will have:
+**After `gofr store init -name=user`:**
 
 ```
 stores/
-├── store.yaml          # Central configuration
-├── all.go              # Store registry factory (auto-generated)
+├── store.yaml          # Central configuration template (edit this)
+├── all.go              # Store registry factory (auto-generated, DO NOT EDIT)
 └── user/
-    ├── interface.go    # UserStore interface
-    ├── userStore.go    # userStore implementation boilerplate
-    └── user.go         # User model (if generated)
+    ├── interface.go    # UserStore interface stub (DO NOT EDIT — regenerated by generate)
+    └── user.go         # userStore implementation stub (editable — add your SQL logic here)
+```
+
+**After `gofr store generate`:**
+
+```
+stores/
+├── store.yaml          # Central configuration (source of truth)
+├── all.go              # Store registry factory (DO NOT EDIT)
+└── user/
+    ├── interface.go    # UserStore interface (DO NOT EDIT — regenerated each time)
+    ├── userStore.go    # userStore implementation boilerplate (add SQL logic here)
+    └── user.go         # User model (if defined in YAML, DO NOT EDIT)
 ```
 
 ### Using Generated Stores
@@ -162,7 +174,7 @@ models:
 | `output_dir` | Directory for generated files | Optional (defaults to `stores/<name>`) |
 | `interface` | Interface name — **recommended: `<Name>Store`** (e.g., `UserStore`) | Optional (defaults to `<Name>Store`) |
 | `implementation` | Implementation struct name (e.g., `userStore`) | Optional (defaults to `<name>Store`) |
-| `queries` | Array of database queries | **Yes** |
+| `queries` | Array of database queries | Optional |
 
 > **⚠️ Naming Convention:** The registry (`stores/all.go`) automatically appends `"Store"` when building constructor calls. To avoid compilation errors, always name your interface as `<Name>Store` (e.g., `UserStore`) and the generated constructor will be `New<Name>Store()`.
 
@@ -309,7 +321,7 @@ func (User) TableName() string {
 
 ## Best Practices
 
-1. **Never Edit Generated Files**: Files marked `DO NOT EDIT` (`interface.go`, `all.go`) are overwritten on every generation. Keep custom SQL logic in your implementation file (e.g., `userStore.go`).
+1. **Know Which Files Are Auto-Generated**: Only `interface.go` and `all.go` are marked `DO NOT EDIT` and are overwritten on every `gofr store generate`. The implementation stub (`<name>.go` or `<name>Store.go`) created by `gofr store init` is editable — this is where you add your SQL logic.
 2. **Use `<Name>Store` Interface Names**: This ensures the registry and constructor align correctly.
 3. **Commit your YAML**: Treat `store.yaml` as source of truth. Re-run `gofr store generate` after every change.
 4. **Reference Existing Models**: If you already have model structs, use the `path` + `package` fields to avoid duplication.