Move e2etestprompts.md to docs (#992)

Author: jongio

.github/PULL_REQUEST_TEMPLATE.md

@@ -19,7 +19,7 @@
     - [ ] **One tool per PR**: This PR adds or modifies only one MCP tool for faster review cycles
     - [ ] Updated `README.md` documentation
     - [ ] Updated command list in `/docs/azmcp-commands.md`
-    - [ ] Updated test prompts in `/e2eTests/e2eTestPrompts.md`
+    - [ ] Updated test prompts in `/docs/e2eTestPrompts.md`
     - [ ] For new or modified tool descriptions, ran the `eng/tools/ToolDescriptionEvaluator` tool and obtained a result >= 0.4
 - [ ] 👉 For Community (non-Azure team member) PRs:
     - [ ] **Security review**: Reviewed code for security vulnerabilities, malicious code, or suspicious activities before running tests (`crypto mining, spam, data exfiltration, etc.`)

CONTRIBUTING.md

@@ -134,7 +134,7 @@ The project is organized as follows:
 
 5. **Update documentation**:
    - Add the new command to [/docs/azmcp-commands.md](https://github.com/Azure/azure-mcp/blob/main/docs/azmcp-commands.md)
-   - Add test prompts for the new command in [/e2eTests/e2eTestPrompts.md](https://github.com/Azure/azure-mcp/blob/main/e2eTests/e2eTestPrompts.md)
+   - Add test prompts for the new command in [/docs/e2eTestPrompts.md](https://github.com/Azure/azure-mcp/blob/main/docs/e2eTestPrompts.md)
    - Update [README.md](https://github.com/Azure/azure-mcp/blob/main/README.md) to mention the new command
 
 6. **Add CODEOWNERS entry** in [CODEOWNERS](https://github.com/Azure/azure-mcp/blob/main/.github/CODEOWNERS) [(example)](https://github.com/Azure/azure-mcp/commit/08f73efe826d5d47c0f93be5ed9e614740e82091)
@@ -167,7 +167,7 @@ Requirements:
 
 ### End-to-end Tests
 
-End-to-end tests are performed manually. Command authors must thoroughly test each command to ensure correct tool invocation and results. At least one prompt per tool is required and should be added to `/e2eTests/e2eTestPrompts.md`.
+End-to-end tests are performed manually. Command authors must thoroughly test each command to ensure correct tool invocation and results. At least one prompt per tool is required and should be added to `/docs/e2eTestPrompts.md`.
 
 ### Testing Local Build with VS Code
 

e2eTests/e2eTestPrompts.md renamed to docs/e2eTestPrompts.md

@@ -1403,7 +1403,7 @@ catch (Exception ex)
 
         ```bash
         # Prompts:
-        # Use markdown format (same as e2eTests/e2eTestPrompts.md):
+        # Use markdown format (same as docs/e2eTestPrompts.md):
         dotnet run -- --prompts-file my-prompts.md
 
         # Use JSON format:
@@ -1426,7 +1426,7 @@ catch (Exception ex)
       - If validation shows POOR results or a confidence score of < 0.4, refine your description and test again
 
     - Custom prompts file formats:
-      - **Markdown format**: Use same table format as `e2eTests/e2eTestPrompts.md`:
+      - **Markdown format**: Use same table format as `docs/e2eTestPrompts.md`:
 
         ```markdown
         | Tool Name | Test Prompt |
@@ -1781,7 +1781,7 @@ Before submitting:
 - [ ] **docs/azmcp-commands.md**: Add command documentation with description, syntax, parameters, and examples
 - [ ] **README.md**: Update the supported services table and add example prompts demonstrating the new command(s) in the appropriate area section
 - [ ] **eng/vscode/README.md**: Update the VSIX README with new service area (if applicable) and add sample prompts to showcase new command capabilities
-- [ ] **e2eTests/e2eTestPrompts.md**: Add test prompts for end-to-end validation of the new command(s)
+- [ ] **docs/e2eTestPrompts.md**: Add test prompts for end-to-end validation of the new command(s)
 - [ ] **.github/CODEOWNERS**: Add new area to CODEOWNERS file for proper ownership and review assignments
 
 **Documentation Standards**:

docs/new-command.md

@@ -71,7 +71,7 @@ try {
     try {
         # Check if we have the required sources for dynamic loading
         $hasSourceCode = Test-Path "$RepoRoot/src"
-        $hasMarkdownPrompts = Test-Path "$RepoRoot/e2eTests/e2eTestPrompts.md"
+        $hasMarkdownPrompts = Test-Path "$RepoRoot/docs/e2eTestPrompts.md"
 
         # Check if we have fallback test data files
         $hasToolsData = Test-Path "tools.json"
@@ -154,7 +154,7 @@ try {
             if ($resolvedPromptsFile) {
                 Write-Host "💬 Prompts File: $resolvedPromptsFile"
             } else {
-                Write-Host "💬 Prompts Source: $RepoRoot/e2eTests/e2eTestPrompts.md"
+                Write-Host "💬 Prompts Source: $RepoRoot/docs/e2eTestPrompts.md"
             }
             Write-Host "📄 Output Format: $(if ($OutputMarkdown) { 'Markdown' } else { 'Plain Text' })"
         }

eng/scripts/Test-ToolSelection.ps1

@@ -257,7 +257,7 @@ static async Task Main(string[] args)
             {
                 // Use default fallback logic
 
-                var defaultPromptsPath = Path.Combine(repoRoot, "e2eTests", "e2eTestPrompts.md");
+                var defaultPromptsPath = Path.Combine(repoRoot, "docs", "e2eTestPrompts.md");
                 toolNameAndPrompts = await LoadPromptsFromMarkdownAsync(defaultPromptsPath, isCiMode);
 
                 // Save parsed prompts to prompts.json for future use

eng/tools/ToolDescriptionEvaluator/Program.cs

@@ -32,7 +32,7 @@ Or copy `.env.example` to `.env` and fill in your credentials.
 ### Typical Workflow
 
 1. Add or update a tool description in the project
-2. Add test prompts for your tool to `/e2eTests/e2eTestPrompts.md`
+2. Add test prompts for your tool to `/docs/e2eTestPrompts.md`
 3. Run the analyzer using PowerShell
 
     ```pwsh

eng/tools/ToolDescriptionEvaluator/Quickstart.md

@@ -7,7 +7,7 @@ This is a testing and analysis tool that evaluates how well Azure MCP Server too
 The application:
 
 1. Loads tool definitions from the Azure MCP Server (dynamically or from JSON files)
-1. Loads test prompts from markdown or JSON files (default: `e2eTests/e2eTestPrompts.md`)
+1. Loads test prompts from markdown or JSON files (default: `docs/e2eTestPrompts.md`)
 1. Creates embeddings for tool descriptions using Azure OpenAI's `text-embedding-3-large` model
 1. Tests prompt-to-tool matching using vector similarity search with cosine similarity
 1. Generates confidence scores and analysis reports to identify gaps in tool selection accuracy
@@ -83,7 +83,7 @@ The tool can load data from multiple sources:
 
 ### Test Prompts
 
-- **Markdown format** (default): Uses `../../../e2eTests/e2eTestPrompts.md`
+- **Markdown format** (default): Uses `../../../docs/e2eTestPrompts.md`
 - **JSON format**: Uses `prompts.json` or custom file specified with `--prompts-file`
 - **Custom files**: Supports both `.md` and `.json` formats
 
@@ -191,7 +191,7 @@ The tool provides several key metrics:
 
 #### Markdown Format (Default)
 
-The tool reads from `e2eTests/e2eTestPrompts.md` which contains tables like:
+The tool reads from `docs/e2eTestPrompts.md` which contains tables like:
 
 ```markdown
 ## Azure Storage