Mark Johnson | QA Engineer QA Engineer portfolio

Quality First

Mark Johnson

QA Engineer

QA Engineer focused on web testing, API validation, bug reporting, and test documentation.

I help teams improve release quality through structured testing, clear communication, and practical quality analysis.

View My QA Projects Contact Me

Core Strengths

Key skills overview

A recruiter should be able to scan this section and see practical QA coverage, not just tool names.

Web Testing

Functional and responsive validation

Validate key user flows across browsers, breakpoints, and device classes with clear evidence and reproducible findings.

API Testing

CRUD scenarios in Postman

Design chained multi-step API scenarios with environment variables, collection variables, and response assertions.

Documentation

Traceable, actionable artifacts

Create test cases, checklists, bug reports, and summary reports that support release decisions and team alignment.

Analysis

Requirement and mockup review

Identify ambiguity, contradictions, missing acceptance criteria, and UI inconsistencies before defects reach production.

Recruiter Fit

Why I am a strong fit for this QA role

This content is written to address the hiring manager’s question: can this candidate contribute to product quality from planning through reporting?

Structured testing mindset

I break features into clear scopes, risks, and measurable checks so testing remains systematic instead of ad hoc.

Balanced technical understanding

I use HTML, CSS, browser tools, SQL basics, and client-server knowledge to investigate issues faster and communicate root causes clearly.

Reliable communication

I work comfortably with developers, PMs, and designers by reporting what matters, asking precise questions, and documenting impact.

Featured Work

Featured QA projects

Use the custom post type to manage projects per subsite. If no projects exist yet, the template shows implementation-ready examples.

Web Testing Project

E-commerce checkout validation

Responsive UI and cross-browser testing of catalog, cart, checkout, and payment confirmation flows.

  • Responsive testing
  • Cross-browser testing
  • Regression checks
API Testing Project

REST API CRUD workflow in Postman

Multi-step scenario with token handling, related entities, response validation, and negative-path checks.

  • CRUD operations
  • Chained requests
  • Assertions
Documentation Project

Test documentation package

Test plan, checklist, detailed test cases, and summary report prepared for release readiness review.

  • Test plan
  • Checklist
  • Summary report

Tools

Testing tools and technologies

Keep this section short on the homepage and link deeper details to the Tools page.

Postman

API collections, variables, assertions, and scenario chaining.

TestRail

Structured test case management and execution tracking.

Chrome DevTools

UI inspection, responsive checks, network diagnostics.

MySQL / SQL

Data verification, query-based validation, state checks.

Testing Mindset

My testing process

  • 1. ClarifyReview requirements, mockups, edge cases, and risks
  • 2. DesignChoose coverage using EP, BVA, decision tables, and error guessing
  • 3. ExecuteRun structured UI, API, database, and regression checks
  • 4. ReportDocument defects with evidence, impact, and reproduction steps

Recommendations

Testimonials placeholder

“Reliable in finding edge cases early, documenting issues clearly, and keeping quality visible across the team.”

“Strong attention to detail and good judgment about what should block a release versus what should be monitored.”

Read more about my QA approach

Artifacts

Examples of QA documentation

Recruiters often respond well to visible artifacts because they show working style, not just claims.

Test case set

Clear preconditions, steps, expected results, and coverage notes.

Bug report sample

Reproducible issue record with evidence, severity, actual result, and expected result.

Requirement review notes

Ambiguities, contradictions, and missing scenarios captured before implementation.

Contact

Open to QA Engineer opportunities

Open to QA Engineer opportunities involving web testing, API testing, quality analysis, and test documentation.

mark@example.com LinkedIn GitHub Telegram

How I Work

What I validate in real projects

  • Functional flows and edge cases
  • Responsive behavior and layout consistency
  • Cross-browser compatibility
  • API contracts and CRUD paths
  • Data persistence and UI-data alignment
  • Release-risk summary for stakeholders