1.

What is a Business design document ?

Answer: further extension to Business Requirement Document with more detail
with snapshots of UI Layer, Technical requirements, finer details of components
of pages, flow of information from page to page with graphics. Business design
document is used to produce code directly.

2. What is module?
Answer: a software component with a specific task. It can contain a number of
classes or packages or can be comprised of a single class/package.

3. What is a Build?

Answer: Build is a development activity where a complete system is compiled
and put together ,preferably configured with configuration management system,
so that a stable system is available at any time including all the latest changes.

4. What is Test Strategy? Clear na !!!!!

Answer: A test strategy is an outline that describes the testing portion of the
software development cycle. This includes the testing objective, methods of testing
new functions, total time and resources required for the project, and the testing
environment.

The test strategy describes how the product risks of the stakeholders are mitigated
at the test-level, which types of test are to be performed, and which entry and exit
criteria apply.

Written by test manager or lead, The test strategy is created based on development
design documents.

The following are some of the components that the Test Strategy includes:

1 Test Levels. 2 Roles and Responsibilities. 3 Environment Requirements. 4
Testing Tools. 5 Risks and Mitigation. 6 Test Schedule. 7 Regression Test
Approach. 8 Test Groups. 9 Test Priorities. 10 Test Status Collections and
Reporting. 11 Test Records Maintenance. 12 Requirements traceability matrix. 13
Test Summary

5. Are test strategy and test plan same kind of document ?

Answer: No. They are different documents. Test Plan is a document that collects and
organizes test cases by functional areas and/or types of testing in a form that can be
presented to the other teams and/or customer where as the Test Strategy is the
documented approach to testing. Test Plan is prepared by the tester whereas the
Test Strategy is prepared by the QA Manager or QA lead.
6. What is shakeout testing?

Answer: This test is basically carried out to check the networking facility, database
connectivity and the integration of modules.- done through configuration Item.

7. What is the difference between load testing and performance testing?

Answer: all load testing are performance testing, but all performance testing are not
load testing. Load testing-> single random scenario, Performance testing - >
multiple/all possible scenario.

8. What was the process of QA testing in your company where you worked for
the last time ?

Answer: Chapa maro re!

9. What is a Primary Key?

Answer: a unique Identifier for each of the row in a table.

10. What is a Foreign Key?

Answer: a primary key of one table used in another table to create relationship
between rows of the two table.

11. What is a Unique Key constrains ?

Answer: The UNIQUE constraint ensures that all values in a column are different. A
primary key automatically has the unique key constraints.

12. What is a Change control ?

Answer: Change control is a systematic approach to managing all changes made to
a product or system

13. What is backend testing?

Answer: It is a test to check whether the data displayed in the GUI front end report
format matches with the particular data in the original database.

14. How do you determine what to test ?

Answer: based on the risk, priority given from customers and test cases developed
according to test plan.


15. what do you do when you find a defect ?

Answer: recreate the defect, Attach a screenshot, log the defect.

16. what is the biggest bug you have ever found ?

Answer: james Buch er kioshk breake er golpo.

17. How to derive test scenarios and use cases ?

Answer: Test scenarios and use cases are derived from requirements documents.
Suppose a requirements called login. Different scenarios might be, wrong id-right
password, right id wrong password, right id and password. Etc.

18. is there any format for test cases ?

answer: project- name- release number- requirements reference test case number.

19. What are the two parts of test harnesses?

Answer: Test execution engine and test script respository.

20. What are the different matrixes that you can use ?

Answer: 1) Percentage of work done in test case preparation.
2) Percentage of work done in test environment preparation.
3) Test Case Execution ( test cases pass/failed run/not run)
4) Defect Info (defect density, defect found/fix, failure rate, retest results)
5) Test coverage and risk.
6) Subjective confidence
7) Date of milestones.
8) Costs of continuing testing.

21. What is parallel or audit testing?

Answer: the old system is used as a test oracle to check if the new system behaves
properly.

22. How do you create a test strategy?

Answer: The test strategy is a formal description of how a software product will be
tested. A test strategy is developed for all levels of testing, as required. The test team
analyzes the requirements, writes the test strategy and reviews the plan with the
project team. The test plan may include test cases, conditions, the test environment, a
list of related tasks, pass/fail criteria and risk assessment. Inputs for this process:
A description of the required hardware and software components, including test
tools. This information comes from the test environment, including test tool data.
A description of roles and responsibilities of the resources required for the test and
schedule constraints. This information comes from man-hours and schedules.
Testing methodology. This is based on known standards.
Functional and technical requirements of the application. This information comes
from requirements, change request, technical and functional design documents.
Requirements that the system can not provide, e.g. system limitations. Outputs for this
process:
An approved and signed off test strategy document, test plan, including test cases.
Testing issues requiring resolution. Usually this requires additional negotiation at the
project management level.

23. How do you create a test plan/design?

Answer: Test scenarios and/or cases are prepared by reviewing functional
requirements of the release and preparing logical groups of functions that can be
further broken into test procedures. Test procedures define test conditions, data to be
used for testing and expected results, including database updates, file outputs, report
results. Generally speaking
Test cases and scenarios are designed to represent both typical and unusual situations
that may occur in the application.
Test engineers define unit test requirements and unit test cases. Test engineers also
execute unit test cases.
It is the test team that, with assistance of developers and clients, develops test cases
and scenarios for integration and system testing.
Test scenarios are executed through the use of test procedures or scripts.
Test procedures or scripts define a series of steps necessary to perform one or more
test scenarios.
Test procedures or scripts include the specific data that will be used for testing the
process or transaction.
Test procedures or scripts may cover multiple test scenarios.
Test scripts are mapped back to the requirements and traceability matrices are used
to ensure each test is within scope.
Test data is captured and base lined, prior to testing. This data serves as the
foundation for unit and system testing and used to exercise system functionality in a
controlled environment.
Some output data is also base-lined for future comparison. Base-lined data is used to
support future application maintenance via regression testing.
A pretest meeting is held to assess the readiness of the application and the
environment and data to be tested. A test readiness document is created to indicate the
status of the entrance criteria of the release.
Inputs for this process:
Approved Test Strategy Document.
Test tools, or automated test tools, if applicable.
Previously developed scripts, if applicable.
Test documentation problems uncovered as a result of testing.
A good understanding of software complexity and module path coverage, derived from
general and detailed design documents, e.g. software design document, source code
and software complexity data.
Outputs for this process:
Approved documents of test scenarios, test cases, test conditions and test data.
Reports of software design issues, given to software developers for correction.

24. What is the difference between Priority and Severity?

Answer: Severity shows how badly the deviation affect other modules, builds or
release. Priority shows how quickly a bug should be fixed and deployed to live
environment.

25. Give example of low severity and high priority and vice versa incidents.

Answer:
High severity-low priority = a broken functionality happens occasionally, for
example, customers cannot perform functionality in old browsers. And the
number of customers in old browser is low.
High priority low severity = the logo or name is not shown on the web page,
atm machine is not showing the balance but everything is working fine at the
back end.
Low priority low severity = privacy info page takes a long time to load.
High priority high severity = the whole application is down or inaccessible
or inoperable.

26. What is the basis for test case review?

Answer: Requirements based, testing technique based, defects based.

27. How would you test a web application?

Answer: both functional and non functional tests.

28. What are server side scripting language and client side scripting language.

Answer: client side scripts: JavaScript, VBScript and server side scripts: Perl, JSP,
ASP.

29. What is the defect life cycle?

Answer: New, Assigned, Open, fixed, reopened/closed, confirmed.
30. what is testing scenario?

Answer:
Testing scenario: USER LOGIN.
Test condition: valid user should be able to login, invalid user should not be
able to login.
Test cases: test input, execution steps, execution post condition, expected
output.

31. What are the attributes of use case?

Answer: Description, objective, actor, pre-condition, post condition, data element
description, primary flow, alternative flow, and business rules.

32. What is testing policy and testing methodology?

Answer: Testing policy means all kinds of testing: functional, non functional, smoke,
sanity etc. Testing methodology means blacl-box, white-box, experience based etc.

33. When there is not sufficient time for testing, how would you test?

Answer: do the most important tests first , sanity testing, and smoke testing.

34. What is prototype methodology?

Answer: The Prototyping Model is a systems development method (SDM) in which
a prototype (an early approximation of a final system or product) is built, tested,
and then reworked as necessary until an acceptable prototype is finally achieved
from which the complete system or product can now be developed