Manual Testing Q

Manual Testing Q & A Part 1 1. What is the testing process? Verifying that an input data produce the expected output. 2. What is the difference between testing and debugging? Big difference is that debugging is conducted by a programmer and the programmer fixes the errors during debugging phase. Tester never fixes the errors, but rather find and return them to programmer. 3. What is the difference between structural and functional testing? Structural is a "white box" testing and based on the algorithm or code. Functional testing is a "black box" (behavioral) testing where the tester verifies the functional specification. 4. What is a bug? What types of bugs do you know? Bug is a error during execution of the program. There are two types of bugs: syntax and logical. 5. What is the difference between testing and quality assurance (QA)? This question is surprisingly popular. However, the answer is quite simple. The goals of both are different: The goal of testing is to find the errors. The goal of QA is to prevent the errors in the program. 6. What kinds of testing do you know? What is it system testing? What is it integration testing? What is a unit testing? What is a regression testing? You theoretical background and home work may shine in this question. System testing is a testing of the entire system as a whole. This is what user sees and feels about the product you provide. Integration testing is the testing of integration of different modules of the system. Usually, the integration process is quite painful and this testing is the most serious one of all. Integration testing comes before system testing. Unit testing is a testing of a single unit (module) of within system. It's conducted before integration testing. Regression testing is a "backward check" testing. The idea to ensure that new functionality added to the system did not break old, checked, functionality of the system. 7. What are all the major processes will involve in testing? The major processes include: 1.Planning (test strategy, test objectives, risk management) 2.Design (functions to be tested, test scenario, test cases) 3Development (test procedures, test scripts, test environment) 4.Execution (execute test) 5.Evaluation (evaluate test results, compare actual results with expected results) 8. Could you test a program 100%? 90%? Why? Definitely not! The major problem with testing that you cannot calculate how many error are in the code, functioning etc. There are many factors involved such as experience of programmer, complexity of the system etc. 9. How would you test a mug (chair/table/gas station etc.)? First of all you must demand requirements and functional specification and design document of the mug. There will find requirements like ability to hold hot water, waterproof, stability, break ability and so on. Then you should test the mug according to all documents. 10. How would you conduct your test? Each test is based on the technical requirements of the software product. 11. What is the other name for white box testing? Clear box testing 12. What is other name for water fall model? Linear sequential model 13. What is considered a good test?

It should cover most of the object's functionality 14. What is 'Software Quality Assurance'? Software QA involves the entire software development PROCESS - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with. 50. How does a client/server environment affect testing? Client/server applications can be quite complex due to the multiple dependencies among clients, data communications, hardware, and servers. Thus testing requirements can be extensive. When time is limited (as it usually is) the focus should be on integration and system testing. Additionally, load/stress/performance testing may be useful in determining client/server application limitations and capabilities. There are commercial tools to assist with such testing. 15. What is 'Software 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. 52.How is testing affected by object-oriented designs? Well-engineered object-oriented design can make it easier to trace from code to internal design to functional design to requirements. While there will be little affect on black box testing (where an understanding of the internal design of the application is unnecessary), white-box testing can be oriented to the application's objects. If the application was welldesigned this can simplify test design. 53.What is Extreme Programming and what's it got to do with testing? Extreme Programming (XP) is a software development approach for small teams on risk-prone projects with unstable requirements. It was created by Kent Beck who described the approach in his book 'Extreme Programming Explained .Testing ('extreme testing') is a core aspect of Extreme Programming. Programmers are expected to write unit and functional test code first - before the application is developed. Test code is under source control along with the rest of the code. Customers are expected to be an integral part of the project team and to help develope scenarios for acceptance/black box testing. Acceptance tests are preferably automated, and are modified and rerun for each of the frequent development iterations. QA and test personnel are also required to be an integral part of the project team. Detailed requirements documentation is not used, and frequent re-scheduling, re-estimating, and re-prioritizing is expected. 54.What are all the basic strategies for dealing with new code? ? Start with obvious and simple test ? Test each function sympathetically ? Test broadly before deeply ? Look for more powerful tests ? Expand your scope ? Do some freestyle exploratory testing 55.What is acceptance testing? Its a formal testing conducted to determine whether a system satisfies its acceptance criteria -enables an end user to determine whether or not to accept the system 56.What is functionality testing? Its a mandatory part in black box testing and is also known as requirement testing. During this testing testing team will validates the correctness of every functionality in terms of behavioral coverage,calculation coverage,input domain coverage and back end coverage. 57.What is GUI testing?

This testing is done against the windows compliance standards such as each windows present in the application,text boxes,options(radio buttons),check boxes,command buttons,drop down list boxes. 58.What is Retesting? Testing of a particular test cases to check whether the bug is fixed or not. 59.What is the difference between functional testing and functionality testing? Functional testing is a mandatory part in black box testing. Functionality testing is also known as requirement testing,during this test testing validates the correctness of every functionality in terms of behavioural coverage,calculation coverage,input domain coverage,back end coverage 60. How to log defects in manual testing? When you find a bug u have to post it in your company's issue tracker(as discovery or open status).While post the bug do not forget to mention the summary,description,build version,screen shot,step to reproduce,severity and reproducibility of the bug. 61. When to use regression testing and retesting? Retesting:In retesting we are going to check whether the bug is fixed or not. Regression: It means after getting conformation the bug is fixed,we are going to check the fixation is going to create any problems in the application or not. 62. What are all the main actions which will be taken by the project manager for testing a product? 1) Assess risks for the project as a whole 2) Assess the risk associated with the testing sub-project 3) Lay out criteria for important milestones and stick to them 4) Develop a project plan for the testing sub project 5) Track testing progress against the plan 63. What are all the important factors want to be trade-off when building a product? 1. Time to market 2. Cost to market 3. Reliability of delivered product 4. Feature set 64. What are all the favorite risks will be arised during the project plan? ? Are there fixed dates that must be met for milestones or components of the product? ? How likely is it that the test group will get the software on schedule? ? What technical areas of the product do the current members of the test group not understand? ? Which areas of the program must be well tested? ? Are there regulatory or legal requirements that the product must meet? 65. What is Guerilla testing? It involves ad hoc testing done by some one who is skilled at finding errors on the fly. It is one person's best shot at finding bugs. This approach is typically time limited. 66. What is combinatorial testing? The most comprehensive approach to testing program-input combinations is referred to as combinatorial testing. In this testing all possible combinations of the test data values selected for the program inputs are tested