Posted in Manual Testing

Why do defects have priority and severity?

Priority indicates how soon the bug should be fixed. Severity indicates the seriousness of the defect on the product functionality. More severe the defect is, higher the priority is given to ensure the defects are fixed as soon as possible to maintain the quality of the application.

Example: A bug that would damage data is more severe than something that is just annoying like say some functionality taking too long to load. Both should be fixed but those with higher negative impact should be fixed first. 

Posted in Manual Testing

Why is defect management process important in software development teams?

Defect management process is very useful to identify the defect of the software for the following reasons:

  1. Provide developers and other parties with feedback about the problem to enable identification, isolation and correction
  2. Provide test leaders means of tracking the quality of the system under test and the progress of the testing
  3. Provide ideas for test process improvement
  4. Find defects easily and at a very early stage of process because as soon as the defect is detected the cost of fixing it will be low
Posted in Manual Testing

Explain Requirement Traceability Matrix (RTM) in simple terms?

  1. RTM is mapping between test cases and customer requirements.
  2. It is used to track the requirements and to check the current project requirements are met.
  3. RTM is prepared before test case designing.  Requirements should be traceable from review activities.

Conclusion: The main purpose of Requirement Traceability Matrix is to see that all test cases are covered so that no functionality should miss while doing Software testing.

Posted in Manual Testing

What is the process to write a manual test case?

  1. Select a tool for writing a test case(Excel spreadsheet)
  2. The field’s needs to be included in test case template are Test Case ID, Test Case Name, Test Data, Test Steps, Expected results, Complexity, Test Environment (operating system and browsers), and Test Result.
  3. Test cases should be small, isolated and reusable.
  4. Test cases should be easy to understand and steps should be executed fast.
  5. They should independent with each other & fail/pass independently from one another.
  6. Fairly, each good test should have defined its expected result.
Posted in Manual Testing

What is the difference between Test Cases and Test Scenario?

A Test Case is defined as a set of actions executed to verify a particular feature or functionality of the software application. A Test Scenario is defined as any functionality that can be tested. It is also called Test Condition.  Test scenarios cover a wide range of possibilities. 

Test Scenario Test Cases
Check Login Functionality Test Case 1: Check results on entering valid User Id & Password Test Case 2: Check results on entering Invalid User ID & Password Test Case 3: Check response when a User ID is Empty & Login Button is pressed And many more.

Conclusion:  Test cases and Test Scenario are the documents used by the testers to ensure that the application meets the customer requirements. These are the most important documents that the testers prepare prior to testing. Even though the core objective of the documents is the same, there is a difference in their representation.