FAQ’s on Manual Testing-In Real Time

1. What is software testing?

Testing is the process of evaluating a system or system component by manual or automated means to verify that it satisfies specified requirements”.

 2. Importance of software testing?

1. To deliver a bug free application to the customer (Error free superior product)
2. To deliver more reliable S/w to customer (Quality Assurance to the client)
3. To reduce the maintenance cost to customer
4. Early finding defects which helps to reduce cost to fix those defects (cut-down cost)
5. When defects are removed quality improves.

3. Why do we need specialist tester?

1. Developers will not do systematic and complete testing.
2. A developer assumes few things to be working fine as they are owners of the work.

4. What is software Quality?

1. Quality from the customer view point is that the S/w should be fit for use and for producer point of view the S/w should meet customer requirement.
2. Factors affecting the quality:
3. Time
4. Cost/budget
5. Reliability

5. Explain Quality management process?

Quality management is process of preventing defects in the S/w process to ensure that there are no defects in the final product, the whole quality process is divided into two parts:

1)      Quality Assurance (QA)

2)      Quality Control (QC)

6. What is Quality Assurance?

1. It measures the quality of processes used to create a quality product.
2. It is an activity that is based on process where we measure each process, identify any weakness and suggest improvement. 

7. What is Quality Control?

1. It is an activity that is based on product where we measure the product, identify any weakness and improve the product.
2. QC is oriented towards detection of defects.

8. Explain objective of S/w tester?

1. The goal of a tester is to find bugs.
2. Find bugs as early as possible
3. Make sure those bugs should be fixed.

09. Explain Testing Limitations

1. We can only test against system requirements
2. May not detect errors in the requirements
3. Incomplete requirements may lead to inadequate or incorrect testing.
4. Exhaustive (total) testing is impossible in present scenario.
5. Time and Budget constrains normally require very carefully planning of the testing effort.
6. Test results are use to make business decisions for release dates.

10. Why Testing CANNOT Ensure Quality? Testing in itself cannot ensure the quality of software. All testing can do is give you a certain     level of assurance (confidence) in the software. On its own, the only thing that testing proves is that under specific controlled conditions, the software functioned as expected by the test cases executed.

11. What is SDLC?

SDLC: It is a process of developing a software project or product to fulfill the customer requirements within the specified cost and time.

15. Common problems in SDLC?

1. Poor Requirements:
2. Unrealistic schedule:
3. adequate testing:
4. Miscommunications:

16. Explain some of SDLC Models?

Based on the requirements and the needs of the customer there can be a specific model adopted in order to implement a S/w application

SDLC Models are:

1. Waterfall Model
2. Incremental Model
3. Prototype Model
4. Rapid Application Development (RAD) Model
5. Spiral Model
6. V-Model

17. What is Agile Testing model?

1. It is new Gen. SDLC Model.
2. Agile testing involves testing from the customer perspective as early as possible.
3. Testing early and often as code becomes available and stable enough from module/unit level testing.

18. Explain V-model? Advantage of V-model?

1. verification & validation. It is a suitable model for large scale companies to maintain testing process. This model defines co-existence relation between development process and testing process.
2. The difference between other models and this model is that it has provided testing the same weight-age as other S/w development activities.

19. Explain Verification?

1. In this process we say “Are we building the product right”?
2. It is performed by reviewing the SRS Document, Design Document, Code to find any mistakes.
3. It is consider as “Static” testing.
4. Reviews, Walkthrough and Inspection are the examples of Verification Techniques.

20. Explain Verification Techniques?

a. Peer Review: It is informal meeting where the author provides the document to any one person to identify any mistakes.

b. Walkthrough: Semi-informal meeting where the participants comes to the meeting and author gives the presentation. In this case author himself is the presenter for explaining the project requirement.

It is planned meeting characterized by team of 2- people, led by author

Objective is to make other participants familiarize with the material and find any mistakes.

c. Inspection:

•          Formal meeting characterized by individual preparation presentation prior to the   meeting

•          The meeting is led by the Moderator who assure that rules are been followed and review is effective. Inspector does review for the document been presented.

•          Presenter is the reader other than the author.

•          Recorder records the defect identified in the meeting.

21.Explain Validation process?

•          In this process we say “Are we build the right product?

•          It is the process of confirmation whether software meets customer requirements.

•          It is performed by executing the application to find any defect

•          It is consider as “DYNAMIC” testing or testing with execution of system.

•          Unit testing, Integration testing, system testing and Acceptance testing are the examples of validation techniques.

22. What is Coding, Testing, Debugging and Bug fixing?

23. What is White Box Testing?

1. It is based on knowledge of the internal logic of the application’s code.
2. Tests are based on coverage of code, statements, branches, paths, conditions & loops.
3. It is also called as Clear Box or Glass Box or Open Box or Structural Testing.
4. Explain disadvantages in WBT?
5. Testers should be skilled to understand the code and internal structure.

In case of code lengthy it would impossible to go through each statement to find the hidden errors

24. What is Black Box Testing?

1. Black box testing not based on any knowledge of internal design or code.
2. Tests are based on requirements & functionality.

25. What is Gray box testing?

1. This is just a combination of both black box and white box testing.  Tester should have the knowledge of both the internal and externals of the function.
2. Tester should have good knowledge of white box testing & complete knowledge of black box testing
3. Grey box testing is especially important with web & internet applications, because the internet is built around loosely integrated components that connect via relatively well-defined interfaces.

26. Explain levels of tests?

1. Unit testing
2.   Module testing
3. Integration testing
4. System testing
5. User acceptance testing

27.Explain Unit Testing?

1. It is code oriented testing.
2. Individual components are tested to ensure that they operate correctly. Each component is tested independently, without other system components.

28. Explain Module Testing?

A module is a collection of dependent components such as an object class, an abstract data type or some looser collection of procedures and functions.A module encapsulate related components so it can be tested without other system modules.

29. Explain Integration testing?

1. It is also called sub-system testing.
2. It is Design oriented.

This phase involves testing collections of modules, which have been integrated into sub-systems. Sub-systems may be independently designed and implemented. The most common problems, which arise in large software systems, are sub-systems interface mismatches. The sub-system test process should therefore concentrate on the detection of interface errors by rigorously exercising these interfaces.

30. Explain system testing?

The sub-systems are integrated to make up the entire system. The testing process is concerned with finding errors that result from unanticipated interactions between sub-systems and system components. It is also concerned with validating that the system meets its functional and non-functional requirements.