Add end-to-end test command to developer CLI with comprehensive Playwright integration (#776)

### Summary & Motivation

This change adds a new `e2e` command to the developer CLI that provides
a streamlined way to run Playwright end-to-end tests which will be
introduce in the next change. The command offers comprehensive test
execution capabilities with smart defaults and extensive configuration
options.

Key features:
- Automatic server availability checking before running tests
- Support for running tests across multiple self-contained systems
- Flexible test filtering by search terms, tags (@smoke,
@comprehensive), or file patterns
- Browser selection (chromium, firefox, webkit, safari, all)
- Interactive debugging with Playwright Inspector
- Performance analysis with timing output
- Test artifacts management (videos, traces, reports)
- Smart test retry logic for flaky tests
- Parallel test execution with configurable workers

Additional improvements:
- Enhanced SQLite configuration in test base classes to better match SQL
Server behavior
- Updated AI rules to enforce using the developer CLI for all test
commands
- Added preprocessing for command-line arguments to handle @ symbols in
search terms

### Checklist

- [x] I have added tests, or done manual regression tests
- [x] I have updated the documentation, if necessary

Author: tjementum

.cursor/rules/tools.mdc

@@ -9,6 +9,8 @@ alwaysApply: true
 * BrowserMCP: Use this to troubleshoot frontend issues. The base URL is https://localhost:9000. The website is already running, so never start it manually.
 * `[PRODUCT_MANAGEMENT_TOOL]`: Use this MCP tool to create and manage product backlog items. 
 
+If an MCP Server is not responding, instruct the user to activate it rather than using workarounds like calling `curl` when the browser MCP is unavailable.
+
 # Product Management Tools
 
 > **Update this value in ONE place:**
@@ -25,7 +27,7 @@ Use the `[CLI_ALIAS]` Developer CLI to build, test, and format backend and front
 
 Always use the Developer CLI to build, test, and format code correctly over using direct commands like `npm run format` or `dotnet test`.
 
-**IMPORTANT:** Never fall back to using direct commands like `npm run format` or `dotnet test`. Always use the Developer CLI with the appropriate alias.
+**IMPORTANT:** Never fall back to using direct commands like `npm run format`, `dotnet test`, `npx playwright test`, `npm test`, etc. Always use the Developer CLI with the appropriate alias.
 
 ## CLI Alias Configuration
 
@@ -67,6 +69,29 @@ After you have completed a backend task and want to ensure that it works as expe
 [CLI_ALIAS] test --solution-name <solution-name>
 ```
 
+## End-to-End Test Commands
+
+```bash
+# Run all end-to-end tests except slow tests
+[CLI_ALIAS] e2e
+
+# Run end-to-end tests for specific so  lution
+[CLI_ALIAS] e2e --self-contained-system <self-contained-system-name>
+
+# Run end-to-end tests for specific browser
+[CLI_ALIAS] e2e --browser <browser-name>
+
+# Run end-to-end tests for specific search term
+[CLI_ALIAS] e2e <search-term>
+
+# Run end-to-end tests for specific test tags
+[CLI_ALIAS] e2e "@smoke"
+[CLI_ALIAS] e2e "smoke"
+[CLI_ALIAS] e2e "@comprehensive"
+```
+
+Any combination of the above parameters is possible. There are other parameters available, but you should only use the ones mentioned above.
+
 ## Format Commands
 
 Run these commands before you commit your changes.

.windsurf/rules/tools.md

@@ -9,6 +9,8 @@ description: You have access to several tools and MCP servers
 * BrowserMCP: Use this to troubleshoot frontend issues. The base URL is https://localhost:9000. The website is already running, so never start it manually.
 * `[PRODUCT_MANAGEMENT_TOOL]`: Use this MCP tool to create and manage product backlog items. 
 
+If an MCP Server is not responding, instruct the user to activate it rather than using workarounds like calling `curl` when the browser MCP is unavailable.
+
 # Product Management Tools
 
 > **Update this value in ONE place:**
@@ -25,7 +27,7 @@ Use the `[CLI_ALIAS]` Developer CLI to build, test, and format backend and front
 
 Always use the Developer CLI to build, test, and format code correctly over using direct commands like `npm run format` or `dotnet test`.
 
-**IMPORTANT:** Never fall back to using direct commands like `npm run format` or `dotnet test`. Always use the Developer CLI with the appropriate alias.
+**IMPORTANT:** Never fall back to using direct commands like `npm run format`, `dotnet test`, `npx playwright test`, `npm test`, etc. Always use the Developer CLI with the appropriate alias.
 
 ## CLI Alias Configuration
 
@@ -67,6 +69,29 @@ After you have completed a backend task and want to ensure that it works as expe
 [CLI_ALIAS] test --solution-name <solution-name>
 ```
 
+## End-to-End Test Commands
+
+```bash
+# Run all end-to-end tests except slow tests
+[CLI_ALIAS] e2e
+
+# Run end-to-end tests for specific so  lution
+[CLI_ALIAS] e2e --self-contained-system <self-contained-system-name>
+
+# Run end-to-end tests for specific browser
+[CLI_ALIAS] e2e --browser <browser-name>
+
+# Run end-to-end tests for specific search term
+[CLI_ALIAS] e2e <search-term>
+
+# Run end-to-end tests for specific test tags
+[CLI_ALIAS] e2e "@smoke"
+[CLI_ALIAS] e2e "smoke"
+[CLI_ALIAS] e2e "@comprehensive"
+```
+
+Any combination of the above parameters is possible. There are other parameters available, but you should only use the ones mentioned above.
+
 ## Format Commands
 
 Run these commands before you commit your changes.

application/account-management/Tests/EndpointBaseTest.cs

@@ -49,6 +49,27 @@ protected EndpointBaseTest()
         // Create connection and add DbContext to the service collection
         Connection = new SqliteConnection("DataSource=:memory:");
         Connection.Open();
+
+        // Configure SQLite to behave more like SQL Server
+        using (var command = Connection.CreateCommand())
+        {
+            // Enable foreign key constraints (SQL Server has this by default)
+            command.CommandText = "PRAGMA foreign_keys = ON;";
+            command.ExecuteNonQuery();
+
+            // Enable recursive triggers (SQL Server supports nested triggers)
+            command.CommandText = "PRAGMA recursive_triggers = ON;";
+            command.ExecuteNonQuery();
+
+            // Enforce CHECK constraints (SQL Server enforces these by default)
+            command.CommandText = "PRAGMA ignore_check_constraints = OFF;";
+            command.ExecuteNonQuery();
+
+            // Use more strict query parsing
+            command.CommandText = "PRAGMA trusted_schema = OFF;";
+            command.ExecuteNonQuery();
+        }
+
         Services.AddDbContext<TContext>(options => { options.UseSqlite(Connection); });
 
         Services.AddAccountManagementServices();

application/back-office/Tests/EndpointBaseTest.cs

@@ -49,6 +49,27 @@ protected EndpointBaseTest()
         // Create connection and add DbContext to the service collection
         Connection = new SqliteConnection("DataSource=:memory:");
         Connection.Open();
+
+        // Configure SQLite to behave more like SQL Server
+        using (var command = Connection.CreateCommand())
+        {
+            // Enable foreign key constraints (SQL Server has this by default)
+            command.CommandText = "PRAGMA foreign_keys = ON;";
+            command.ExecuteNonQuery();
+
+            // Enable recursive triggers (SQL Server supports nested triggers)
+            command.CommandText = "PRAGMA recursive_triggers = ON;";
+            command.ExecuteNonQuery();
+
+            // Enforce CHECK constraints (SQL Server enforces these by default)
+            command.CommandText = "PRAGMA ignore_check_constraints = OFF;";
+            command.ExecuteNonQuery();
+
+            // Use more strict query parsing
+            command.CommandText = "PRAGMA trusted_schema = OFF;";
+            command.ExecuteNonQuery();
+        }
+
         Services.AddDbContext<TContext>(options => { options.UseSqlite(Connection); });
 
         Services.AddBackOfficeServices();