1 Brought to you by: http://way2mca.

com

Some of Viva questions for software testing 1 What is White box testing/unit testing? It is done by developers. It typically involves in coding. In this Testing developers concentrates on internal structure of the program and justifies whether that program is correct or not. 2 Difference between Black and White box testing? 3 What are the roles of glass-box and black-box testing tools? 4 What is Black box testing? Black box testing is done by the professional testing team.This does not require knowledge of internal coding of the application. Testing the application against the functionality of the application with out the knowledge of internal coding of the software. 5 What is Integration testing? 6 What knowledge you require to do white box, integration and black box testing? For white box testing you need to understand the internals of the module like data structures and algorithms and have access to the source code and for black box testing only understanding/functionality of the application. 7 What is Regression testing? Regression testing: Re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.. 8 Why do we do regression testing? In any application new functionalities can be added so the application has to be tested to see whether the added functionalities have affected the existing functionalities or not. Here instead of retesting all the existing functionalities baseline scripts created for these can be rerun and tested. 9 How do we regression testing?

2 Brought to you by: http://way2mca.com

Various automation-testing tools can be used to perform regression testing like WinRunner, Rational Robot and Silk Test. 10 What are positive scenarios? Testing to see whether the application is doing what it is supposed to do. 11 What are negative scenarios? Testing to see whether the application is not doing what it is not suppose to do. 12 What is the difference between regression automation tool and performance automation tool? Regression testing tools capture test and play them back at a later time. The capture and playback feature is fundamental to regression testing. Performance testing tool determine the load a server can handle. And must have feature to stimulate many users from one machine, scheduling and synchronize different users, able to measure the network load under different number of simulated users. 13 What is the difference between exception and validation testing? Validation testing aims to demonstrate that the software functions in a manner that can be reasonably expected by the customer. Testing the software in conformance to the Software Requirements Specifications. Exception testing deals with handling the exceptions (unexpected events) while the AUT is run. Basically this testing involves how to change the control flow of the AUT when an exception arises. 14 What is user acceptance testing? It is also called as Beta Testing. Once System Testing is done and the system seems stable to the developers and testers, system engineers usually invite the end users of the software to see if they like the software. If the users like the software the way it is then software will be delivered to the user. Otherwise necessary changes will be made to the software and software will pass through all phases of testing again. 15 What is manual testing and what is automated testing? Manual testing involves testing of software application by manually performing the actions on the AUT based on test plans.

3 Brought to you by: http://way2mca.com

Automated testing involves testing of a software application by performing the actions on the AUT by using automated testing tool (such as Quick Test Professional, WinRunner, LoadRunner, Rational Root) based on test plans

16 What is smoke testing? The smoke test must evolve as the system evolves. At first, the smoke test will probably test something simple, such as whether the system can say, "Hello, World." As the system develops, the smoke test will become more thorough. The first test might take a matter of seconds to run; as the system grows, the smoke test can grow to 30 minutes, an hour, or more. 17 What is soak testing? The software system will be run for a total of 14 hours continuously. If the system is a control system, it will be used to continuously move each of the instrument mechanisms during this time. Any other system will be expected to perform its intended function continuously during this period. The software system must not fail during this period. 18 What is stress testing, performance testing, Security testing, Recovery testing and volume testing. Stress testing: Testing the system if it can handle peak usage period loads that result from large number of simultaneous users, transactions or devices. Monitoring should be performed for throughput and system stability. Performance Testing: Testing the system whether the system functions are being performed in an acceptable timeframe under simultaneous user load. Timings for both read and update transactions should be gathered to determine whether. This should be done stand-alone and then in a multi-user environment to determine the transaction throughput. Security Testing: Testing the system for its security from unauthorized use and unauthorized data access. Recovery Testing: Testing a system to see how it responds to errors and abnormal conditions, such as system crash, loss of device, communications, or power. Volume Testing: Testing to the system to determine if it can correctly process large volumes of data fed to the system. Systems can often respond unpredictably when large volume causes files to overflow and need extensions 19 What is MR?

4 Brought to you by: http://way2mca.com

MR is a Modification Request also known as Defect Report, a request to modify the program so that program does what it is supposed to do. 20 Why you write MR? MR is written for reporting problems/errors or suggestions in the software 21 What criteria you will follow to assign severity and due date to the MR? Defects (MR) are assigned severity as follows: Critical: show stoppers (the system is unusable) High: The system is very hard to use and some cases are prone to convert to critical issues if not taken care of. Medium: The system functionality has a major bug but is not too critical but needs to be fixed in order for the AUT to go to production environment. Low: cosmetic (GUI related) 22 You find a bug and the developer says "It's not possible" what do u do? I'll discuss with him under what conditions (working environment) the bug was produced. I'll provide him with more details and the snapshot of the bug. 23 How do you help developer to track the fault s in the software? By providing him with details of the defects which include the environment, test data, steps followed etc and helping him to reproduce the defect in his environment. 24 What is the role of a bug tracking system? Bug tracking system captures, manages and communicates changes, issues and tasks, providing basic process control to ensure coordination and communication within and across development and content teams at every step.. 25 What is a successful product? A bug free product, meeting the expectations of the user would make the product successful. 26 What Process/Methodologies are you familiar with?

5 Brought to you by: http://way2mca.com

Waterfall methodology Spiral methodology V Model Agile 27 What are CMM and CMMI? What is the difference? The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes. The Capability Maturity Model Integration (CMMI) provides the guidance for improving your organization's processes and your ability to manage the development, acquisition, and maintenance of products and services. 28 What was the test team hierarchy? Project Leader QA lead QA Analyst Tester 29 What are the different automation tools you know? Automation tools provided by Mercury Interactive Quick Test Professionl, WinRunner, LoadRunner; Rational Rational Robot; Segue- SilkTest. 30 How will you describe testing activities? Testing planning, scripting, execution, defect reporting and tracking, regression testing. 31 What is good code? These are some important qualities of good code

6 Brought to you by: http://way2mca.com

Cleanliness: Clean code is easy to read; this lets people read it with minimum effort so that they can understand it easily. Consistency: Consistent code makes it easy for people to understand how a program works; when reading consistent code; one subconsciously forms a number of assumptions and expectations about how the code works, so it is easier and safer to make modifications to it. Extensibility: General-purpose code is easier to reuse and modify than very specific code with lots of hard coded assumptions. When someone wants to add a new feature to a program, it will obviously be easier to do so if the code was designed to be extensible from the beginning. Correctness: Finally, code that is designed to be correct lets people spend less time worrying about bugs and more time enhancing the features of a program. 32 When should testing be stopped? This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are: Deadlines (release deadlines, testing deadlines, etc.) Test cases completed with certain percentage passed Test budget depleted Coverage of code/functionality/requirements reaches a specified point Bug rate falls below a certain level Beta or alpha testing period ends

33 When do you start developing your automation tests? First, the application has to be manually tested. Once the manual testing is over and baseline is established. 34 What are benefits of the test automation? 1. Fast

7 Brought to you by: http://way2mca.com

2. Reliable 3. Repeatable 4. Programmable 5. Comprehensive 6. Reusable 35 Describe some problems that you had with automation testing tools One of the problems with Automation tools is Object recognition 36 Can test automation improver test effectiveness? Yes, because of the advantages offered by test automation, which includes repeatability, consistency, portability and extensive reporting. 37 What is the main use of test automation? Regression Testing. Fast 38 Does automation replace manual testing? No, it does not. There could be several scenarios that cannot be automated or simply too complicated that manual testing would be easier and cost effective. Further automation tools have several constrains with regard the environment in which they run and IDEs they support. 39 What could wrong with automation testing? There are several things. For ex. Script errors can cause a genuine bug to go undetected or report a bug in the application when the bug does not actually exist. 40 What are good principles for test scripts? 1. Portable 2. Repeatable 3. Reusable

8 Brought to you by: http://way2mca.com

4. Maintainable 41 What type of document do you need for QA, QC and testing? Following is the list of documents required by QA and QC teams Business requirements SRS Use cases Test plan Test cases 42 What are the properties of a good requirement? Understandable, Clear, Concise, Total Coverage of the application 43 Where do you get your expected results? Requirement document 44 How do you go about testing a project? 1. Analyze user requirement documents and other documents like software specifications, design document etc. 2. Write master test plan which describe the scope, objective, strategy, risk/contingencies, resources 3. Write system test plan and detailed test cases 4. Execute test cases manually and compare actual results against expected results. 5. Identify mismatches, report defect to the development team using defect reporting tool. 6. Track defect, perform regression test to verify that defect is fixed and did not disturb other parts of the application.

9 Brought to you by: http://way2mca.com

7. Once all the defects are closed and application is stabilized, automate the test scripts for regression and performance testing. 45 What is configuration management? Tools used? Configuration management: helps teams control their day-to-day management of software development activities as software is created, modified, built and delivered. Comprehensive software configuration management includes version control, workspace management, build management, and process control to provide better project control and predictability 46 How did you use automating testing tools in your job? Automating testing tools are used for preparing and managing regression test scripts and load and performance tests. 47 Describe me the difference between validation and verification? Verification: typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings. Validation: typically involves actual testing and takes place after verifications are completed. The term 'IV & V' refers to Independent Verification and Validation

48 What is test Metrics? Test metrics contains following details:

Total test Test run Test passed Test failed Tests deferred Test passed the first time

49 What is the use of Metrics? Provide the accurate measurement of test coverage. 50 What is a pre-condition data?

10 Brought to you by: http://way2mca.com

Data required to setup in the system before the test execution. 51 What are the different documents in QA? Requirements Document, Test Plan, Test cases, Test Metrics, Task Distribution Diagrams ( Performance), Transaction Mix, User Profiles, Test Log, Test Incident Report, Test Summary Report 52 Who in the company is responsible for Quality? Both development and quality assurance departments are responsible for the final product quality. 53 What is Walkthrough? Walkthrough: A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required.. 54 What is inspection? Inspection: An inspection is more formalized than a 'walkthrough', typically with 3-8 people including a moderator, reader, and a recorder to take notes. The subject of the inspection is typically a document such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, not to fix anything. Attendees should prepare for this type of meeting by reading thru the document; most problems will be found during this preparation. The result of the inspection meeting should be a written report. Thorough preparation for inspections is difficult, painstaking work, but is one of the most cost effective methods of ensuring quality. 55 What is Software Review? Software Review: An evaluation technique that involves the bringing together a group of technical personnel to analyze a software artifact in order to improve its quality. Review types:

Informal: adhoc process, no planning, no structure Formal (Formal Technical Review): Follow a structured process Produce written report on artifact status Collect and analyze review metrics