Part-1: Software Testing Interview Questions with Answers

1. What is Retesting?
Ans: If u do all the test procedures once u make any new change or add a new functionality is Regression testing whereas in Retesting
U will do testing for only the Changed Scenarios.

2. What documents we need/refer to make a test plan?
Ans: Most required SRS documentation
Real time question: We can refer only LLD for clear information About Requirements,Then what is the use of referring SRS document in V model, Please can u make difference

Srs is Software requirement specification, which contains the detailed description of what the user expects the application or software to perform . LLd is nothing but logic design/ code of control flow & data flow in the software or application.

In order to detect defects at the early stages of software development cycle . Testers has to be provided with both SRS and LLD.

3. What is Test Bed?
Ans: An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used.

4. What is Software Requirements Specification?
Ans:A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software

5.Difference between smoke testing and sanity testing?
Ans: Smoke Testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but not bothering with finer details. Sanity Testing is a cursory testing,it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing. It normally includes a set of core tests of basic GUI functionality to demonstrate connectivity to the database, application servers, printers, etc.

6.What is Soak Testing?
Ans: Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.

7.What is exactly the technical definition of a build
Ans:The application under test is known as Build.
OR
The executable software which is under testing.

8.What is Scalability Testing?
Ans: Performance testing focused on ensuring the application under test gracefully handles increases in work load.

9. What is Release Candidate?
Ans:A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).

10. What is Ramp Testing?
Ans: Continuously raising an input signal until the system breaks down.

11. What is Quality System?
Ans: The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.


12. What is Quality Policy?
Ans: The overall intentions and direction of an organization as regards quality as formally expressed by top management.

13. What is Quality Management?
Ans:That aspect of the overall management function that determines and implements the quality policy.

14.What is Quality Control?
Ans:The operational techniques and the activities used to fulfill and verify requirements of quality.

15.What is Quality Circle?
Ans:A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.

16.What is Quality Audit?
Ans:A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.

17.What is Quality Assurance?
Ans: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.

18.What is Monkey Testing?
Ans:Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.

19.What is Metric?
Ans: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.


20.What is Localization Testing?
Ans:This term refers to making software specifically designed for a specific locality.

21.What is Independent Test Group (ITG)?
Ans:A group of people whose primary responsibility is software testing.

21.What is Gorilla Testing?
Ans:Testing one particular module, functionality heavily.

22.What is Gray Box Testing?
Ans: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.

23.What is Functional Specification?
Ans. A document that describes in detail the characteristics of the product with regard to its intended features.

24.What is Functional Decomposition?
Ans:A technique used during planning, analysis and design; creates a functional hierarchy for the software.

25.What is Exhaustive Testing?
Ans:Testing which covers all combinations of input values and preconditions for an element of the software under test.

26. What is Equivalence Partitioning?
Ans: A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

27. What is Equivalence Class?
Ans: A portion of a component’s input or output domains for which the component’s behavior is assumed to be the same from the component’s specification.

28. What is Endurance Testing?
Ans: Checks for memory leaks or other problems that may occur with prolonged execution what is testing
Testing involves operation of a system or application under controlled conditions and evaluating the results (eg, ‘if the user is in interface A of the application while using hardware B, and does C, then D should happen’). The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn’t or things don’t happen when they should. It is oriented to ‘detection’. (See the Bookstore section’s ‘Software Testing’ category for a list of useful books on Software Testing.) • Organizations vary considerably in how they assign responsibility for QA and testing. Sometimes they’re the combined responsibility of one group or individual. Also common are project teams that include a mix of testers and developers who work closely together, with overall QA processes monitored by project managers. It will depend on what best fits an organization’s size and business structure.

29. What is Depth Testing?
Ans:A test that exercises a feature of a product in full detail.

30. What is Dependency Testing?
Ans: Examines an application’s requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.

31. What is Defect?
Ans:Non conformance to requirements or functional / program specification

32.What is Debugging?
Ans:The process of finding and removing the causes of software failures.

33.What is Cyclomatic Complexity?
Ans:A measure of the logical complexity of an algorithm, used in white-box testing.

34.What is Conversion Testing?
Ans: Testing of programs or procedures used to convert data from existing systems for use in replacement systems.

35. What is Component?
Ans: A minimal software item for which a separate specification is available.

36. What is Code Coverage?
Ans: An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.

37. What is Cause Effect Graph?
Ans: A graphical representation of inputs and the associated outputs effects which can be used to design test cases.

38. What is Breadth Testing?
Ans: A test suite that exercises the full functionality of a product but does not test features in detail.

39.What is Branch Testing?
Testing in which all branches in the program source code are tested at least once.

40. What is Boundary Value Analysis?
Ans:BVA is similar to Equivalence Partitioning but focuses on “corner cases” or values that are usually out of range as defined by the specification. his means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001.

41. What is Boundary Testing?
Ans:Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

42. What is Binary Portability Testing?
Ans: Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

43. What is Baseline?
Ans:The point at which some deliverable produced during the software engineering process is put under formal change control.

44. What is Basis Set?
Ans: The set of tests derived using basis path testing.

45. What is Basis Path Testing?
Ans: A white box test case design technique that uses the algorithmic flow of the program to design tests.

46. What is Basic Block?
Ans:A sequence of one or more consecutive, executable statements containing no branches.

47.What is Backus-Naur Form?
Ans: A metalanguage used to formally describe the syntax of a language.

48. How do you debug an ASP.NET Web application?
Ans: Attach the aspnet_wp.exe process to the DbgClr debugger.

49.Why are there five tracing levels in System. Diagnostics. Trace Switcher?
Ans: The tracing dumps can be quite verbose. For applications that are constantly running you run the risk of overloading the machine and the hard drive. Five levels range from none to Verbose, allowing you to fine-tune the tracing activities.


50.What’s the difference between the Debug class and Trace class?
Ans:Documentation looks the same. Use Debug class for debug builds, use Trace class for both debug and release builds.


51. What is test case? How test case is written. Example.
Ans: It is a input condition with expected result to a small work unit.
Based on Business requirements and Functional requirements test case is return.
For ex: A pen
1.To check whether pen is writing properly or not.
2.To check whether ink is there in the refill.
3. Verify pen cap is there or not.
etc.

52. What we do when the Requirements are continuously changed?
Ans: Whenever the requirements are continuously changing, we will do agile testing.

53.In an application if I enter delete button it should give an error message "Are you sure u want to delete?" but the application gives message as "are u sure?"is it a bug? And if it a bug how you rate severity?
Ans: First we have to make sure what the actual error message should be from the specifications document. If it is not clearly mentioned, then the bug to be reported should have a severity as "low" with suggestion attached.. If it is clearly mentioned in the specifications document, then its severity should be "medium" with reference attached.

54. What do you mean by review? How many reviews are there in manual testing? Please explain those?
Ans:

REVIEW
review is verification process without EXECUTION
static technique
bug prevention technique

Ex:- peer review, walkthrough, inspection

TYPES
1. TECHNICAL REVIEW
2. MGMT REVIEW


55.Test cases for shirt button?
Ans:
verify color of button
verify size of button
verify holes size in button

56.WHAT IS UCD ?
Ans: UCD means USE CASE DOCUMENT, it is the diagrammatic representation of requirements given by B.A

57.What is the maximum possible value of reliability?
Ans:To estimate\" peakload\" test eng,s are performing stress test
under customer expected configuration and more than customer expected load

58.When should you begin test plan
Ans:After the preparation of SRS document by PM and PL.

59. What is benchmark testing?
Ans:Benchmark testing is a normal part of the application development life cycle. It is a team effort that involves both application developers and database administrators (DBAs), and should be performed against your application in order to determine current performance and improve it.

60. How many test cases can we write for a scenario?
Ans: we can’t say the exact maximum no. but we can write 1 positive test case and 1 negative test case at minimum

61.What are the key challenges of testing?
Ans: To find out uncover bugs. Not notice even by client side
tell me some typical bugs you encountered in your last assignment give some examples
Example: In this question my answer is if we are testing the web page. If we are click one link, that link is not displayed related web page this is one bug. And another one is links are not working this is also one bug.

62. What is thread Testing?
Ans: A testing technique used to test the business functionality or business logic of the AUT in an end-to-end manner, in much the same way a User or an operator migyht interact with the system during its normal use.

63.How to write simple test cases for login page?
Ans:
enter valid id and valid pass word it should open expected page
enter valid and invalid password it should show \" enter valid pass word\"
enter invalid id and valid pass word it should show \" for got your user id\"
enter invalid id and invalid pass word it should show\" please enter valid pass word\"
leave user id blank and valid pass word it should show \"enter valid id\"
enter valid id and pass word blank it should show \" enter valid pass word\"
both of fields leave blank and click on Ok it should show \" forgot ur pass word\"
apply BVA for both user id and pass word
apply ECP for both user id and pass word

64.what is PATCH and abbreviate it

Ans: Patch is nothing but a software which contains supported additional features OR may be the fix for bugs. This patch is loaded and verify the new features and bug fixes

65.How much interaction with users should testers have and why there should be interaction within client
Ans: Client can provide their requirements and feedback to the under development project and helps to tester get known to client inputs(actual data) .

66.what is scenario? tell me with a simple example.
Ans:Test scenarios is nothing but combination of test cases
ex: if you take for a login window in that we have user name and password click on ok button this is one scenario.

67. In an application if I enter delete button it should give an error message "Are you sure u want to delete?" but the application gives message as "are u sure?"Is it a bug? And if it a bug how you rate severity?
Ans: First we have to make sure what the actual error message should be from the specifications document. If it is not clearly mentioned, then the bug to be reported should have a severity as "low" with suggestion attached.. If it is clearly mentioned in the specifications document, then its severity should be "medium" with reference attached.

68. What is the role of bug tracking system?
Ans: The Bug tracking system is used to know the status of bugs that occurs during the test execution. The tools like mantis, test director, Bugzilla are used for defect tracking.

69. How can we do database testing?
Ans: TO conduct database testing the test engineers are following bellow issues:

1) verification of data entered by the users through application at back end.
2) verification of database design
3) verifying the data integrity
4) verification of SQL scripts.