What You Will Learn:

• The definition of Quality Assurance (QA) Engineering, its benefits, roles, and major responsibilities.
• A comprehensive classification of software testing methods based on various categories, including execution type, purpose, scope/level, system knowledge (black-box, white-box, grey-box), and common test design techniques such as boundary value analysis and decision table testing.
• The key differences between the two common software development models: Waterfall and Agile. Testing stages occur in the former model (Waterfall) only after the development phase is completed, which means that identifying and fixing any errors at this stage can be time-consuming and costly. In contrast, Agile follows an iterative approach, where the testing phase is repeated continuously throughout the development cycle. In other words, the risk of errors and rework is significantly lower in Agile compared to the Waterfall model.
• The differences between test documentation types in manual software testing: test plan, test scenarios, test case, test execution report, and defect report.
• The methods of test documentation in automated software testing, including the main elements: test script, assertion, locator, test automation framework, page object model, and behavior-driven development, as well as the most commonly used automation tools.

Who should join?

Designed for IT engineering professionals and university graduates with a solid background in QA, IT, or technical development. Participants will learn the key concepts of Quality Assurance Engineering, explore common QA terms and tools relevant to the job market, and gain practical experience in writing test cases both manually and through automation.

About the Course:

Learn from Instructor Wessam-Juby is a Quality Assurance and Automation Engineer (SDET) with over 5 years of hands-on experience in building automation frameworks and leading QA teams across web, mobile, API, and desktop applications. Throughout his career, he has collaborated with international companies in the UAE, Italy, Germany, and Syria, delivering high-quality software solutions. He has led QA teams, built automation solutions from scratch, and participated in large-scale projects used across Europe and the Middle East, ranging from ERP systems and delivery applications to enterprise-level accounting platforms and AI-powered invoice processing systems. He possesses strong expertise in delivering high-quality software products through meticulous test planning, execution, and effective collaboration with cross-functional teams.

Learn the definition of Quality Assurance (QA); a process that prevents the occurrence of bugs in software development and ensures that the final product meets all requirements criteria. QA plays a vital role in cost efficiency, customer satisfaction, and security assurance. Each organization assigns various responsibilities to QA engineers depending on its structure and objectives. It is important to note that a QA engineer is an integral part of the software development team, not merely a tester.

Explore the main responsibilities, including:

1. Requirement analysis.
2. Test planning and strategy.
3. Test case design and execution.
4. Bug reporting and tracking.
5. Automation.
6. Regression testing.
7. Reporting.

Learn the Classification of Software Testing Based on Different Types:

1. Based on Execution: Manual and Automated Testing.

2. Based on Purpose: Functional and Non-Functional Testing.

3. Based on Scope or Level: Unit, Integration, System, and Acceptance Testing.

Explore the difference between Manual and Automated Testing:

• Manual testing involves human testers who execute test cases step by step to identify bugs and verify functionality. It is best suited for cases that require human experience, intuition, or exploratory testing that automation cannot replicate.
• Automated testing, on the other hand, relies on specialized tools and scripts to execute predefined test cases automatically. It is ideal for long, repetitive, and standardized tests.

Explore the difference between Functional and Non-Functional Testing:

• Functional testing focuses on logic flow, verifying that the software’s features and functions work correctly according to the specified requirements.
• Non-functional testing ensures that the secondary aspects of the software, such as performance, reliability, scalability, and usability, meet the expected standards.

Learn how to measure the quality of the provided software using common metrics,

• Defect Density.
• Test Coverage.
• Defect Leakage.
• Performance.
• Security.

Explore ecosystem tools used in both manual and automated testing to manage, organize, and track the testing process.

• Bug Tracking.
• Test Management tools.
• Collaboration and Documentation tools.
• A test environment.

At the end of the session, you will work with some examples to understand the concept of writing and executing test cases both manually and automatically.