1. Describe how drivers and stubs can be used in unit testing with diagram.

Drivers:
- Drivers are used for bottom-up integration testing approch.
- These are used for interact with external system and usually complex than stubs.

Stubs:
- Stubs are used for top-down integration testing.
- When needs to interact with external system then also stubs are used.

2. What is integration testing? Explain types of integration with diagram.

Integration testing:
Integration testing is a logical extension of unit testing.

Types of integration testing:

i. Non-incremental integration testing.
ii. Incremental integration testing.
iii. Top-down integration testing.
iv. Bottom-up integration testing.

i. Non-incremental integration testing

All the s/w units are assembled into entire program. This aassembly is then tested as a
whole from the beginning.

ii. Incremental integration testing

 The program is constructed and tested in small increments by adding a minimum
number of components at each interval.

iii. Top-down integration testing

The top-down approch of integration testing require the highest level module be test
and integrated first. Modules are integrated from the main module to the subordinate
modules.

iv. Bottom-up integration testing

The bottom-up approch requires the lowest-level units to be tested and integrated
first.

3. Describe bi-directional integration testing with diagram.

- The bi-directional integration testing combines both top-down and bottom-up

approaches together and forms final integration.
- This type of testing is also known as sandwitch testing.
- Initially modules are tested in sequence.
- Module A, B, C, D, E are tested with the help of stubs and drivers.
- Stubs will perform the role of missing module while driver will perform the role of
re-direction of request to other module.

Advantages:
i. Useful for very large projects.
ii. Itself a large system.

Disadvantages:
i. Can not be used for large projects.
ii. High Cost.

4. How to perform security testing? State element of security testing.

- Security testing is performed to verify if the application is secured or not because
unauthorized access are very comman issues.
- During security testing password cracking, unauthorized entry into the s/w, network
security are all taken into consideration.
 - It is done to check the security of a program.
- This testing might not be required in some cases.

Elements:
i. Test for unauthorised access to secure program.
ii. Restricted files should not be downloadable.
iii. Check sessions are automatically killed.
iv. On use of SSL certificates, website should re-direct to encrypted page.

5. Differentiate between alpha and beta testing.

Alpha Testing Beta Testing
1.Performed at the developer site. 1.Performed at the end user site.
2. Performed in controlled environment in 2. Performed in uncontrolled environment
developer presence. in developer absence.
3.Done during the implementation phase. 3.Done at the pre-release.
4.Conducted for specific customer. 4. Conducted for market requirements.

6. What is load and stress testing?

Load testing:

Stress testing:

7. Explain the alpha testing. State its limitations.

- It comes after system testing and invalue both BBT and WBT.
- It is performed at developer site.
- Alpha testing is considered as a form at internal acceptance testing in which user test
the s/w at developer site.
- On completion of alpha testing user report the error to s/w developer.

Objectives:
- To involve customer deep into process of development.
- To identify and resolve critical bugs and issues in s/w.

Limitations:
i. Limited scope.
 ii. Time consuming.
iii. Internal bias.
iv. High requirment.

8. Explain GUI testing.

- It is process of testing that detemines such as image, text, button to validate their
expected prformance as well as their function.
- By performing GUI testing the team can validate various graphical icon like check
box, dialog box, list etc.
- GUI testing is performed manually with a human tester.
- As well as automatically with use of a s/w program.
- There are two types of GUI testing
i. Manual based testing
ii. Automated based testing

i. Manual based testing

Under this approch, graphical screen are checked manually by testers.
ii. Automated based testing
Under this approach it uses s/w program to detect if your desktop application is
functionally correct or not.

9. What is test plan? List test planning activities.

Test plan:
Test plan is an important document for execution tracking and reporting the entire testing.

Activities:
i. Analyze the product.
ii. Develop test strategy.
iii. Define objective of testing
iv. Define test criteria.
v. Planning the resources
vi. Plan test environment.
vii. Schedule and cost.
viii. Test deliverables.

10. Explain test deliverables in details.

It usually include following information:
i. Scope: Priority levels of different phases during testing.
ii. Methodology: Person who is going to perform the testing and method the methods.
iii. Requirements: Specifies what kind of h/w, s/w, human resources, tools you need.
iv. Criteria for pass-fail: To determine pass or fail.
v. Schedule: Plan of scheduling.

11. List test case specifications.

12. Explain the test infrastructure component with diagram.

 Testing infrastructure has three components:
i. Required h/w infrastructure
- This is main component of testing infrastructure.
- Efficient, high as well as old configuration.

ii. Required s/w infrastructure:

- This is another component of testing infrastucture.
- Latest as well as previous s/w should be available for testing.

iii. Required automated teating tools infrastructure:

- This is most important component of testing infrastructure for automated testing.
- Different testing tools for different types of testing.

13. What is test deliverables and milestone? Explain any four test deliverables.
It usually include following information:
i. Scope: Priority levels of different phases during testing.
ii. Methodology: Person who is going to perform the testing and method the methods.
iii. Requirements: Specifies what kind of h/w, s/w, human resources, tools you need.
iv. Criteria for pass-fail: To determine pass or fail.
v. Schedule: Plan of scheduling.

14. Write 5 test cases to test sign-in form of Gmail account.

15. Describe test case specification of test process with example.

16. Which are different causes of software defect?

i. Lack of design experience.
ii. Lack of coding practice.
iii. Unrealistic time schedule for development.
iv. Multipe changes in the requirements.

17. Describe the requirement defect and coding defect in detail.

Requirement defect:
- Requirement defect arise in product, when one falls to understand what is required by
the customer.
 - These defects may be due to customer gap, where customer is unable to define his
requirements.
- Defects arised in early stage can be very difficult to remove in later phases.
- These types of defect usually caused by developer’s oversight.

Coding defect:
- The program crashes or produces wrong result, this may lead to the coding defect.
- This defect may arise because product is developed in wrong way.
- These types of defect usually caused by developer’s oversight.
- There are three types as;
i. Variable declaration defect
ii. Documentation defect
iii. Database related defect

18. Explain technique for finding defect.

i. Static techniques:
Testing that is done without physically execution of program or system.
For ex. Code review

ii. Dynamic testing:

Testing that is done with physically execution of program or system.
For ex. Execution of test cases

iii. Operational testing:

While using the final s/w product the defect is found and s/w is not working or falls.

19. What do you mean by defect impact?

Defect impact means degree of impact on the development of product or system. Once
the critical risks are identified, the financial impact of each rish should be estimated.

20. Explain defect classification.

21. What is defect management? Give defect classification in detail.

Defect management:
 The process of finding defect and reducing them at the lowest cost is called as defect
management.

Classification:
S/w defects are classified as;
i. Severity wise
ii. Probability wise
iii. Priority wise
iv. Work product wise
v. Type of error wise

i. Severity based
- Severity is defined as the affect of defect on the application.
- It is related to the development aspect of the product.
- It can be decided based on how bad is the defect for system
- Its status can give idea about the affect in the functionality due to defect.
ii. Probability based
- Defect visibility: Indicates the likelihood of a user encountering the defect.
- High: Encountered by all or almost all the user.
- Medium: Encountered by about 50% of the user.
- Low: Encountered by very few users of the feature.
iii. Priority based
- Priority is defined as the order in which the defects should be resolved.
- Its status is set based on the requirements of the users.
- The status is usually set by QA team.
- There are some classes as;
 Low
 Medium
 High
 Urgent
iv. Work product based
- SSD: Defect from System Study Document
- FSD: Defect from Functional Specification Document
- ASD: Defect from Architectural Design Document
- DDS: Defect from Detailed Design Document
v. Type of error based
- Comments
- Data error
- Database error
- Missing Design

22. Illustrate defect prevention process of defect fixing process with diagram.
 i. Identify critical risks
- The first step is preventing defects is to understand the critical risks.
- The best way to do this is to identify the types of defects that pose the largest area.
- These risk can vary from project to project.
- These risks might include:
 Missing a key requirement
 h/w maifunction
ii. Estimate expected impact
- Once the critical risk are identified, it is necessary to identify the financial impact
of the risk.
- This can be done by assessing the impact in dollars.
- The risk does become a problem combined with probability.
- The expected impact of a risk(E) is calculated as;
E=I*P
Where, I = Impact in dollars
P = Probability of risk becoming problem.
iii. Minimize expected impact
- The expected impact may be strongly affected so it is nessecary to minimize.
- It includes;
 Eliminate the risk
 Reduce the probability of a risk becoming a problem
 Reduce the impact if there is a problem

23. Explain defect life cycle to identity status of defect with proper labeled diagram.

24. Explain the defect template with its attributes.

i. Defect ID: Unique identifier.
ii. Defect name: Name of the defect.
iii. Project name: Identifies project name
iv. Module name: For which the defect is found.
v. Severity: Declared in test plan
vi. Priority:
vii. Title:
viii. Description:
ix. Reported by: Who found the defect.
x. Assigned to: The tester who is going to fix the defect.
xi. Signature:

25. What are the different points to be noted in reporting defect?

26. Describe any two limitations of manual testing

- Time consuming process:

Manual testing consumes much time because most of the test operations or test cases
are repeated again and again.
- Non consistent:
Manual testing process is not consistent as testing methos of automated testing.

27. What is automated testing?

28. Explain needs of automation testing.

 i. Using testing effectively:
Automation of testing processes allows machines to complete the operation more
effectivly.
ii. Reducing testing costs:
The cost of performing manual testing is much as compared to that the cost for
automated testing is less.
iii. Replacating testing across different platform
Automation allows the testing organization to perform cnsistent and repetable test.
iv. Greater application coverage:
Greater application test coverage also reduces the risk.
v. Results reporting:
Full featured automated testing system also produce convenint test reporting and
analysis.

29. Explain static and dynamic testing tools in detail.

30. What do you mean by software metrics? List any three types of metrics.
Software testing matric is defined as a quantitative measure that helps to estimate the
progress, quality and health of a s/w testing efforts.

Types:
i. Process metrics
ii. Product metrics
iii. Project metrics

31. Define metrics and measurement.

Metrics:
 Software testing matric is defined as a quantitative measure that helps to estimate the
progress, quality and health of a s/w testing efforts.

Measurment:
In general, Kilogram is metrics for measuring the attribute weight. Similarly in s/w ‘How
many issues are found in thousand lines of the code?’, here no. Of issues is one
measurement and no. Of lines of code is another measurement. Metrics is defined in these
two measurements.

32. Describe any four limitations of testing.

33. State various advantages and disadvantages of using manual testing tool.
Advantages:
i. It is cheaper
ii. It requires less time
iii. It allows tester to perform adhoc testing
iv. Tester does not need knowledge of automated testing tool.

Disadvantages:
i. Time consuming process
ii. Limited scope
iii. No batch testing
iv. Non consistent

34. Differentiate between manual testing and automation testing.

35. Explain the need of automation testing
36. Elaborate the advantages of using the test automation tools.
i. Reduction of repetitive work:
Repetative work is very boring if it if done manually.
ii. Greater consistency and repeatability:
A tool will exactly reproduce what it did before, so each time it is run result is
consistent.
iii. Objective assessment:
The assessment is more repeatable and consistently calculated.
iv. Ease of access to information about tests:
Special purpose tools give these features directly for the information they process.

37. Define metrics and measurement. Explain need of software measurement.

 Need:
i. Gain an understanding of processes, products, resources and environment.
ii. To evaluate in order to
iii. To predict in order to
iv. To improve in order to

38. State the different metrics types with its classification. Explain three types product
metrics.