Analyze SOAP Contracts
1. Confirm Scope
- Confirm that SOAP or WSDL is truly in scope.
- Keep this skill for contract analysis and scenario design.
- Escalate if the user expects a dedicated SOAP framework rather than Rest Assured-based HTTP and XML checks.
2. Load The Contract
- Run
python scripts/extract_wsdl_summary.py --input <path>to extract services, ports, and operations. - Read wsdl-analysis.md when namespaces or bindings are complex.
3. Extract Testable Surface
- List services, ports, operations, and SOAP actions.
- List required request elements and expected response elements when visible.
- List fault contracts and fault codes when declared.
4. Convert To Test Candidates
- Create happy-path candidates per operation.
- Create XML validation candidates for required fields and namespaces.
- Create fault-path candidates from declared SOAP faults.
- Flag WS-Security and complex attachment cases explicitly.
5. Examples
- Input:
Derive tests from legacy/customer.wsdl.Output: A SOAP operation matrix with required XML elements, faults, and auth concerns.
6. Troubleshooting
- Problem: The WSDL imports external schemas that are missing. Fix: Resolve the schema set before finalizing the scenario list.
- Problem: The target uses heavy WS-Security or attachments. Fix: State that Rest Assured may not be the best primary implementation tool for that branch.