What is Project 2045?
Project 2045 is a unified advertising platform designed to streamline the process of ad creation across multiple marketing channels. It eliminates the need for agencies to manually set up advertisements on each platform, significantly reducing effort and complexity.
Challenges Faced During QA
The most challenging phase of this project was Quality Assurance (QA), during which I faced multiple obstacles.As part of this project, I explored three different roles, which were very challenging, brainstorming,etc. I am listing below few of the parameters:
1. Writing JSON Files for API Requests – New role, Responsibility & New Learning
At the project’s start, I was responsible for writing JSON files for API requests. This required thorough research using each platform’s documentation to ensure compliance with:
- Standard data types
- Input/output (IO) types
- Path parameters & query parameters
Since each platform had its unique structure, where the process was a new learning but also it was time-consuming which required significant effort from an individual point of view.
2. Balancing the work role in API Testing, JSON Writing & Research
One of the biggest challenges was balancing multiple responsibilities:
- Writing JSON files
- Testing APIs
- Researching field structures
- Uploading files to GitHub
- Creating README documentation for each JSON
Due to the vast scope of the project and being an individual handling these tasks, I sometimes missed writing detailed test cases because R&D was time-consuming.
3. Inadequate Requirement Clarity and Inefficient Communication
A major obstacle was dealing with unclear requirements. Often, I had to rely on inputs from the Developer or Tech Lead to understand the expected behavior of a feature. Initially, my test reports simply stated that a feature was “working fine.” However, I later realized the importance of detailed communication—clearly specifying:
- What was tested
- How it was tested
- Any potential edge cases
- Due to time constraints was not able to maintain proper documentation
This approach significantly improved transparency and helped in better defect tracking.
4. Testing the Entire Flow After Every PR Merge
Each Pull Request (PR) merge had the potential to impact the entire application. This meant that for every update, I had to:
- Verify logs in New Relic
- Check the database (6-7 tables involved)
- Test functionality on all integrated platforms
Each end-to-end test cycle required 1-2 hours to complete, making regression testing a time-consuming yet essential process to verify system stability, detect potential issues, and ensure seamless functionality across all components.
5. Better Approach to test API-heavy projects.
Testing a project like Project 2045, which involves API integrations across multiple advertising platforms, requires a structured and scalable QA strategy. Here’s a better approach to testing such projects:
- Start testing at the unit level – Ensure each endpoint can handle all types of requests and return necessary errors instead of causing application failures.
- Integrate small units first – Verify data flow between connected APIs to understand how they interact. This helps in detecting issues early and ensures smooth data exchange.
- Ensure endpoint changes don’t break other parts – Perform regression testing to confirm that modifications in one API do not negatively impact the rest of the system.
- Collaborate early with developers – Define request/response formats and set clear acceptance criteria before development begins to avoid confusion and rework.
- Implement API automation testing – Use tools like Postman or Playwright to reduce manual effort, improve test accuracy, and generate detailed test reports.
- Maintain a clear test plan – A well-structured test plan helps track testing efforts, document test cases, and ensure coverage of all scenarios.
- Manage resources effectively – Avoid overloading a single team member with excessive tasks, as it can affect performance and slow down the overall project.
- Take ownership of responsibilities – Every stakeholder, from project managers to testers, should be accountable for their tasks to ensure smooth execution and timely delivery.
Key Learnings from Project 2045
Despite the challenges, this project provided me with valuable learning experiences:
- New Relic Software – Understanding how to monitor logs and system performance.
- Database Interactions – Deep diving into table structures and queries for debugging.
- Platform Knowledge – Gaining expertise in DV360, TTD, and XANDR.
- Client Management – Learning how to handle aggressive clients and manage expectations effectively.
Conclusion
Project 2045 has been a challenging yet rewarding journey. It not only strengthened my technical skills but also improved my ability to handle multiple responsibilities, communicate effectively, and adapt to evolving project requirements.
