Manual Testing Course in Ahmedabad

Smoke testing is a quick initial test to check if the major functionalities of an application are working. It ensures the build is stable enough for further testing.

Sanity testing verifies that specific functionality or bug fixes work after minor changes. It is narrow in scope and conducted before deeper regression testing.

Regression testing ensures that new code changes have not affected existing functionality. It’s repeated after every update or bug fix to maintain software stability.

Severity indicates the impact of a defect on the application, while priority reflects how soon it should be fixed. A high-severity issue may not always be high priority.

BVA is a test design technique that focuses on values at the edges of input ranges. Testing these values helps uncover common input-related errors.

Equivalence partitioning divides input data into valid and invalid sets where each set represents similar behavior. One test case from each group is enough for coverage.

White box testing checks internal code logic and paths, while black box testing validates external behavior without knowledge of the code structure.

UAT is the final testing phase where end-users verify the software meets their business needs. It ensures readiness for production use.

Ad-hoc testing is informal and unstructured, performed without planning or documentation. It helps discover unexpected issues through random testing.

Functional testing validates the features and operations of the software based on requirements, such as login, search, or payment functionality. Non-functional testing assesses aspects like performance, usability, and reliability that affect user experience.

I ensure complete coverage by mapping test cases to requirements using a traceability matrix. I also conduct peer reviews, consider boundary and edge cases, and validate both positive and negative scenarios for thorough testing.

A test closure report is a formal document summarizing all testing activities. It includes metrics like test case execution, defect status, coverage reports, and lessons learned. It helps stakeholders assess testing effectiveness and project readiness.

I maintain flexible and modular test cases to adapt to changes quickly. Communication with developers and regular sync-ups ensure I stay updated. I also maintain a changelog and revise affected test cases promptly.

Smoke testing checks the basic functionality of an application after a new build to ensure it’s stable for further testing. Sanity testing is a focused check to verify specific functionality after bug fixes or minor changes.

Test data is crucial for simulating real-world scenarios during testing. It helps validate input fields, data processing, and output accuracy. Proper test data ensures that the application behaves correctly under various conditions.

Defects are logged in a tracking tool like Jira or Bugzilla with details such as steps to reproduce, screenshots, severity, priority, and environment. A well-documented bug report helps developers resolve issues efficiently.

Severity is based on the impact on application functionality—critical, major, or minor. Priority is set according to how urgently the defect needs fixing. High-severity and high-priority bugs are addressed first.

Compatibility testing ensures that the application works as expected across different browsers, devices, operating systems, and network environments. It helps identify UI or functional discrepancies due to platform variations.