docs(): add description and test instructions

Author: tomalaforge

apps/forms/65-signal-form-edition/README.md

@@ -8,6 +8,12 @@
 npx nx serve forms-signal-form-edition
 ```
 
+### Run Tests
+
+```bash
+npx nx test forms-signal-form-edition
+```
+
 ### Documentation and Instruction
 
 Challenge documentation is [here](https://angular-challenges.vercel.app/challenges/forms/65-signal-form-edition/).

docs/src/content/docs/challenges/forms/65-signal-form-edition.md

@@ -1,6 +1,6 @@
 ---
 title: 🟠 signal-form-edition
-description: Challenge 65 is about ...
+description: Refactor a user management form to use Angular's new Signal-based Forms API.
 author: thomas-laforge
 contributors:
   - tomalaforge
@@ -13,9 +13,9 @@ sidebar:
 
 ## Information
 
-Angular has introduced a new way to work with forms using Signals. This modern approach provides better type safety, reactivity, and a more intuitive API compared to traditional Reactive Forms.
+Angular has introduced a new way to work with forms using Signals. This modern approach provides better reactivity and a more intuitive API compared to traditional Reactive Forms.
 
-In this challenge, you will maintain a user management application. The current implementation uses Reactive Forms (`FormControl`, `FormGroup`). Your goal is to migrate it to the new Signal-based Forms API.
+In this challenge, you will refactor a user management application. The current implementation uses traditional Reactive Forms. Your goal is to migrate it to the new Signal-based Forms API.
 
 ## Statement
 
@@ -25,7 +25,7 @@ The application allows listing, adding, and editing users. It includes:
 - **User Form**: A form used for both adding and editing users.
 - **Fake Backend**: Simulates HTTP calls with a 500ms delay.
 
-Your goal is to **refactor the `UserFormComponent` to use Angular's new Signal-based Forms API** while maintaining exactly the same functionality and validation rules.
+Your goal is to **refactor the `UserFormComponent` to use Angular's Signal-based Forms API** while maintaining exactly the same functionality and validation rules.
 
 ### Current Implementation
 
@@ -35,18 +35,29 @@ The form currently uses:
 - `Validators` for mandatory fields (`firstname`, `lastname`, `age`) and minimum age.
 - `patchValue` and `reset` for managing form state during edition.
 
+The application also uses `rxResource` to load users and navigation to handle the editing context.
+
 ### Expected Result
 
-After completing the challenge, your application should:
+After completing the challenge:
 
 - Use Signal-based form instead of `FormControl` and `FormGroup` in `UserFormComponent`.
 - Maintain all existing validation rules and error messages.
 - Correctly handle the transition between "Add" and "Edit" modes.
-- Keep the 500ms delay simulation working via the service.
 - Maintain the same UI and user experience.
 
+## Testing
+
+A comprehensive test suite is provided to ensure your refactoring doesn't break any functionality. You can run the tests using:
+
+```bash
+npx nx test forms-signal-form-edition
+```
+
+These tests verify the entire user management flow, including adding, editing, and deleting users, as well as form validation.
+
 ## Constraints
 
 - Do not modify the `FakeBackendService` or `User` model.
-- You can refactor `AppComponent` and `UserListComponent` if necessary to better support signals, but the primary focus is the form.
+- You can refactor other components if necessary, but the primary focus is the `UserFormComponent`.
 - The form must properly validate inputs before submission.