claude-mpm 4.20.3__py3-none-any.whl → 4.25.10__py3-none-any.whl

claude_mpm/skills/bundled/testing/webapp-testing/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

claude_mpm/skills/bundled/testing/webapp-testing/SKILL.md

@@ -1,96 +1,184 @@
 ---
 name: webapp-testing
-description: Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
+version: 2.0.0
+category: testing
+description: Automated webapp testing with Playwright. Server management, UI testing, visual debugging, and reconnaissance-first approach.
 license: Complete terms in LICENSE.txt
+progressive_disclosure:
+  entry_point:
+    summary: "Reconnaissance before action: verify server state and page load before testing"
+    when_to_use: "When testing web applications with Playwright. Server verification, UI testing, frontend debugging."
+    quick_start: "1. Check server with lsof 2. Start with with_server.py 3. Wait for networkidle 4. Screenshot and verify"
+  references:
+    - playwright-patterns.md
+    - server-management.md
+    - reconnaissance-pattern.md
+    - decision-tree.md
+    - troubleshooting.md
 ---
 
-# Web Application Testing
+# Webapp Testing
 
-To test local web applications, write native Python Playwright scripts.
+## Overview
 
-**Helper Scripts Available**:
-- `scripts/with_server.py` - Manages server lifecycle (supports multiple servers)
+**Core Principle: Reconnaissance Before Action**
 
-**Always run scripts with `--help` first** to see usage. DO NOT read the source until you try running the script first and find that a customized solution is abslutely necessary. These scripts can be very large and thus pollute your context window. They exist to be called directly as black-box scripts rather than ingested into your context window.
+Automated webapp testing using Playwright with a focus on verifying system state (server status, page load, element presence) before taking any action. This ensures reliable, debuggable tests that fail for clear reasons.
 
-## Decision Tree: Choosing Your Approach
+**Key capabilities:**
+- Automated browser testing with Playwright
+- Server lifecycle management
+- Visual reconnaissance (screenshots, DOM inspection)
+- Network monitoring and debugging
 
-```
-User task → Is it static HTML?
-    ├─ Yes → Read HTML file directly to identify selectors
-    │         ├─ Success → Write Playwright script using selectors
-    │         └─ Fails/Incomplete → Treat as dynamic (below)
-    │
-    └─ No (dynamic webapp) → Is the server already running?
-        ├─ No → Run: python scripts/with_server.py --help
-        │        Then use the helper + write simplified Playwright script
-        │
-        └─ Yes → Reconnaissance-then-action:
-            1. Navigate and wait for networkidle
-            2. Take screenshot or inspect DOM
-            3. Identify selectors from rendered state
-            4. Execute actions with discovered selectors
-```
+## When to Use This Skill
+
+- **Web application testing** - UI behavior, forms, navigation, integration testing
+- **Frontend debugging** - Screenshots, DOM inspection, console monitoring
+- **Regression testing** - Ensure changes don't break existing functionality
+- **Server verification** - Check servers are running and responding
+
+**Not suitable for:** Unit testing (use Jest/pytest), load testing, or API-only testing.
+
+## The Iron Law
+
+**RECONNAISSANCE BEFORE ACTION**
+
+Never execute test actions without first:
+1. **Verify server state** - `lsof -i :PORT` and `curl` checks
+2. **Wait for page ready** - `page.wait_for_load_state('networkidle')`
+3. **Visual confirmation** - Screenshot before actions
+4. **Read complete output** - Examine full results before claiming success
+
+**Why:** Tests fail mysteriously when servers aren't ready, selectors break when DOM is still building, and 5 seconds of reconnaissance saves 30 minutes of debugging.
 
-## Example: Using with_server.py
+## Quick Start
 
-To start a server, run `--help` first, then use the helper:
+### Step 1: Verify Server State
 
-**Single server:**
 ```bash
-python scripts/with_server.py --server "npm run dev" --port 5173 -- python your_automation.py
+lsof -i :3000 -sTCP:LISTEN  # Check server listening
+curl -f http://localhost:3000/health  # Test response
 ```
 
-**Multiple servers (e.g., backend + frontend):**
+### Step 2: Start Server (If Needed)
+
 ```bash
+# Single server
+python scripts/with_server.py --server "npm run dev" --port 5173 -- python test.py
+
+# Multiple servers (backend + frontend)
 python scripts/with_server.py \
   --server "cd backend && python server.py" --port 3000 \
   --server "cd frontend && npm run dev" --port 5173 \
-  -- python your_automation.py
+  -- python test.py
 ```
 
-To create an automation script, include only Playwright logic (servers are managed automatically):
+### Step 3: Write Test with Reconnaissance
+
 ```python
 from playwright.sync_api import sync_playwright
 
 with sync_playwright() as p:
-    browser = p.chromium.launch(headless=True) # Always launch chromium in headless mode
+    browser = p.chromium.launch(headless=True)
     page = browser.new_page()
-    page.goto('http://localhost:5173') # Server already running and ready
-    page.wait_for_load_state('networkidle') # CRITICAL: Wait for JS to execute
-    # ... your automation logic
+
+    # 1. Navigate and wait
+    page.goto('http://localhost:5173')
+    page.wait_for_load_state('networkidle')  # CRITICAL
+
+    # 2. Reconnaissance
+    page.screenshot(path='/tmp/before.png', full_page=True)
+    buttons = page.locator('button').all()
+    print(f"Found {len(buttons)} buttons")
+
+    # 3. Execute
+    page.click('button.submit')
+
+    # 4. Verify
+    page.wait_for_selector('.success-message')
+    page.screenshot(path='/tmp/after.png', full_page=True)
+
     browser.close()
 ```
 
-## Reconnaissance-Then-Action Pattern
+### Step 4: Verify Results
+
+Review console output, check for errors, verify state changes, examine screenshots.
+
+## Key Patterns
+
+**Server Management** - Check → Start → Wait → Test → Cleanup
+- Use `with_server.py` for automatic lifecycle management
+- Check status with `lsof`, test with `curl`
+- Automatic cleanup on exit
+
+**Reconnaissance** - Inspect → Understand → Act → Verify
+- Screenshot current state
+- Inspect DOM for elements
+- Act on discovered selectors
+- Verify results visually
+
+**Wait Strategy** - Load → Idle → Element → Action
+- Always wait for `networkidle` on dynamic apps
+- Wait for specific elements before interaction
+- Playwright auto-waits but explicit waits prevent race conditions
+
+**Selector Priority** - data-testid > role > text > CSS > XPath
+- `[data-testid="submit"]` - most stable
+- `role=button[name="Submit"]` - semantic
+- `text=Submit` - readable
+- `button.submit` - acceptable
+- XPath - last resort
+
+## Common Pitfalls
+
+❌ **Testing without server verification** - Always check `lsof` and `curl` first
+❌ **Ignoring timeout errors** - TimeoutError means something is wrong, investigate
+❌ **Not waiting for networkidle** - Dynamic apps need full page load
+❌ **Poor selector strategies** - Use data-testid for stability
+❌ **Missing network verification** - Check API responses complete
+❌ **Incomplete cleanup** - Close browsers, stop servers properly
+
+## Reference Documentation
+
+**[playwright-patterns.md](playwright-patterns.md)** - Complete Playwright reference
+Selectors, waits, interactions, assertions, test organization, network interception, screenshots, debugging
+
+**[server-management.md](server-management.md)** - Server lifecycle and operations
+with_server.py usage, manual management, port management, process control, environment config, health checks
+
+**[reconnaissance-pattern.md](reconnaissance-pattern.md)** - Philosophy and practice
+Why reconnaissance first, complete process, server checks, network diagnostics, DOM inspection, log analysis
+
+**[decision-tree.md](decision-tree.md)** - Flowcharts for every scenario
+New test decisions, server state paths, test failure diagnosis, debugging flows, selector/wait strategies
 
-1. **Inspect rendered DOM**:
-   ```python
-   page.screenshot(path='/tmp/inspect.png', full_page=True)
-   content = page.content()
-   page.locator('button').all()
-   ```
+**[troubleshooting.md](troubleshooting.md)** - Solutions to common problems
+Timeout issues, selector problems, server crashes, network errors, environment config, debugging workflow
 
-2. **Identify selectors** from inspection results
+## Examples and Scripts
 
-3. **Execute actions** using discovered selectors
+**Examples** (`examples/` directory):
+- `element_discovery.py` - Discovering page elements
+- `static_html_automation.py` - Testing local HTML files
+- `console_logging.py` - Capturing console output
 
-## Common Pitfall
+**Scripts** (`scripts/` directory):
+- `with_server.py` - Server lifecycle management (run with `--help` first)
 
-❌ **Don't** inspect the DOM before waiting for `networkidle` on dynamic apps
-✅ **Do** wait for `page.wait_for_load_state('networkidle')` before inspection
+## Integration with Other Skills
 
-## Best Practices
+**Mandatory:** verification-before-completion
+**Recommended:** systematic-debugging, test-driven-development
+**Related:** playwright-testing, selenium-automation
 
-- **Use bundled scripts as black boxes** - To accomplish a task, consider whether one of the scripts available in `scripts/` can help. These scripts handle common, complex workflows reliably without cluttering the context window. Use `--help` to see usage, then invoke directly. 
-- Use `sync_playwright()` for synchronous scripts
-- Always close the browser when done
-- Use descriptive selectors: `text=`, `role=`, CSS selectors, or IDs
-- Add appropriate waits: `page.wait_for_selector()` or `page.wait_for_timeout()`
+## Bottom Line
 
-## Reference Files
+1. **Reconnaissance always comes first** - Verify before acting
+2. **Never skip server checks** - 5 seconds saves 30 minutes
+3. **Wait for networkidle** - Dynamic apps need time
+4. **Read complete output** - Verify before claiming success
+5. **Screenshot everything** - Visual evidence is invaluable
 
-- **examples/** - Examples showing common patterns:
-  - `element_discovery.py` - Discovering buttons, links, and inputs on a page
-  - `static_html_automation.py` - Using file:// URLs for local HTML
-  - `console_logging.py` - Capturing console logs during automation
+The reconnaissance-then-action pattern is not optional - it's the foundation of reliable webapp testing.