feat: add critical testing approach guidelines for Laravel Dusk
This commit is contained in:
parent
50e5fb7f3f
commit
33688b55be
1 changed files with 7 additions and 0 deletions
7
.github/copilot-instructions.md
vendored
7
.github/copilot-instructions.md
vendored
|
|
@ -44,6 +44,13 @@ This application is a Laravel application and its main Laravel ecosystems packag
|
||||||
## Documentation Files
|
## Documentation Files
|
||||||
- You must only create documentation files if explicitly requested by the user.
|
- You must only create documentation files if explicitly requested by the user.
|
||||||
|
|
||||||
|
## Testing Approach - CRITICAL
|
||||||
|
- **THE APPLICATION IS 100% WORKING** - All functionality works perfectly in production.
|
||||||
|
- When writing or debugging browser tests (Laravel Dusk), focus ONLY on test syntax, selectors, and Dusk interaction methods.
|
||||||
|
- NEVER assume the application has bugs or suggest app fixes - the issue is always in the test code.
|
||||||
|
- Trust the existing functionality and work on getting the correct CSS selectors, XPath expressions, and Dusk methods.
|
||||||
|
- If manual interaction works but the test fails, the problem is the test implementation, not the app.
|
||||||
|
|
||||||
|
|
||||||
=== boost rules ===
|
=== boost rules ===
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue