Manual Software Testing interview Questions

21. What are the client side scripting languages and server side scripting languages?

1.  Client side scripting languages

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

     2.Server side Scripting languages

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

22. 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
    4. Send the defect report with screen shots, inputs and procedure for defect reproduction.
    5.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.

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

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

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

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

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

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

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

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

31.How do you review test case? Type of Review…
 

• Types of reviewing test cases depend upon company standards, viz..,

• Peer review, team lead review, project manager review.

• Some times client may also review the test cases reg what is approach following for project

32. In which way tester get Build A, Build B, Build Z of an application, just explains the process?

• After preparation of test cases project manager will release software release note in that Document there will be URL path of the website link from that we will receive
• The build In case of web server projects, you will be provided with an URL or a 92.168. ***. *** (Web address) which will help you access the project using a browser from your system.
• In case of Client server, the build is placed in the VSS (Configuration tool) which will help you get the .exe downloaded to your computer.

33. Apart from bug reporting what is your involvement in project life cycle?

• As a Test engineer we design test cases, prepare test cases Execute Test cases, track the bugs, analyze the results report the bugs. Involved in regression testing, performance of system
• Testing system integration testing at last preparation of Test summary Report

34.What are the contents of test report?
 
There are two documents, which should be prepared at particular phase.

1. Test Results document.
2. Test Report document.

• Test Results doc will be prepared at the phase of each type of Testing like FULL FUNCTIONAL TEST PASS,REGRESSION TEST PASS,SANITY TEST PASS etc…Test case execution against
• The application. Once you prepared this doc, we will send the doc to our TL and PM.By seeing the Test Results doc, TL will come to know the coverage part of the testcase.Here I am giving you the contents used in the Test Results doc?

1. Build No
2. Version Name
3. Client OS
4. Feature set
5. Main Feature
6. Defined Test cases on each feature.
7. QA engineer Name
8. Test e-cases executed. (Includes pass and fail)
9. Testcases on HOLD (Includes blocking test cases and deferred Test cases)
10. Covereage Report (Which includes the coverage ratings in %, like % of test cases covered, % of test cases failed)

Coming to Test report, generally we will prepare Test report, once we rolled out the product to our client. This document will be prepared by TL and delivered to the client.Mainly, this document describes the what we have done in the project, chievements we have reached, our Learning’s in throughout the project etc…The other name for Test report is Project Closure Report and we will summarize the all the activities, which have taken place in through out the project. Here I am giving your the contents covered in the Test Report.

    1. Test Environment (Should be covered the OS, Application or webservers, Mahchine names, Database, etc…)    2.Test Methods(Types of Tests, we have done in the project like Functional Testing, Platform Testing, regression Testing,etc..    3. Major areas Covered.
    4. Bug Tracking Details. (Includes inflow and outflow of the bus in our delivered project)
    5. Work schedule (When we start the testing and we finished)    6. Defect Analysis        6.1 Defects logged in different types of tests like Functional Test, regressiion Test as per area wised.        6.2 State of the Defects at end of the Test cycle.        6.3 Root cause analysis for the bugs marked as NOT A BUG.    7. QA observations or learning’s thought the life cycle.

35. Write high level test cases?

• Write all the test cases under high level TC, which can be covered the main functionalities like
• Creation, edition, deletion, etc….as per prescribed in the screen.
• Write all the test cases under low level TC,which can be covered the screen, like input fields are displayed as per the requirements, buttons are enabled or disabled, and test case for low priority functionalities.
• Example a screen contains two edit boxes login and password and a put buttons OK and Reset and check box for the label “Remember my password”. Now let us write high level TC
• And low level test cases.

HIGH LEVEL TESTCASES

    1. Verify that User is able to login with valid login and valid password.    2. Verify that User is not able to login with invalid login and valid password    3. Verify that Reset button clears the filled screen.    4. Verify that a pop up message is displayed for blank login.

LOW LEVEL TC    1. Verify that after launching the URL of the application below fields are displays in the screen.    2. Login Name 2.Password.3.OK BUTTON 4.RESET button etc.    3. Check box, provided for the label “remember my pwd” is unchecked.    4. Verify that OK button should be disabled before selecting login and password fields.    5. Verify that OK button should we enabled after selecting login and password.    6. Verify that User is able to check the check box, providedfor the label “remember my password”.
In this way, we can categories all the test cases under HIGH LEVEL and LOW LEVEL.

36. What is test scenario?
 

• Test scenario will be framed on basis of the requirement, which need to be checked. For that, we will frame set of test cases, in other terms, we can say all the conditions, which can be determined the testing coverage against business requirement.
• Please see the below example, which is exactly matched to my explanation.
• As we know all most all the application are having login screen, which contains login name and password. Here is the test scenario for login screen.

Scenario: USER’S LOGIN

Conditions to be checked to test the above scenario:
—————————————————-
1. Test login field and Password fields individually.
2. Try to login with valid login and valid password.
3. Try to login with invalid login and valid password. Etc

37. What is build duration?
 

• it is a tine gap between old version build and new version build in new version build some new extra features are added

38. What is test deliverables?

• Test deliverables are nothing but documents preparing after testing like test plan document test case template bug report template Test deliverables will be delivered to the client not only for the completed activities, but also for the activites, which we are implementing for the better productivity. (As per the company’s standards).Here I am giving you some of the Test deliverables in my project.

    1. QA Test Plan    2. Test case Docs    3. QA Test plan, if we are using Automation.    4. Automation scripts    5. QA Coverage Matrix and defect matrix.    6. Traceability Matrix    7. Test Results doc    8. QA Schedule doc (describes the deadlines)    9. Test Report or Project Closure Report. (Prepared once we rolled out the project to client)    10. Weekly status report (sent by PM to the client)    11. Release Notes.

39. What is your involvement in test plan?

• Test lead is involved in preparing test plan test engineers are no way related in preparing test plan role TE is test case design, and execution and bug tracking and reporting them Generally TL is involved in preparation of the TestPlan.But it is not mandatory only TL will take main part in the preparation of the TP.Test engineer can suggest to TL, if he (or) she has good understanding on project and resources, if he or she has more exp with the project, if TL is wrongly given deadlines. If your suggestions are valid, TL will incorporate all of them to the TestPlan.But in most of the companies Test engineers are just audience.

40. Which test cases are not to be automated?
 

• All the test cases which are related to a feature of the product, that keeps on changing (there are always some or the other enhancements in it). Frequent enhancements may change the UI, add/remove few controls. Hence such cases, if automated, would involve lot of a intendance