Workshop
Beginner

Master MCP for Testing: Build, Secure & Scale Your Testing

Rejected

Session Description

Workshop Agenda

Part 1: MCP Fundamentals & Setup

  • Introduction to Model Context Protocol and its testing applications

  • Traditional testing bottlenecks vs. MCP-powered solutions

  • Development environment setup and tooling overview

Part 2: Live Build Session – Custom MCP Testing Tool

  • Build an MCP from scratch

  • Implementation of core logic and integrations

  • Testing and debugging the custom tool

Part 3: Existing MCP Tools Demonstration

  • MCP Appium Gestures – Mobile automation capabilities and setup

  • MCP Appium WebDriverAgent – iOS testing scenarios and configuration

  • Additional Testing MCPs – Browser automation, API testing, performance tools

Part 4: Security & Production Deployment

  • Authentication, authorization, and data protection best practices

  • Secure communication protocols and network security

  • MCP Scanners in action

Key Takeaways

  • Build custom MCP tools for specific testing challenges

  • Integrate existing MCP solutions like Appium Gestures and WebDriverAgent

  • Implement security measures for production MCP deployments

  • Deploy and scale MCP solutions in enterprise environments

References

Session Categories

Engineering practice - productivity, debugging
Technology / FOSS licenses, policy
Community
Which track are you applying for?
Main track

Speakers

Srinivasan Sekar
Director of Engineering LambdaTest
https://www.linkedin.com/in/srinivasan-sekar/
Srinivasan Sekar
Sai Krishna
Director of Engineering LambdaTest
Sai Krishna

Reviews

0 %
Approvability
0
Approvals
3
Rejections
0
Not Sure

We have many many submissions for MCPs and this is reading like 50% an ad for your MCP

Reviewer #1
Rejected

Combo of Appium and MCP. There is a great chance that through the workshop, the attendee may not receive a depth/understanding of both of these two topics too.

Reviewer #2
Rejected

For future submissions, we recommend that you focus on a specific and novel technical challenge you have solved or a unique contribution you have made to an open-source project, rather than presenting a generic overview of a tool.

Reviewer #3
Rejected