“Knowing yourself is the beginning of all wisdom.” – Aristotle
I’m Ahmed Gomaa, a Communication Engineering graduate and a Software Testing Engineer at Aquadic software solutions and currently a trainee at DEPI. A lifelong learner and naturally curious person, I’ve always been drawn to understanding how things work — especially myself. That self-awareness has helped me discover my strengths: attention to detail, persistence, and a drive to improve.
Today, I apply those strengths in the world of software quality assurance. I test, analyze, and improve software to make sure users get smooth, reliable experiences. Whether it’s manual testing, Requirement and design Analyss and validation, or preparing myself for automation, I’m focused on learning, growing, and adding real value.
I believe quality isn’t just about bug reports — it’s about building trust between users and technology. That’s why I do what I do.
You can download my CV as a PDF from my Google Drive.
You can find examples of the described skills in the Examples of my work section.
Foundational Knowledge
- Software Development Life Cycle (SDLC): A clear understanding of the entire software development process, from requirements to deployment and maintenance.
- Software Testing Life Cycle (STLC): Knowledge of the phases of testing, including planning, analysis, design, execution, and closure.
- Agile and Scrum Methodologies: Familiarity with modern development frameworks and how a QA tester fits into a collaborative, iterative team.
Test analysis & design
- Reviewing requirements and specifications: Carefully examining the functional and non-functional requirements, design documents, and user stories.
- dentifying test conditions: Breaking down the requirements into individual, testable conditions.
- Evaluating testability: Assessing whether the requirements are clear, unambiguous, and can actually be tested. If a requirement is vague, i seek clarification from the development team or product owner.
- Prioritizing test conditions: Ranking the identified test conditions based on their risk, importance, and complexity.
Testing Techniques & Types
- Test Case Design: The ability to write clear, concise, and effective test cases from requirements or user stories.
- Test Design Techniques: Proficiency in techniques such as Equivalence Partitioning, Boundary Value Analysis, Decision Table Testing, and State Transition Testing to create comprehensive test scenarios.
- Functional Testing: Verifying that a software system performs as per the functional requirements.
- Regression Testing: A core manual testing skill, ensuring that new code changes have not negatively impacted existing functionality.
- Non-Functional Testing: Basic knowledge of performance, usability, and security testing.
- Cross-Browser and Cross-Platform Testing: The ability to test applications across different browsers (Chrome, Firefox, Safari) and operating systems (Windows, macOS, mobile platforms).
- Exploratory Testing: The skill of performing unstructured, unscripted testing to discover unexpected issues and gain a deeper understanding of the system
Google Sheet
- Have great Experience in executing, and manage test cases and test suites thorought it.
Jira
- know how to create bug reports
- able to create projects and track their progress
Trello
- Created and maintained a defect tracking workflow in Trello, using cards to log bugs, assign them to developers, and monitor their status from 'To-Do' to 'Done with a clear title and describtive bug reports
- Collaborated with the development team on Trello boards to prioritize bug fixes and provide real-time updates on bug status
I have Worked on more than 15 Application (Mobile - web - Dashboard) 2 Examples of my work
-
Test cases in Google Sheets For a car care application in the UAE which have 4 platform (Mobile app - website - Driver app - POS WebAPP ) (https://drive.google.com/file/d/1Mhiu8QEbU1JAai26SECLSXN8mK6TrB4z/view?usp=drive_link)
-
Test cases in Google Sheets For AVE A customizable type van cars services (https://drive.google.com/file/d/1BBH5K1TgXFwcxFumhYR6s2fOAv5OlQLr/view?usp=drive_link)
- Bug #1. Check the screenshot of the bug report in Trello.