Skip to content
View SamuelMtzA's full-sized avatar
🏠
Working from home
🏠
Working from home

Highlights

  • Pro

Block or report SamuelMtzA

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
SamuelMtzA/README.md

πŸ‘‹ Hi, I'm Samuel Martinez

Senior SDET | Quality Engineer | Test Automation | AI-Powered QA

I'm a Senior Software Development Engineer in Test (SDET) from Mexico with 8+ years of experience building quality engineering practices, test automation frameworks, and software quality strategies across fintech, travel, e-commerce, and enterprise platforms.

My focus is not only on writing automated tests, but on engineering quality into the software development lifecycle β€” from requirements and exploratory testing to automation, CI/CD, observability, production validation, and continuous improvement.


πŸ§ͺ What I Do

  • πŸ—οΈ Build QA and Quality Engineering practices from scratch
  • πŸ€– Design scalable test automation frameworks
  • 🎭 Build UI automation with Playwright, TypeScript, Cypress, and Selenium
  • πŸ”Œ Perform API and integration testing
  • πŸ—„οΈ Validate databases, data pipelines, and ETL/EL processes
  • ☁️ Test cloud-based applications and AWS services
  • πŸ”„ Integrate automated testing into CI/CD pipelines
  • πŸ“Š Analyze production systems using Datadog and Splunk
  • β™Ώ Perform WCAG accessibility testing
  • ⚑ Conduct performance and scalability testing with k6 and LoadRunner
  • πŸ“¨ Validate event-driven architectures using Apache Kafka
  • 🧩 Test enterprise CMS platforms such as Adobe Experience Manager (AEM)
  • 🧠 Build AI-assisted QA workflows and autonomous testing agents
  • πŸ”— Explore MCP (Model Context Protocol) for AI-powered software testing

πŸš€ Current Focus

I'm currently focused on the intersection of:

Software Testing + AI + Developer Tools + Quality Engineering

Some of the things I'm building and exploring:

  • πŸ€– AI-powered QA agents
  • 🎭 Playwright automation with MCP
  • 🧠 LLM-assisted test generation
  • πŸ” AI-driven exploratory testing
  • πŸ› Automated defect investigation
  • πŸ“Š Intelligent QA reporting
  • πŸ”„ Agent-based CI/CD quality pipelines
  • β™Ώ Automated accessibility testing
  • ⚑ Performance testing with k6
  • πŸ”Œ API and distributed-system testing

One of my main goals is to build QA systems that behave less like traditional test scripts and more like engineering systems capable of exploring, reasoning, testing, investigating, and reporting on software quality.


🧠 My QA Philosophy

I believe automation is not the goal.

Quality is the goal. Automation is one of the tools that helps achieve it.

My approach is generally:

Requirements
     ↓
Risk Analysis
     ↓
Test Strategy
     ↓
Exploratory / Manual Testing
     ↓
Automation
     ↓
API / Database / Integration Validation
     ↓
CI/CD Quality Gates
     ↓
Observability
     ↓
Production Validation
     ↓
Continuous Improvement

I focus on identifying the right things to test, not simply increasing the number of automated tests.


πŸ› οΈ Technology Stack

Languages

TypeScript JavaScript Java C# Python SQL

Test Automation

Playwright Cypress Selenium Appium

API Testing

  • REST Assured
  • Karate DSL
  • Postman
  • Playwright APIRequestContext

Cloud & Distributed Systems

AWS

  • Amazon S3
  • AWS Lambda
  • DynamoDB
  • Cloud-based application testing

Messaging

  • Apache Kafka

CI/CD & DevOps

  • Azure DevOps
  • Jenkins
  • GitHub Actions
  • Docker

Observability

  • Datadog
  • Splunk

Performance

  • k6
  • LoadRunner

Accessibility

  • WCAG 2.2
  • Axe-core
  • BrowserStack

Enterprise Platforms

  • Adobe Experience Manager (AEM)
  • Looker Studio

🏒 Experience

🎯 Senior SDET β€” Princess Cruise Lines

Working within the Booking Engineering organization, focusing on critical customer-facing booking workflows.

Areas include:

  • Playwright / TypeScript automation
  • Booking and reservation workflows
  • AEM content validation
  • Accessibility testing
  • Mobile and cross-browser testing
  • Production release validation
  • Hotfix verification
  • Performance testing with k6
  • AI-assisted testing
  • Third-party integrations

πŸ’³ Senior SDET β€” Capital One

Worked within a financial services environment where the development organization did not previously have a dedicated QA team.

Key contributions included:

  • Establishing Quality Engineering practices
  • Defining testing strategies and quality gates
  • Building automation frameworks
  • UI, API, component, and integration testing
  • REST Assured and Karate DSL
  • Jenkins CI/CD integration
  • Splunk log analysis
  • Distributed system validation
  • Shift-left testing
  • Production defect investigation

The focus was not simply creating tests, but helping establish quality as part of the engineering lifecycle.


πŸ“± SDET β€” Insight Global / VPZone

Worked across mobile and backend enterprise applications.

Technologies and responsibilities included:

  • Java
  • Selenium
  • Appium
  • REST Assured
  • Jenkins
  • API testing
  • Mobile testing
  • Apache Kafka
  • Backend validation
  • Regression testing

πŸ“Š QA / Platform Engineer β€” Google / Looker Studio

Worked with analytics and cloud-based platforms with a focus on:

  • EL/ETL testing
  • Data validation
  • SQL
  • Looker Studio
  • Data integrity
  • Cloud platform validation
  • Datadog monitoring
  • Production troubleshooting

πŸš€ SDET β€” Sin Delantal & Interjet

Helped establish QA practices from the ground up across food delivery and airline platforms.

Responsibilities included:

  • Manual testing
  • Functional testing
  • Regression testing
  • Exploratory testing
  • API testing
  • Release validation
  • Defect management
  • QA process design
  • C# automation
  • Selenium
  • Azure DevOps
  • CI/CD

This experience taught me an important lesson:

Before automating a process, you need to understand the quality problem you're trying to solve.


πŸ€– AI + QA

One of my current areas of research is AI-powered software testing.

I've been experimenting with architectures where multiple specialized AI agents collaborate throughout the QA lifecycle.

For example:

                    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                    β”‚  Orchestrator β”‚
                    β””β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”˜
                            β”‚
          β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
          ↓                 ↓                 ↓
      Analyst            Explorer          Generator
          β”‚                 β”‚                 β”‚
          β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                            ↓
                         Runner
                            ↓
                      Investigator
                            ↓
                        Reporter

The idea is to create a QA pipeline that can:

  1. Understand application requirements
  2. Explore a live application
  3. Identify important user flows
  4. Generate test scenarios
  5. Execute tests
  6. Investigate failures
  7. Correlate evidence
  8. Identify defects
  9. Assign severity
  10. Generate a QA report and release recommendation

I'm particularly interested in combining:

LLMs + Playwright + MCP + CI/CD + QA Engineering


πŸ”¬ Projects

Some areas I'm currently building or researching:

πŸ€– AI QA Pipeline

An AI-driven QA ecosystem designed around specialized agents.

Potential capabilities:

  • Application exploration
  • Test generation
  • Playwright execution
  • API testing
  • Accessibility testing
  • Performance testing
  • Failure investigation
  • Defect classification
  • QA reporting
  • Historical QA memory

🎭 Playwright Automation

Building scalable Playwright frameworks using:

  • TypeScript
  • Fixtures
  • Page Objects
  • APIRequestContext
  • Network interception
  • Authentication state reuse
  • Parallel execution
  • Cross-browser testing
  • Trace Viewer
  • CI/CD

β™Ώ Accessibility Automation

Exploring automated accessibility testing using:

Playwright + Axe-core + WCAG 2.2

πŸ“Š ETL Testing

Building projects around:

  • Data extraction
  • Transformation validation
  • Data warehouse testing
  • SQL validation
  • Data quality
  • Business-rule validation

πŸŽ“ Background

I originally studied Communications and Electronics Engineering and later moved into software engineering.

That background still influences the way I approach software:

systems thinking + engineering + experimentation + automation

I enjoy understanding how systems work internally rather than treating them as black boxes.


🌎 From Mexico πŸ‡²πŸ‡½

I'm based in Mexico and interested in working with international engineering teams, particularly remote opportunities across:

  • πŸ‡²πŸ‡½ Mexico
  • πŸ‡ΊπŸ‡Έ United States
  • 🌎 LATAM

I'm especially interested in roles involving:

Senior SDET Β· Quality Engineer Β· QA Automation Engineer Β· Software Engineer in Test Β· Quality Engineering


πŸ“š Always Learning

Currently exploring:

  • Artificial Intelligence
  • LLMs
  • AI Agents
  • MCP
  • Playwright
  • TypeScript
  • Python
  • FastAPI
  • Rust
  • Cloud Architecture
  • AWS
  • Azure
  • Modern CI/CD
  • Distributed Systems
  • Software Architecture

πŸ“« Connect With Me

LinkedIn

TikTok

Instagram


πŸ’‘ "Quality is not something we test at the end. It's something we engineer throughout the lifecycle."

Pinned Loading

  1. qa-pipeline qa-pipeline Public

    JavaScript 6 9

  2. qa-framework-practice qa-framework-practice Public

    TypeScript