Removing inspector tests, implemented application tests instead #99
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implemented application tests as proof of concept instead of inspector tests
Motivation and Context
Currently pipelines are failing

I believe that PHP version of tests fits better to PHP SDK and has a lot of benefits.
How Has This Been Tested?
Breaking Changes
No
Types of changes
Checklist
Additional context
I couldn't test initialize response via Inspector tests, so as discussed in slack tried to implement Application tests as proof of concept.
npx
package, no version pin- Require
npm
/npx
, adds infrastructure dependency- Generally slow
- Limited method coverage (
tools/list
,tools/call
,resources/*
,prompts/*
,logging/setLevel
)- Cannot access
initialize
response, can’t test server capabilities- Coding agents can’t run
npx
inside sandboxed envs- No
npm
/npx
dependency- Very fast (≈200 ms for
ManualStdioExampleTest
)- Easy to implement
- Flexible — can extend with custom client logic (e.g. initialization, logger setup)
- Missing handlers won’t automatically raise MCP errors
If we will add some client logic to ApplicationTestCase like initialization, logger setting etc. it will work same as Inspector but without overheads of npm.
Test runs are very fast:

Testing is quite easy to implement, server responses indexed by ids and very easy to get for comparison.