top of page

IMS Masonry QA Capstone – Automated Testing Showcase

This capstone project demonstrates my ability to plan, write, and run end-to-end automated tests using WebdriverIO, VSCode, and JIRA. I chose to test the IMS Masonry website—verifying key UI and functional elements like the navigation menu, contact form, project gallery, and footer—while incorporating both positive and negative testing scenarios. This project represents everything I’ve learned in MTECH’s QA program, built with a real-world mindset and professional structure.

Click above to see all test files, Page Object Models, and project structure  available on my GitHub. The repo includes commit history, test logic, and readme documentation.

🧪 Core Test Components

​

  • Navigation Bar: Hover behavior, link text, and correct navigation

  • Project Gallery: Image visibility and responsive layout checks

  • Contact Us Form: Field validation (positive & negative), submission success

  • Footer: Presence and accuracy of office hours, contact info, email links

  • Negative Testing: Empty form submission, incorrect email formats, missing required fields

Watch the Automated Test Suite in action, below...

This short video shows my complete test suite running in VSCode using WebdriverIO. It includes automated tests for navigation hover behavior, gallery image validation, footer content, and contact form functionality—all using the Page Object Model and dynamic selectors.

Tools Used

​

  • WebdriverIO

  • JavaScript

  • VSCode

  • GitHub

  • JIRA

  • Chrome DevTools

All code follows modern best practices: Page Object Model structure, dynamic selectors, minimal logic in spec files, and meaningful test separation.

Create Your First Project

Start adding your projects to your portfolio. Click on "Manage Projects" to get started

Test Planning with JIRA

I used JIRA to write and organize detailed test cases for every section of the site. Each case includes clear steps, expected results, and both positive and negative scenarios.

-What I learned

The most challenging part of this project was mastering the Page Object Model and keeping expectations out of my test files. I learned how to use dynamic selectors, reduce test redundancy, and think like a real tester—not just from a happy path perspective. This project taught me how to debug, write maintainable code, and apply QA theory to real-world sites.

I’m passionate about finding bugs, thinking outside the box, and delivering reliable test coverage. I've just finished the QA program at MTEC and actively looking for a role where I can bring this kind of creative, detail-oriented testing to a professional team.

Phone Number: 801-600-2213

​

2847 E 250 N Spanish Fork, UT 84660

bottom of page