Hi, I found this document to be helpful while planning for manual testing interview.Personal Question

1.    How you want to see yourself after 3 years?
I would be looking at a senior member in the organization where i could take some crucial decision and also leading a team of testers.

2.    What is your life dream?
To be a good manager for a team of young testers.

3.    Tell about your Positives and negatives?
My positives are group work and adjusting mentality. My negatives are difficulty in saying a 'no'.

4.    In what way you say that this work given to you will be done better than others?
My ability for team work, better understanding, and client coordination will give a better out put.

5.    When you realize for a relentless fault that you have done that will cause a major problem how you will react?
I will owe it up and explain to my seniors about how i did the mistake and apologize for the same. Then will find ways by which i can solve the issue.

6.    How will be your Problem management in absence of your immediate senior?
I will talk to my team members and take a collective decision and talk to senior over phone and tell him about the team decision and ask him for his advice and proceed as per his instructions.

7.    Tell me about your very good and very bad experience?
My good experience was after SIT a few bugs were not rectified and send to client the developers took the responsibility for the bugs. When the same issue was raised by the client the developers said that they had rectified it. Since the issue was raised by the client it     directly came top the quality dept from our top management and since i had screen shoots and explained the situation to my seniors before sending the release i was not affected by it.

8.    When you are forced to do the work that is not coming under your responsibility what will you do?
It will basically depend on the scope of the project. If it is not there in the scope will tell them it is not in our project scope. But if we happen to see that the client is a very important for the organization will try to put in some extra effort and do the work for the client.












Technical Questions

1.    What is Software Testing?
Software testing is a testing to make a product bug free. Testing involves operation of a system or application under controlled conditions and evaluating the results. The controlled conditions should include both normal and abnormal conditions.

2.    What is the Purpose of Testing?
To give a product to the client that is bug free and working up to the expectation of the client as his requirement.

3.    What types of testing do testers perform?
Unit Testing, Integration Testing, SIT, UAT, Black Box and White Box.

4.    What is the Outcome of Testing?
A bug free product as per the expectation of the client.

5.    What kind of testing have you done?
Unit Testing and SIT.

6.    What is the need for testing?
To give a product to the client that is bug free and working up to the expectation of the client as his requirement.

7.    What are the entry criteria for Functionality and Performance testing?
Functionality Testing: All the relevant documents should be prepared (Test condition, Cases) and signed off by the client. The testing environment should be freeze.
Performance testing: The application should be stable and SIT should have been done.

9.    What is test metrics?
Test Metrics is a mechanism to know the effectiveness of the testing that can be measured quantitatively. It is a feedback mechanism to improve the Testing Process that is followed currently.
Test metrics should cover basically 3 things:
a.    Test coverage.
b.    Time for one test cycle.
c.    Convergence of testing.

10.    Why do you go for White box testing, when Black box testing is available?
To check the internal logic and to cover all basis path and loop testing.

11.    What are the entry criteria for Automation testing?
The entry criteria is that the application should be stable.

12.    When to start and Stop Testing?
Testing can start once the coding is completed and application is stable or a part of the module coding is completed. Testing can end once all the bugs raised by the tester is rectified or differed for future enhancement.



13.    What is Quality?
A product that is fit to use. Quality means getting things right at the first time when it is done.

14.    What is Baseline document, Can you say any two?
These documents are used for testing and developing they are Functional Specification and Business Requirement.

15.    What is verification?
The process of evaluating a system or component to determine whether the products of the given development phase satisfy the conditions imposed at the start of that phase. [IEEE] [Did we develop the right product?]

16.    What is validation?
Determination of the correctness of the products of software development with respect to the user needs and requirements. [Did we develop the product right?]

17.    What is quality assurance?
A planned and systematic set of activities to ensure that variances in processes are clearly identified, assessed and improving defined processes for fulfilling the requirements of customers and product or service makers.

A planned and systematic pattern of all actions necessary to provide adequate confidence that the product optimally fulfils customer's expectations.

A planned and systematic set of activities to ensure that requirements are clearly established and the defined process complies with these requirements.

18.    What is quality control?
Quality control is a process by which actually helps us in delivering a product that is bug free and maintains some standards

19.    What are SDLC and TLC?
SDCL is Software Development Life Cycle and TLC is Testing Life Cycle

20.    What are the Qualities of a Tester?
A tester should have a good logical understanding of the application and his job is to see ways by which he can find errors in the system. He should also give some good constructive ideas to the development team to develop a good product.

21.    When to start and Stop Testing?
Testing can start once the coding is completed and application is stable or a part of the module coding is completed. Testing     can end once all the bugs raised by the tester is rectified or differed for future enhancement.

22.    What are the various levels of testing?
Unit Testing
Integration Testing
SIT
UAT


23.    What are the types of testing you know and you experienced?
Unit Testing
Integration Testing
SIT

24.    What exactly is Heuristic checklist approach for unit testing?
It is one of the techniques used in usability testing

25.    After completing testing, what would you deliver to the client?
Test Closure Documents like Test Case, Test Conditions, Traceability Matrix, Defect Report, Test Summary Report, Test Data and Down Time Report.

26.    What is a Test Bed?
It is set of data we input when we get a blank database for starting the testing.

27.    What is a Data Guidelines?
Guidelines which are the inputs for preparing the data.

28.    Why do you go for Test Bed?
When we get a empty database for testing it will not be possible for us to start testing so we need to input some initial data so that we can start the testing (so that we do not get data set up problems).

29.    What is Severity and Priority and who will decide what?
Severity is to tell how whether the bug is Critical, Medium, or Low. If it is critical it is a show stopper if it is medium it has some functional problem but can proceed if it is low some minor alignment or look and feel problem.
Priority is when the bugs will be rectified.
Severity is decided by the testers and priority is decided by the developers.

30.    Can Automation testing replace manual testing? If it so, how?
No automation cannot replace manual testing. Only if an application is stable can we go for automation. To find whether an application is stable we need to do Manual testing.

31.    What is a test case?
Test case is derived from a test condition and it tells what functionality we are going to test for a given condition and the expected result.

32.    What is a test condition?
Test condition is derived from BR/FS, which reflects the actual customer requirements.

33.    What is the test script?
It tells us the flow or a step-by-step process that we are going to execute along with the test data.

34.    What is the test data?
It is a data that we are going to use to test a particular functionality.

35.    What is an Inconsistent bug?
If we get a bug that cannot be simulated or it come some times only then it is called inconsistent bug.
36.    What is the difference between Re-testing and Regression testing?
Retesting is one which is done fully and regression is one it is done related to a bug and the places it can have an impact.

37.    What are the different types of testing techniques?
Equivalence Class Partisan, Boundary Value Analysis, Error Guessing.

38.    What are the risks involved in testing?
Schedule Risk
Resource Risk
Technology Risk

39.    Differentiate Test bed and Test Environment?
Test bed is initial data that is entered to start testing. Test Environment is the environment in which we are going to test the application.

40.    What is the difference between quality and testing?
Quality is a process to deliver a bug free product. Testing is a part of quality.

41.    What is the difference between White & Black Box Testing?
White box is used for code checking and see the flow of loops.
Black box we do a functionality testing without looking at the coding.

42.    What is the difference between Quality Assurance and Quality Control?
Quality control is a process by which actually helps us in delivering a product that is bug free and maintains some standards.
Quality Control is a process by which we maintain certain standard so that we develop a product which will have some pre defined standards.

43.    What is the difference between Testing and debugging?
Testing is a process by which we identify the bugs and debugging is a process by which the developers identify the bugs and rectifies it.

44.    What is the difference between bug and defect?
Defect is a deviation from the FS/BR. A bug is an error found in the application.

45.    What is the difference between verification and validation?
Verification asks, "Is the product being built right?" It is the process of determining whether or not the products of a given phase of the software development cycle fulfill the established requirements. Validation asks, "Is the right product being built?" It evaluates software at the end of the development lifecycle to ensure that the product not only complies with standard safety requirements and the specific criteria set forth by the customer, but performs exactly as expected.

46.    What is the difference between functional spec. and Business requirement specification?
Functional specification is used for SIT and Business requirement is used for UAT.  FS is more technical used for development process and BR is more useful towards the analysis point.



47.    What is the difference between unit testing and integration testing?
Unit is the basic level of testing and tries to validate more towards field level validation. Integration testing is done at a module level.

48.    What is the diff between Volume & Load?
In volume number of transaction is increased and the no of user constant in load the no user will be increased and transaction is kept constant.

49.    What is diff between Volume & Stress?
In volume number of transaction is increased and the no of user is constant in stress both user and transaction is increased.

50.    What is the diff between Stress & Load Testing?
In stress both user and transaction is increased in load the no user will be increased and transaction is kept constant.

51.    What is the Diff between Two Tier & Three tier Architecture?
Business/ application logic resides in a separate system in 3 tier where as in 2 tier it resides in the front end system.

52.    What is the diff between Client Server & Web Based Testing?
Client server it is a controlled environment we concentrate more at the functionality where as in web based we check more towards the security of the application.

53.    What is the diff between Integration & System Testing?
Integration testing we test the interfaces in system testing we test the functionality.

54.    What is the Diff between static and dynamic?
Static Testing: Analysis of a program carried out without executing the program.
Dynamic Testing: Testing software through executing it.

55.    What is the diff between alpha testing and beta testing?
Alpha testing is done by user is performed at the development site.
Beta testing is done by user is performed at the client site.

56.    What are the Minimum requirements to start testing?
The application should be stable to start testing.

57.    What is Smoke Testing & when it will be done?
Smoke testing is like adhoc testing and it is normally done at the sanity testing level or during the last stage of testing to see that no error is there in the application.

58.    What is Adhoc Testing? When it can be done?
Adhoc testing is a free form testing it can be done if we do not have much information about the application or during the normal testing process also for it helps to find some defects that are not covered in the conditions.




59.    What is security testing?
Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.

60.    What is database testing?
To check if the data base get updated once a transaction is posted in the front end and also to see if the data gets updated in the data base correctly.

61.    What is the relation ship between Quality & Testing?
Testing is a part of quality and testing tell us how to improve the quality of a product and where we have to concentrate.

62.    How do you determine, what to be tested?
Based on the FS and the priority of the modules that need to delivered we determine what needs to be tested.

63.    How do you go about testing a project?
Start with the initiation, planning, execution, defect management and test closure.

64.    What is the Initial Stage of testing?
Initiation.

65.    What is Web Based Application Testing?
Web Based Application Testing is End-to-end system testing with dynamically created test actions based on results from previous test actions.

66.    What is Two Tier & Three tier Architecture?
2 Tier: Refers to client/server architectures in which the user interface runs on the client and the database is stored on the server. The actual application logic can run on either the client or the server.
3 Tier: A special type of client/server architecture consisting of three well-defined and separate processes, each running on a different platform:

a.    The user interface, which runs on the user's computer (the client).
b.    The functional modules that actually process data. This middle tier runs on a server and is often called the application server.
c.    A database management system (DBMS) that stores the data required by the middle tier. This tier runs on a second server called the database server.

67.    What is the use of Functional Specification?
It gives an over view of the application and helps us in planning, estimation, duration and helps us in writing test case and conditions.

68.    Why do we prepare test condition, test cases, and test script (Before Starting Testing)?
To deliver a good product and also to show that we have covered all the scenarios in the application and we have fully covered the application.

69.    Is it not waste of time in preparing the test condition, test case & Test Script?
No  

70.    How do you go about testing of Web Application?
To concentrate more towards the security and loading of different pages and links.

71.    How do you go about testing of Client Server Application?
To concentrate more towards the functionality part.

72.    What is meant by Static Testing?
It is testing without executing, just a walk through of the application.

73.    Can the static testing be done for both Web & Client Server Application?
Yes

74.    In the Static Testing, what all can be tested?
Baseline documents, test deliverables before test execution and closer.

75.    Can test condition, test case & test script help you in performing the static testing?
Yes
76.    What is meant by dynamic testing?
Is normal testing done by executing the application.

77.    Is the dynamic testing a functional testing?
Yes

78.    Is the Static testing a functional testing?
No

79.    What are the functional testing you perform?
SIT

80.    What is meant by Alpha Testing?
Alpha testing is done by user is performed at the development site.

81.    What kind of Document you need for going for an Functional testing?
Functional Specification.

82.    What is meant by Beta Testing?
Beta testing is done by user is performed at the client site.

83.    At what stage the unit testing has to be done?
It is done at the initial stage after completing the coding and we find the application to be stable.

84.    Who can perform the Unit Testing?
Normally the developers are better to do unit testing. If it is not done by them then it can be done by the testers.

85.    When will the Verification & Validation be done?
Verification before testing and validation during testing.




86.    What is meant by Code Walkthrough?
A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.

87.    What is meant Code Review?
A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards. It is also called as Code Inspection.

88.    What is the testing that a tester performs at the end of Unit Testing?
Integration Testing.

89.    What are the things, you prefer & Prepare before starting Testing?
Understanding the application fully, test conditions, test case, test data, traceability matrix.

90.    What is Integration Testing?
IT checks to see the integration (flow of information from one module to another) between different modules.

91.    What is Incremental Integration Testing?
Module by module testing is Incremental Integration Testing.

92.    What is meant by System Testing?
System testing is functional testing.

93.    What is meant by SIT?
System Integration Testing.

94.    When do you go for Integration Testing?
Once unit testing is done and application is stable.

95.    Can the System testing be done at any stage?
No only after we complete unit it is advisable to go for System testing.

96.    What are stubs & drivers?
Stub: A skeletal or special-purpose implementation of a software module, used to develop or test a component that calls or is otherwise dependent on it.
Driver: A program or test tool used to execute software against a test case suite.

97.    What is the final Stage of Integration Testing?
SIT.

98.    Where in the SDLC, the Testing Starts?
After Coding.

99.    What is the Outcome of Integration Testing?
A stable application that can be sent to production for SIT.

100.    What is meant by GUI Testing?
To check for GUI components and the their functionality.

101.    What is meant by Back-End Testing?
It is database testing.

102.    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.

103.    What is Usability Testing?
Usability testing is to see how good the product is as per the requirements of the customer and also to see how user friendly the product is.

104.    What is the Importance of testing?
To deliver a bug free product as per the requirement of the client.

105.    What is meant by regression Testing?
Regression Testing is used to check the status of bugs that we sent top developers and to see if they have any impact due to the rectification of the bugs sent.

106.    When we prefer Regression & what are the stages where we go for                                                                                Regression Testing?
After the fixing of the defects by the developers we go for regression.

107.    What is performance testing?
It is testing to see what happens to the application under different loads of data.

108.    What is the Performance testing; those can be done Manually & Automatically?
It is testing to see what happens to the application under different loads of data. It is normally done using tools (automation).

109.    What is Volume, Stress & Load Testing?
In volume number of transaction is increased and the no of user constant in load the no user will be increased and transaction is kept constant in stress both user and transaction is increased.

110.    What is a Bug?
It is a defect in the product that dose not match with the FS or the expected result.

111.    What is a Defect?
It is a deviation from the FS that lead to error.

112.    What is the defect Life Cycle?
It tells us what happens after a bug is raised by the tester.

113.    What is the Priority in fixing the Bugs?
Critical bugs are normally fixed first followed by medium and then low normally.


114.    Explain the Severity you rate for the bugs found?
Severity is to tell how whether the bug is Critical, Medium, or Low If it is critical it is a show stopper if it is medium it has some functional problem but can proceed if it is low some minor alignment or look and feel problem.

115.    Diff between UAT & IST?
For UAT we use the BR, for IST we use the FS.

UAT is done normally by the end user with a good domain knowledge and IST by the Testers.

In IST we do testing based on condition and in UAT it will be mostly done in scenario based.

116.    What is meant by UAT?
It is User Acceptance Testing.

117.    What all are the requirements needed for UAT?
Sit should have been done, BR document should be available.

118.    What is risk analysis?
It helps us to find what are the risks associated with a project.
Schedule Risk
Resource Risk
Technology Risk

119.    How to do risk management?
By finding out the expected risk before testing.

120.    What are test closure documents?
Test Closure Documents like Test Case, Test Conditions, Traceability Matrix, Defect Report, Test Summary Report, Test Data and Down Time Report.

121.    What is traceability matrix?
It is document which tells whether we have tested completely.

122.    What ways you followed for defect management?
We used tracebility matrix and Orbi Solve.

Share
Related Documents
  1. Software Testing FAQ (1534)
  2. Software Testing : Frequently Asked Questions (1664)
  3. Software Testing Basic FAQ (1835)
  4. Software QA and Testing Frequently-Asked Questions (1349)
  5. Load Runner Interview Questions (1783)
  6. Software Testing & Quality Assurance FAQ (1582)
  7. Database Testing Interview Questions (3181)
  8. FAQ on Software Testing (793)
  9. Testing faqs (1757)
  10. Software Testing : Interview Questions & Answers (2704)
  11. How to Answer 64 Toughest Interview Questions (2308)
  12. QTP questions & Answers (3228)
  13. Testing interview question (1582)
  14. Software Testing FAQ (1528)
  15. Tips for a Software Quality Assurance (SQA) Interview (1647)
  16. Tech Interview : Software Testing Interview Questions (1235)
  17. Interview Questions frp fuocemter.com (1280)
  18. Short Interview Question with Explanation usefull (2264)
  19. E-commerce interview questions (3414)
  20. Interview Q & A (1074)