βTest what matters most to the user.β
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.
Quality Command Center
Where test cases, bugs, evidence, and automation come together.
Bug Reports β’ Test Cases β’ Automation
Focused testing that turns risk into clear, actionable feedback.
QA Mindset
How I Think as a Tester
My work is guided by user focus, clear reporting, consistency, and follow-through.
βClear bug reports move teams faster.β
βIf it can break, find it early.β
βConsistency in testing builds release confidence.β
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?
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
Regression Testing
Smoke Testing
Sanity Testing
Exploratory Testing
Mobile Testing
Web Testing
API Testing
UI Testing
UX Testing
Accessibility Testing
Localization Testing
Compatibility Testing
Performance Testing
Security Testing
End-to-End Testing
Integration Testing
Data Validation
Negative Testing
Acceptance Testing
Work Samples
QA Deliverables & Project Proof
Hands-on work including bug reports, test cases, exploratory testing, recordings, and automation validation.
Login Functionality Testing
Manual and exploratory testing focused on login validation, input handling, error behavior, and user experience.
π§ͺ 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.
Featured Bug
Real Bug Report Breakdown
This sample shows how I document bugs with clear steps, expected results, actual results, severity, and QA insight.
[Login][Username Field] Input Cleared After Failed Submission
- Environment
- Edge browser, Windows 11, desktop web application.
- Steps to Reproduce
-
- Navigate to the login page
- Enter an overlength username (e.g., 150 characters)
- Enter a valid password
- Click the Login button
- Observe the username field after submission
- Expected Result
- The username input should remain in the field so the user can edit and correct it.
- Actual Result
- The system clears the entire username field after submission, forcing the user to re-enter the data.
- QA Insight
- Clearing input after a failed login creates friction. Preserving input improves usability and supports faster correction.
What this shows
Edge-case thinking, clear reproduction steps, usability awareness, and actionable feedback.
Retest focus
After a fix, I would verify the username remains editable after failed submission and confirm the error message still displays correctly.
Automation Showcase
Login Security Testing
Automation proves I can go beyond finding issues and build repeatable checks for validation.
[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.
Testlio
Freelance QA tester actively executing real test runs, validating builds, reporting bugs, and collaborating with test leads across mobile and web environments.
Runestone Academy
Completed a 7-week automation externship focused on writing and executing automated tests using Playwright and TypeScript.
TripleTen QA Engineering
Completed QA Engineering training covering manual testing, bug reporting, test case design, API testing, SQL basics, and automation concepts.
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: christina34mea@gmail.com
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.