66 QA interview questions and answers(Part 6)

Q51. What is the role of Bug Tracking System?

The Bug Tracking System role is discussed below:
  • Testers and developers can know the status of the bug at every stage.
  • Changes to the Status will be available to all team members.
  • Developers and Testers can easily interact with bugs.
  • Repetition of bugs will be avoided.
  • Easy to distribute the bug among the developer.
  • It will act as a centralized one for defects.

Q52. How do you prioritize testing tasks within a project?

Test Process are execute in step by step. We cannot skip any of the process defined. Following is the Test Process which are in terms of their priority:
1. Preparation of Test Plan.
2. Preparation of Test Cases.
3. Execution of the Test Cases.

4. Defect report and tracking.
5. Test Report Summary.

Q54 Describe Bottom-Up and Top-Down approach in Testing.

Bottom Up Approach:
  • The bottom up approach testing approach is carried out with the help of the test driver. The test driver calls a component to be tested.
  • The modules in the lower level of call hierarchy are tested independently. Then the next level modules are tested that call previously tested modules. This is done repeatedly until all the modules are included in the testing.
  • Bottom up testing stops when the top module in the call hierarchy is tested with all lower call hierarchy modules.
    Top Down Approach:
  • the top down approach is carried out with the help of the test stub. Test stub are the dummy programs. The Stub is called from the software component to be tested.
  • Tests top layer of controlling subsystem first. Then combine modules that are called by the tested modules and test resulted collection of modules.
  • Do this until all the modules are combined and tested.

Q55. What methodologies do you used to develop test cases?

For developing the test cases we use following strategies:
  • Error Guessing: The tester has to guess what fault might occur and to design the tests to represent them.
  • Equivalence Class Partitioning: The input domain data is divided into different equivalence data classes; take few valid values with 2 invalid values. This is used to reduce the total number of test cases to a finite set of testable test cases.
  • Boundary value analysis: Boundary value analysis testing technique is used to identify errors at boundaries rather than finding those exist in center of input domain. Boundary value analysis is a next part of Equivalence.

Q56. What are the differences between test strategy and test plan?

The differences between these two are described below:
  • Test plan is dynamic where as test strategy is static.
  • Test plan is prepared by the Test Lead where as Test Strategy is prepared by the company management.
  • Test strategy defines: methods and coverage criteria to be covered test completion criteria, prioritization of the test where as Test plan is a document describing the scope, approach, resources and schedule of intended test activities.
  • Test Strategy is a high level description of the test levels to be performed where as Test plan is written record of the test strategy and resource planning.

Post a Comment