Latest Software Testing Interview Questions

1. What’ is Software Testing?

A set of activities conducted with the intent of finding errors in software.

2.What is Acceptance Testing?

Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.

3. What is Accessibility Testing?

Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

4. What is Ad Hoc Testing?

A testing phase where the tester tries to ‘break’ the system by randomly trying the system’s functionality.

5. What is Application Programming Interface (API)?

A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.

6. What is Backus-Naur Form?

A metalanguage used to formally describe the syntax of a language.

7. What is Beta Testing?

Testing of a release of a software product conducted by customers.

8. What is Application Binary Interface (ABI)?

A specification defining requirements for portability of applications in binary forms across different system platforms and environments.

9. What is Binary Portability Testing?

Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

10. What is Black Box Testing?

Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.

11. What is Bottom Up Testing?

An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

12. What is Boundary Testing?

Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

13. What is the difference between verification and validation?

Verification is a review without actually executing the process while validation is checking the product with actual execution. For instance, code review and syntax check is verification while actually running the product and checking the results is validation.

14. What is Bug?

A fault in a program which causes the program to perform in an unintended or unanticipated manner.

15. What is Defect?

If software misses some feature or function from what is there in requirement it is called as defect.

16. What is Branch Testing?

Testing in which all branches in the program source code are tested at least once.

17. What is Breadth Testing?

A test suite that exercises the full functionality of a product but does not test features in detail.

18. What is Alpha Testing ?

The Alpha Testing is conducted at the developer sites and in a controlled environment by the end user of the software.

19. What is Beta Testing ?

Testing the application after the installation at the client place.

20. What is Component Testing ?

Testing of individual software components (Unit Testing).

21. What is End-to-End testing ?

Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

22. What is CAST?

Computer Aided Software Testing.

23. What is CMM?

The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

24. What is Cause Effect Graph?

A graphical representation of inputs and the associated outputs effects which can be used to design test cases.

25. What is Coding?

The generation of source code.

26. What is Compatibility Testing?

Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.

27. What is Cyclomatic Complexity?

A measure of the logical complexity of an algorithm, used in white-box testing.

28. What is Debugging?

The process of finding and removing the causes of software failures.

29. What is Dependency Testing?

Examines an application’s requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.

30. What are the different Ways of doing Black Box testing?

There are five methodologies most frequently used:

A)Top down according to budget
B)WBS (Work Breakdown Structure)
C)Guess and gut feeling
D)Early project data
E)TPA (Test Point Analysis)

31 What’ is Database testing?

In database testing, we can check the integrity of database field values.

32. How many types of testing?

There are two types of testing-

Functional- Black Box Testing
Structural- white Box Testing

33. What does the mclabe cyclomatic complexity of a program determine?

Cyclomatic complexity is likely the most widely used complexity metric in software engineering. It describes the complexity of a procedure by measuring the linearly independent paths through its source code.

34. What is the difference between interoperability and compatibility testing with some examples?

Interoperatability:-To check if the software can co exist with other supporting softwares in the system

Compatibility:-To check if the software runs on different types of operating systems according to customer requirements.

35. Which testing method is used to check the software in abnormal condition?

1) Stress testing
2) Security testing
3) Recovery testing
4) Beta testing

36. What’s the Test Case?

A set of test inputs, execution, and expected result developed for a particular objective.

37. What’s the Traceability Matrix?

A document that showing the relationship between Test Requirements and Test Cases.

38. How many types of approaches are used in Integration Testing?

There are two types of approaches used-

Bottom-Up
Top-Down

39. What is Emulator?

A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.

40. What is Functional Decomposition?

A technique used during planning, analysis and design; creates a functional hierarchy for the software.

41. What is Glass Box Testing?

A synonym for White Box Testing.

42. What is Gorilla Testing?

Testing one particular module, functionality heavily.

43. What is Gray Box Testing?

A combination of Black Box and White Box testing methodologies testing a piece of software against its specification but using some knowledge of its internal workings.

44. What is Integration Testing?

Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

45. What is Metric?

A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code.

46. What is Quality Assurance?

All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.

47. What is Quality Control?

The operational techniques and the activities used to fulfill and verify requirements of quality.

48. What is Race Condition?

A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access.

49. What is Scalability Testing?

Performance testing focused on ensuring the application under test gracefully handles increases in work load.

50. What is Software Requirements Specification?

A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software.