|
1 | 1 | --- |
2 | | -description: Test the Bun Module generator end-to-end |
3 | | ---- |
4 | | - |
5 | | -# Testing the Bun Module Generator |
6 | | - |
7 | | -You are a generator testing coordinator. Use the Task tool to delegate testing phases to specialized subagents. Execute these phases in sequence: |
8 | | - |
9 | | -## Phase 1: Environment Setup & Prerequisites |
10 | | - |
11 | | -Use a general subagent to verify the environment is ready: |
12 | | - |
13 | | -**Task:** Verify prerequisites for generator testing |
14 | | - |
15 | | -- Check Bash is installed: `bash --version` |
16 | | -- Check git is configured: `git config user.name` and `git config user.email` |
17 | | -- Create or use test directory |
18 | | -- Report environment status |
19 | | - |
20 | | -## Phase 2: Clone & Run Generator |
21 | | - |
22 | | -Use a general subagent to: |
23 | | - |
24 | | -- Clone template repo |
25 | | -- Run `./setup.sh` with test inputs: |
26 | | - - Module name: `test-module` |
27 | | - - Description: `A test module` |
28 | | - - Author: `Test User` |
29 | | - - Email: `test@example.com` |
30 | | - - Repo: `https://github.com/test/test-module` |
31 | | - - GitHub org: `test` |
32 | | - |
33 | | -## Phase 3: Verify Generator Output |
34 | | - |
35 | | -Using `task(general)` to validate: |
36 | | - |
37 | | -**Files Generated:** |
| 2 | +description: Test Palantir documentation tools |
| 3 | +--- |
38 | 4 |
|
39 | | -- `package.json`, `src/index.ts`, `README.md`, `.github/workflows/` |
40 | | -- All expected template files present |
| 5 | +# Palantir Plugin Tool Test |
41 | 6 |
|
42 | | -**Generator Cleanup:** |
| 7 | +You are testing the Palantir Foundry documentation tools. Follow these rules strictly: |
43 | 8 |
|
44 | | -- `template/` removed |
45 | | -- `setup.sh` removed |
46 | | -- Old `.git/` replaced with fresh repo |
| 9 | +## Rules |
47 | 10 |
|
48 | | -**Git Repository:** |
| 11 | +1. Use ONLY the `list_all_docs` and `get_doc_page` tools. Do NOT use web search, file reading, or any other tools. |
| 12 | +2. NEVER guess a URL. Always start with `list_all_docs` to discover available pages. |
| 13 | +3. When looking for information, first list all docs, then identify candidate pages by title, then read them one at a time. |
| 14 | +4. If information spans multiple pages, read ALL relevant pages before synthesizing. |
49 | 15 |
|
50 | | -- `.git/` exists and initialized |
51 | | -- On `main` branch |
52 | | -- Initial commit exists |
53 | | -- Remote origin configured |
| 16 | +## Test Sequence |
54 | 17 |
|
55 | | -**Template Rendering:** |
| 18 | +### Step 1: Verify list_all_docs |
56 | 19 |
|
57 | | -- `package.json` name matches `test-module` (kebab-case) |
58 | | -- `description`, `author.name`, `author.email` correctly templated |
59 | | -- `repository.url` set correctly |
60 | | -- `README.md` contains module name and author info |
| 20 | +Call `list_all_docs`. Confirm it returns a list with 3,000+ pages. Report the exact count. |
61 | 21 |
|
62 | | -**Kebab-Case Conversion:** |
| 22 | +### Step 2: Find and read a specific topic |
63 | 23 |
|
64 | | -- Test with various formats: CamelCase, spaces, underscores, special chars |
65 | | -- Verify all convert correctly to kebab-case |
| 24 | +Using ONLY the list from Step 1, find pages related to "Ontology". Identify 3+ candidate pages by their titles. Read each one using `get_doc_page` with the exact URL from the list. Summarize what you learned about Ontology from across these pages. |
66 | 25 |
|
67 | | -## Phase 4: Build & Verify Module |
| 26 | +### Step 3: Cross-page information retrieval |
68 | 27 |
|
69 | | -Use a general subagent to: |
| 28 | +Using ONLY the list from Step 1, find pages related to "Pipeline Builder" or "Transforms". Read at least 2 pages. Explain how Pipelines relate to the Ontology based ONLY on what the documentation says. |
70 | 29 |
|
71 | | -- Run `bun install` |
72 | | -- Run `mise run build` |
73 | | -- Run `mise run lint` |
74 | | -- Run `mise run test` |
75 | | -- Verify all steps succeed |
| 30 | +### Step 4: Edge cases |
76 | 31 |
|
77 | | -## Phase 5: Results & Reporting |
| 32 | +- Try `get_doc_page` with a URL that does NOT exist (e.g., `/nonexistent/page/`). Confirm it returns a "not found" message. |
| 33 | +- Find a page with a long URL path (3+ segments). Read it successfully. |
78 | 34 |
|
79 | | -Compile results from all phases: |
| 35 | +### Step 5: Report |
80 | 36 |
|
81 | | -- Overall pass/fail status |
82 | | -- List of any failures or issues |
83 | | -- Generated module path location |
84 | | -- Next development steps for the user |
| 37 | +Summarize: |
85 | 38 |
|
86 | | -Execute all phases in order using the Task tool with appropriate subagent types. Provide the user with a comprehensive test report upon completion. |
| 39 | +- Total pages available |
| 40 | +- Pages successfully read |
| 41 | +- Any failures or unexpected results |
| 42 | +- Whether cross-page information retrieval worked correctly |
0 commit comments