πŸ§ͺ QA Portfolio β€’ Testing Services β€’ Future QA Education Brand

CaraQAway

I test with purpose, document with clarity, and help teams release with confidence. CaraQAway is my QA portfolio, my business foundation, and the start of a future space built to motivate, educate, and help others grow in software testing.

βœ… Current Freelance QA Tester πŸ€– Playwright + TypeScript 🐞 Bug Reports + Test Cases πŸ“ Chicago β€’ Remote Ready
QA

Quality Command Center

Where test cases, bugs, evidence, and automation come together.

20Testing Methods
3Bug Jams
7Week Externship
Live QA Workflow

Bug Reports β€’ Test Cases β€’ Automation

Focused testing that turns risk into clear, actionable feedback.

Functional FlowValidated
Critical BugDocumented
Security CheckAutomated

QA Mindset

How I Think as a Tester

My work is guided by user focus, clear reporting, consistency, and follow-through.

β€œTest what matters most to the user.”

β€œClear bug reports move teams faster.”

β€œIf it can break, find it early.”

β€œConsistency in testing builds release confidence.”

Focus

Testing With Purpose

In QA, focus means isolating behavior and validating what matters. Every test should answer one clear question: what am I proving right now?

Follow Through

Retest. Verify. Confirm.

Finding a bug is not the finish line. Real QA value comes from retesting, verifying fixes, and confirming stability before release.

What QA Means to Me

QA protects the user experience.

QA is how I make sure products work the way users expect. I validate flows, identify risk, document issues clearly, and help turn assumptions into verified outcomes.

πŸ•’ Shift-Left Testing

I begin early by reviewing requirements and planning coverage upfront.

πŸ”Ί Automation Awareness

I understand where automation fits and where manual testing adds value.

πŸ” Exploratory Testing

I explore beyond scripts to uncover real-world issues and edge cases.

🚧 Quality Gates

I support testing processes that prevent unstable builds from shipping.

Testing Methods

Core Testing Types

Tap or hover a tile to flip it and see what the method means and how I would use it in real testing.

πŸ§ͺ

Functional Testing

Functional TestingI test features against requirements and real user behavior to confirm the product does what it should do.
πŸ”

Regression Testing

Regression TestingI retest important flows after updates to make sure a fix or new feature did not break something that already worked.
🚬

Smoke Testing

Smoke TestingI quickly check the main flows first, like login or checkout, before spending time on deeper testing.
βœ…

Sanity Testing

Sanity TestingI focus on the specific change or fix to confirm it works before expanding into wider testing.
🧭

Exploratory Testing

Exploratory TestingI explore the app like a real user, follow my curiosity, and look for issues scripted cases may miss.
πŸ“±

Mobile Testing

Mobile TestingI test on real devices for layout, taps, scrolling, device behavior, app version, OS version, and network conditions.
🌐

Web Testing

Web TestingI check forms, links, page flow, responsiveness, browser behavior, and whether the site is clear and usable.
πŸ”Œ

API Testing

API TestingI would verify requests, responses, status codes, and returned data to make sure the backend supports the user flow correctly.
🧾

UI Testing

UI TestingI check buttons, text, spacing, menus, forms, colors, and layout so the interface looks right and works clearly.
πŸ‘€

UX Testing

UX TestingI test how the product feels to use and call out anything confusing, frustrating, or hard for the user to complete.
β™Ώ

Accessibility Testing

Accessibility TestingI would check keyboard navigation, labels, contrast, readable text, and whether users with different needs can complete the flow.
🌍

Localization Testing

Localization TestingI check language, dates, currency, location behavior, and regional details so the app makes sense for that audience.
🌎

Compatibility Testing

Compatibility TestingI compare behavior across devices, browsers, operating systems, and screen sizes to catch differences users may see.
⚑

Performance Testing

Performance TestingI watch for slow loading, lag, freezing, delayed buttons, or anything that makes the app feel unstable.
πŸ”’

Security Testing

Security TestingI look for risky behavior like missing brute force protection, weak validation, exposed data, or unsafe access patterns.
πŸ›’

End-to-End Testing

End-to-End TestingI test the full journey from start to finish, such as login to task completion, to confirm the full flow works.
πŸ”—

Integration Testing

Integration TestingI check that connected parts of the system work together, like front-end actions matching backend results.
πŸ“Š

Data Validation

Data Validation TestingI confirm the data entered, saved, displayed, or returned is accurate and consistent across the flow.
🧯

Negative Testing

Negative TestingI intentionally use invalid inputs or unexpected actions to confirm the app handles errors clearly and safely.
πŸ“

Acceptance Testing

Acceptance TestingI confirm the product meets the business goal and is ready for users, not just technically working.

Work Samples

QA Deliverables & Project Proof

Hands-on work including bug reports, test cases, exploratory testing, recordings, and automation validation.

Featured QA Project

Login Functionality Testing

Manual and exploratory testing focused on login validation, input handling, error behavior, and user experience.

Manual TestingExploratoryBug ReportTest CasesSecurity Check
πŸžπŸ”

πŸ§ͺ Bug Jam 1

Hands-on testing work including bug reporting, test execution, and visual evidence.

πŸ“‹βœ…

πŸ§ͺ Bug Jam 2

Structured QA work showing test case coverage, issue documentation, and testing decisions.

πŸŽ₯🧭

πŸ§ͺ Bug Jam 3

Visual testing walkthrough with findings, observations, and user-flow validation.

Automation Showcase

Login Security Testing

Automation proves I can go beyond finding issues and build repeatable checks for validation.

Playwright β€’ TypeScript β€’ Security-Aware QA

[Login][Security] No Brute Force Protection Detected

I wrote an automated test to check whether repeated invalid login attempts trigger protection such as account lockout, rate limiting, CAPTCHA, or another verification challenge.

What the test validates

  • Repeated invalid login attempts
  • System response after multiple failures
  • Absence of brute force protection
  • Repeatability of the security finding

Why it matters

Missing brute force protection can expose an application to repeated credential attempts. This shows my ability to test functionality, risk, and security behavior through automation.

Automation Code (Playwright + TypeScript)

// Test: No brute force protection on login
// Severity: High - Security Vulnerability

import { test, expect } from '@playwright/test';

const loginUrl = 'http://the-internet.herokuapp.com/login';
const validUsername = 'tomsmith';
const invalidPassword = 'WrongPass123';

test('System should trigger protection after repeated failed logins', async ({ page }) => {
  await page.goto(loginUrl);

  for (let i = 0; i < 15; i++) {
    await page.fill('#username', validUsername);
    await page.fill('#password', invalidPassword);
    await page.click('button[type="submit"]');
    await page.waitForTimeout(300);

    const error = await page.locator('#flash');
    await expect(error).toBeVisible();
  }

  const finalMessage = await page.locator('#flash').textContent();
  expect(finalMessage).toContain('Your username is invalid!');
});
        

Experience

QA Work, Training & Growth

My background combines my current freelance QA work, formal QA training, and a 7-week automation externship.

Current Role

Testlio

Freelance QA tester actively executing real test runs, validating builds, reporting bugs, and collaborating with test leads across mobile and web environments.

Manual QAMobile TestingBug ReportingTest Execution
Automation Externship

Runestone Academy

Completed a 7-week automation externship focused on writing and executing automated tests using Playwright and TypeScript.

PlaywrightTypeScriptAutomationGitHub
QA Training

TripleTen QA Engineering

Completed QA Engineering training covering manual testing, bug reporting, test case design, API testing, SQL basics, and automation concepts.

Manual QAAPI TestingSQLTest Design
Cara Cross, QA tester and founder of CaraQAway
πŸ”

About Cara

Add your About Cara image at about-me.png

About Cara

Building a QA path with purpose.

I am a QA professional building real experience through freelance testing, project work, automation practice, and continuous learning. CaraQAway is more than a portfolio β€” it is the start of my QA business and future QA school.

My goal is to help companies improve product quality while also creating a space that motivates and educates new testers coming behind me.

Contact & Feedback

Let’s connect.

I’m open to QA opportunities, contract work, collaboration, and feedback on my portfolio.

Email:

Location: Chicago | Open to remote, contract, freelance, and QA collaboration opportunities.

Manual QA

Test execution, bug reports, test cases, regression checks, and exploratory testing.

Automation Support

Playwright and TypeScript test coverage for repeatable validation and bug checks.

Portfolio Feedback

Open to feedback, collaboration, and future QA education partnerships.