Testing Interview Questions

1. How you can decide the number of test cases is enough for testing the given module?

The developed test cases are covered all the functionality of the application we can say test cases are enough. If u knows the functionality covered or not u can use RTM.

2. What is the difference between Retesting and Data Driven Testing?

Retesting: it is manual process in which application will be tested with entire new set of data.
Data Driven Testing(DDT)-It is a Automated testing process in which application is tested with multiple test dated is very easy procedure than retesting because the tester should sit and need to give different new inputs manually from front end and it is very tedious and boring
Procedure.

3. What is regression testing?

After the Bug fixed, testing the application whether the fixed bug is affecting remaining functionality of the application or not.Majorly in regression testing Bug fixed module and it’s
Connected modules are checked for their integrity after bug fixation.

4. How does u test web application?

Web application testing
Web application should have the following features like
1. Attractive User Interface (logos, fonts, alignment)
2. High Usability options
3. Security features (if it has login feature)
4. Database (back end).
5. Performance (appearing speed of the application on client system)
6. Able to work on different Browsers (Browser compatibility), O.S compatibility (technically called as portability)
7. Broken link testing………etc
So we need to follow out the following test strategy.
1. Functionality Testing
2. Performance Testing (Load, volume, Stress, Scalability)
3. Usability Testing
4. User Interface Testing (colors, fonts, alignments…)
5. Security Testing
6. Browser compatibility Testing (different versions and different browser)
7. Broken link and Navigation Testing
8. Database (back end) Testing (data integrity)
9. Portability testing (Multi O.s Support)….etc

5. How does u perform regression testing, means what test cases u select for regression?

Regression testing will be conducted after any bug fixed or any functionality changed.
During defect fixing procedure some part of coding may be changed or functionality may be manipulated. In this case the old test cases will be updated or completely re written
According to new features of the application where bug fixed area. Here possible areas are old test cases will be executed as usual or some new test cases will be added to existing test cases or some test cases may be deleted.

6. What r the client side scripting languages and server side scripting languages?

Client side scripting languages are
Javascript, VbScript, PHP…etc
Server side Scripting languages are
Perl, JSP, ASP, PHP.etc
Client side scripting languages are useful to validate the inputs or user actions from user side or client side.
Server side Scripting languages are to validate the inputs at server side.
These scripting languages provide security for the application. And also provides dynamic nature to web or client server application
Client side scripting is good because it won’t send the unwanted input’s to server for validation. From front-end it self it validated the user inputs and restricts the user activities and guides him

7. If a very low defect (user interface) is detected by u and the developer not compromising with that defect,what will u do?
User interface defect is a high visibility defect and easy to reproduce.
Follow the below procedure
1. Reproduce the defect
2. Capture the defect screen shots
3. Document the proper inputs that you are used to get the defect in the defect report
3. Send the defect report with screen shots, i/ps and procedure for defect reproduction.
Before going to this you must check your computer hard ware configuration that is same as developer system configuration. And also check the system graphic drivers are properly
Installed or not. If the problem in graphic drivers the User interfaces error will come.
So first check your side if it is correct from your side then reports the defect by following the above method.

8.if u r only person in the office and client asked u for some changes and u didn’t get what the client asked for what will u do?
One thing here is very important. Nobody will ask test engineer to change software that is
not your duty, even if it is related to testing and anybody is not there try to listen care fully if you are not understand ask him again and inform to the corresponding people immediately.
Here the client need speedy service, we (our company) should not get any blame from customer side.

9. How to get top two salaries from employee tables?
Select * from EMP e where 2>= (select count (*) from EMP e where sal>e.sal) order by desc sal.

10. How many Test-Cases can be written for the calculator having 0-9 buttons, Add, Equalto buttons? The test cases should be focused only on add-functionality but mot GUI.What is those test-cases?
Test-Cases for the calculator
so here we have 12 buttons totalize 0,1,2,3,4,5,6,7,8,9,ADD,Equalto -12 buttons
here u can press at least 4 buttons at a time minimum for example 0+1= for zero u should press ‘zero’ labeled button for plus u should press ‘+’ labeled button for one u should press ‘one’ labeled button for equal to u should press ‘equal to’ labeled button 0+1=here + and = positions will not vary so first number position can be varied from 0 to 9 i.e. from permutation and combinations u can fill that space in 10 ways in the same way second number position can be varied from 0 to 9 i.e. from permutation and combinations u can fill that space in 10 ways
Total number of possibilities are =10×10=100
This is exhaustive testing methodology and this is not possible in all cases.
In mathematics we have one policy that the function satisfies the starting and ending values of a range then it can satisfy for entire range of values from starting to ending.
then we check the starting conditions i.e. one test case for ‘0+0=’ (expected values you know that’s ‘0′) then another test case for ‘9+9=’(expected values you know that’s ‘18′) only two test cases are enough to test the calculator functionality.

11. What is positive and negative testing.Explain with example?
Positive Testing - testing the system by giving the valid data.
Negative Testing - testing the system by giving the Invalid data.
For Exam application contains a textbox and as per the user’s Requirements the textbox should accept only Strings. By providing only String as input data to the textbox & to check whether its working properly or not means it is Positive Testing. If giving the input other than String means it is negative Testing.

12. How will you prepare Test plan. What are the techniques involved in preparing the Test plan?
Test plan means planning for the release. This includes Project background
Test Objectives: Brief overview and description of the document
Test Scope: setting the boundaries
Features being tested (Functionalities)
Hardware requirements
Software requirements
Entrance Criteria (When to start testing):
Test environment established, Builder received from developer, Test case prepared and reviewed.
Exit criteria (when to stop testing):
All bug status cycle are closed, all functionalities are tested, and all high and medium bugs are resolved.
Project milestones: dead lines

13. What is the Defect Life Cycle?
Defect life cycle is also called as bug life cycle. It has 6stages namely
1. New: found new bug
2. Assigned: bud assigned to developer
3. Open: developer is fixing the bug
4. Fixed: developer has fixed the bug
5. Retest: tester retests the application
6. closed/reopened: if it is ok tester gives closed statuselse he reopens and sends back to developer.

14. Expalin about metrics Management?
Metrics: is nothing but a measurement analysis.Measurment analysis and Improvement is one of the process area in CMM I L2.

15. What is performance Testing and Regression Testing?
Performance Testing:-testing the present working condition of the product
Regression Testing:-Regression Testing is checking for the newly added functionality causing any errors interims of functionality and the common functionality should be stable
In the latest and the previous versions

Related Posts

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.