Manual Testing Questions & Answers

MANUAL TESTING QUESTIONS & ANSWERS 1. What is meant by Priority and severity? Severity: 1. This is assigned by the Test Engineer 2. This is to say how badly the deviation that is occurring is affecting the other modules of the build or release. Priority: 1. This is assigned by the Developer. 2. This is to say how soon the bug as to be fixed in the main code, so that it pass the basic requirement. Egg. The code is to generate some values with some valid input conditions. The priority will be assigned so based on the following conditions: a It is not accepting any value b It is accepting value but output is in non-defined format (say Unicode Characters). A good example I used some Unicode characters to generate a left defined arrow, it displayed correctly but after saving changes it gave some address value from the Stack of this server. For more information mail me I will let you know. 2. Give me some example for high severity and low priority defect? If suppose the title of the particular concern is not spelled correctly, it would give a negative impacted ICICC is spelled as a title for the project of the concern ICICI. Then it is a high severity, low priority defect. 3. What is basis for test case review? The main basis for the test case review is 1. Testing techniques oriented review 2. Requirements oriented review 3. Defects oriented review. 4. What are the contents of SRS documents? Software requirements specifications and Functional requirements specifications. 5. What is difference between the Web application testing and Client Server testing? Testing the application in intranet (without browser) is an example for client -server. (The company firewalls for the server are not open to outside world. Outside people cannot access the application.)So there will be limited number of people using that application. Testing an application in internet (using browser) is called web testing. The application which is accessible by numerous numbers around the world (World Wide Web.) So testing web application, apart from the above said two testing there are many other testing to be done depending on the type of web application we are testing. If it is a secured application (like banking site- we go for security testing etc.) If it is an e-commerce testing application we go for Usability etc… Testing. 6. Explain your web application architecture? Web application is tested in 3 phases 1. Web tier testing – browser compatibility 2. Middle tier testing – functionality, security 3. Data base tier testing – database integrity, contents se the product/application has to deliver to client at 5.00PM,At that time you or your team member caught a high severity defect at 3PM.(Remember defect is high severity)But the client is cannot wait for long time. You should deliver the product at 5.00Pm exactly. Then what is the procedure you follow? The bug is high severity only so we send the application to the client and find out the severity is priority or not. If its priority then we ask him to wait. Here we found defects/bugs in the last minute of the delivery or release date Then we have two options 1. Explain the situation to client and ask some more time to fix the bug. 2. If the client is not ready to give some time then analyze the impact of defect/bug and try to find workarounds for the defect and mention these issues in the release notes as known issues or known limitations or known bugs. Here the workaround means remedy process to be followed to overcome the defect effect. 3. Normally this known issues or known limitations (defects) will be fixed in next version or next release of the software 8. Give me examples for high priority and low severity defects? Suppose in one banking application there is one module ATM Facility. In that ATM facility when ever we are depositing/withdrawing money it is not showing any conformation message but actually at the back end it is happening properly with out any mistake means only missing Of message. In this case as it is happening properly so there is nothing wrong with the application but as end user is not getting any conformation message so he/she will be Confuse for this. So we can consider this issue as HIGH Priority but LOW Severity defects… 9. Explain about Bug life cycle? 1) Tester- 2) Open defect- 3) Send to developer 4) -if accepted moves to step5 else sends the bug to tester gain 5) Fixed by developer - 6) Regression testing- 7) No problem inbuilt and sign off -if problem in built reopen the issue send to step3 10. How can you report the defect using excel sheet? To report the defect using excel sheet Mention: The Future that been effected. Mention: Test Case ID (Which fail you can even mention any other which are dependency on this bug) Mention : Actual Behavior Mention : Expected Behavior as mentioned in Test Case or EFS or EBS or SRS document with section Mention : Your Test Setup used during Testing Mention : Steps to Re-Produce the bug Mention : Additional Info Mention : Attach a Screen Shot if it is a GUI bug Mention : Which other features it is blocking because of this bug that you are unable to Execute the test cases. Mention: How much time you took to execute that test case or follow that specific TC Which leaded to bug? 11.If you have executed 100 test cases ,every test case passed but apart from these test case you found some defect for which test case is not prepared,thwn how you can report the bug? While reporting this bug into bug tracking tool you will generate the test case mean put the steps to reproduce the bug. 12. What is the difference between web based application and client server application? The basic difference between web based application & client server application is that the web application are 3 tier & client based are 2 trier.In web based changes are made at one place & it is reflected on other layers also whereas client based separate changes need be installed on client machine also. 13. What is test plan? And can you tell the test plan contents? Test plan is a high level document which explains the test strategy, time lines and available resources in detail. Typically a test plan contains: -Objective -Test strategy -Resources -Entry criteria -Exit criteria -Use cases/Test cases -Tasks -Features to be tested and not tested -Risks/Assumptions. 14. How many test cases can you write per a day, an average figure? Complex test cases 4-7 per day Medium test cases 10-15 per day Normal test cases 20-30 per day 15. Who will prepare FRS (functional requirement documents)? What is the important of FRS? The Business Analyst will pre pare the FRS. Based on this we are going to prepare test cases. It contains 1. Over view of the project 2. Page elements of the Application (Filed Names) 3. Prototype of the of the application 4. Business rules and Error States 5. Data Flow diagrams 6. Use cases contains Actor and Actions and System Responses 16. 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. 17. 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. 18. 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. 19. 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 20. 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. 21. 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 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 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. 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) 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