Embedded Files
Capstone Project (CSE 485 & CSE 486)
Capstone Project (CSE 485 & CSE 486)
Project Objective and Approach
Project Objective and Approach
The main objective of the project was to strengthen how test cases are stored, reviewed, and organized inside the platform. We focused on building features that were stable and usable in real engineering environments.
We followed a sprint based development process. Each cycle included planning, implementation, testing, sponsor feedback, and refinement. Features were built in small steps and tested using realistic data scenarios. A large part of the work involved making sure the frontend and backend communicated correctly and consistently.
My Contributions
My Contributions
I designed and implemented a secure private test plan ingestion workflow using a dedicated Google service account. Previously, customers had to make their Google Sheet test plans public in order for our system to access them. This created unnecessary exposure of sensitive data.
To solve this, I created a centralized Google service account and configured a dedicated QTM email identity. Customers now only need to share their test plan with that service account instead of making the file public. On the backend, I implemented the logic to authenticate using the service account credentials and securely fetch spreadsheet data through the Google Sheets API.
I built the ingestion pipeline that parses spreadsheet data, validates structure, maps columns to internal database fields, and handles inconsistent or missing data. I implemented this processing inside an AWS Lambda function to isolate the ingestion logic and allow it to run server side. The Lambda function handled authentication, data transformation, validation, and structured persistence into our database.
This required significant backend coding to ensure permission handling, schema mapping, error detection, and retry safety were correct. I added defensive validation to prevent malformed sheets from corrupting repository data. This architecture improved privacy, reduced manual configuration for customers, and made ingestion more secure and scalable.
In addition, I designed and implemented the team onboarding system. I connected backend APIs to handle team creation, membership management, invitation logic, and role assignment. On the frontend, I implemented forms, state management, and validation to guide companies through onboarding. I ensured proper API contract alignment and handled edge cases such as duplicate invites and partial failures.
I also worked on integration stability across frontend and backend layers. I resolved payload mismatches, standardized response schemas, and added structured error handling and loading states to protect the user experience during asynchronous operations.
Throughout development, I clarified technical requirements with the sponsor before implementation. This reduced rework and ensured architectural decisions aligned with real product needs.
The screenshot above shows the first step of the team onboarding flow I designed and implemented
What I Learned
What I Learned
This experience taught me how to build and improve a scalable full stack system inside a real team environment. I learned that small inconsistencies in data structures can create large visible failures. I learned to pay close attention to contracts between layers of the system.
I also developed a stronger understanding of how structured testing workflows support overall software quality. Behind every reliable digital platform, there are organized processes that most users never see. Working on QTM helped me appreciate how much effort goes into building stable foundations.
The sprint process also strengthened my discipline. Instead of trying to build everything at once, I learned to make steady progress through smaller deliverables and continuous feedback.
Connection to My Broader Focus
Connection to My Broader Focus
Much of modern life depends on digital systems functioning correctly. Platforms in healthcare, banking, education, and communication rely on strong testing practices. Improving how teams manage test cases supports stronger software quality overall.
My broader focus is on improving daily life through systems people can trust. Reliable infrastructure is part of that. When testing workflows are organized and dependable, the end systems people use every day become more stable and trustworthy. Contributing to QTM helped me understand how backend structure connects to real world trust.
Value to My Academic and Professional Goals
Value to My Academic and Professional Goals
This project strengthened both my technical depth and my systems thinking. It connected with other parts of my GCSP work by reinforcing responsibility in engineering. I began to see features not just as code to implement, but as parts of a larger ecosystem that affects real users.
As I move into my professional career, this experience gives me confidence working in full stack systems with real constraints, real collaboration, and
Artifact
Artifact
The team project poster presented at the end of the first semester is attached below. It summarizes the project background, objectives, system design, and early implementation results.
A link to the final project presentation video is also included. The video demonstrates key workflows and explains the system architecture and feature set.
Because this project was industry sponsored, detailed source code and internal documentation cannot be shared publicly.
Page updated
Report abuse