TESTING INTERVIEW PREPARATION BY CHETAN

What is Software Testing ?
What is the Purpose of Testing ?
What types of testing do testers perform ?
What is the Outcome of Testing ?
What kind of testing have you done ?
What is the need for testing ?
How do you determine, what to be tested ?
How do you go about testing a project ?
What is the Initial Stage of testing ?
What are the various levels of testing ?
What are the Minimum requirements to start testing ?
What is test metrics ?
Why do you go for White box testing, when Black box testing is available ?
What are the entry criteria for Automation testing ?
When to start and Stop Testing ?
What is Quality ?
What is quality assurance ?
What is quality control ?
What is verification ?
What is validation ?
What is SDLC and TDLC ?
What are the Qualities of a Tester ?
What is the relation ship between Quality & Testing ?
What are the types of testing you know and you experienced ?
After completing testing, what would you deliver to the client ?
What is a Test Bed ?
Why do you go for Test Bed ?
What is a Data Guidelines ?
What is Severity and Priority and who will decide what ?
Can Automation testing replace manual testing ? If it so, how ?
What is a test case ?
What is a test condition ?
What is the test script ?
What is the test data ?
What is an Inconsistent bug ?
What is the difference between Re-testing and Regression testing ?
What are the different types of testing techniques ?
What are the different types of test case techniques ?
What are the risks involved in testing ?
Differentiate Test bed and Test Environment ?
What ifs the difference between defect, error, bug, failure, fault ?What is the difference between quality and testing ?
What is the difference between White & Black Box Testing ?
What is the difference between Quality Assurance and Quality Control ?
What is the difference between Testing and debugging ?
What is the difference between bug and defect ?
What is the difference between verification and validation ?
What is the difference between functional spec. and Business requirement specification ?
What is the difference between unit testing and integration testing ?
What is the diff between Volume & Load ?

What's Ad Hoc Testing ?
A testing where the tester tries to break the software by randomly trying functionality of software.
What's the Accessibility Testing ?
Testing that determines if software will be usable by people with disabilities.
What's the Alpha Testing ?
The Alpha Testing is conducted at the developer sites and in a controlled environment by the end user of the software
What's the Beta Testing ?
Testing the application after the installation at the client place.
What is Component Testing ?
Testing of individual software components (Unit Testing).
What's Compatibility Testing ?
In Compatibility testing we can test that software is compatible with other elements of system.
What is Concurrency Testing ?
Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.
What is Conformance Testing ?
The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard.
What is Context Driven Testing ?
The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.
What is Data Driven Testing ?
Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.
What is Conversion Testing ?
Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
What is Dependency Testing ?
Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.
What is Depth Testing ?
A test that exercises a feature of a product in full detail.
What is Dynamic Testing ?
Testing software through executing it. See also Static Testing.
What is Endurance Testing ?
Checks for memory leaks or other problems that may occur with prolonged execution.
What is End-to-End testing ?
Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
What is Exhaustive Testing ?
Testing which covers all combinations of input values and preconditions for an element of the software under test.
What is Gorilla Testing ?
Testing one particular module, functionality heavily.
What is Installation Testing ?
Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.
What is Localization Testing ?
This term refers to making software specifically designed for a specific locality.
What is Loop Testing ?
A white box testing technique that exercises program loops.
What is Mutation Testing ?
Mutation testing is a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources
What is Monkey Testing ?
Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.
What is Positive Testing ?
Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing.
What is Negative Testing ?
Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.
What is Path Testing ?
Testing in which all paths in the program source code are tested at least once.
What is Performance Testing ?
Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".
What is Ramp Testing ?
Continuously raising an input signal until the system breaks down.
What is Recovery Testing ?
Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.
What is the Re-testing testing ?
Retesting- Again testing the functionality of the application.
What is the Regression testing ?
Regression- Check that change in code have not effected the working functionality
What is Sanity Testing ?
Brief test of major functional elements of a piece of software to determine if its basically operational.
What is Scalability Testing ?
Performance testing focused on ensuring the application under test gracefully handles increases in work load.
What is Security Testing ?
Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.
What is Stress Testing ?
Stress testing is a form of testing that is used to determine the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results.
What is Smoke Testing ?
A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.
What is Soak Testing ?
Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.
What's the Usability testing ?
Usability testing is for user friendliness.
What's the User acceptance testing ?
User acceptance testing is determining if software is satisfactory to an end-user or customer.
What's the Volume Testing ?
We can perform the Volume testing, where the system is subjected to large volume of data.

Topic: Difference between Stub Testing and Driver Testing Posted: 26Mar2008 at 1:31am stub testing: In top down approach,a core module is developed.to test that core module, small dummy modules r used.so stubs r small dummy modules that test the core module.Driver testing:in bottom up approach, small modules r developed.to test them a dummy core module called driver is developed.These are the different types of integration techniquesStub: When u approached top down approach you have to use stubs. ie when testing the module from top level hierachy to bottom level hierachyDEF: Stub is nothing but a calling function for the function to be tested.Driver: When u approached bottom up approach you have to use driver. ie when testing the module from bottom level hierachy to the top level hierachyDriver: Driver will act as a dummy program for the fucntion to be testedDriver: test tool that replaces a component that takes care of the control or the calling of a component or systemStub: special purpose implementation of a software component that calls or is otherwise dependent on it . it replaces a called component

Test your Software Testing knowledge. Take this mock test
Verify your answers at the answer page provided at the bottom of this test page.
1. Verification is: a. Checking that we are building the right systemb. Checking that we are building the system rightc. Performed by an independent test teamd. Making sure that it is what the user really wants
2. A regression test:a. Will always be automatedb. Will help ensure unchanged areas of the software have not been affectedc. Will help ensure changed areas of the software have not been affectedd. Can only be run during user acceptance testing
3. If an expected result is not specified then: a. We cannot run the testb. It may be difficult to repeat the testc. It may be difficult to determine if the test has passed or failedd. We cannot automate the user inputs
4. Which of the following could be a reason for a failure1) Testing fault2) Software fault3) Design fault4) Environment Fault5) Documentation Faulta. 2 is a valid reason; 1,3,4 & 5 are notb. 1,2,3,4 are valid reasons; 5 is notc. 1,2,3 are valid reasons; 4 & 5 are notd. All of them are valid reasons for failure
5. Test are prioritized so that: a. You shorten the time required for testingb. You do the best testing in the time availablec. You do more effective testingd. You find more faults
6. Which of the following is not a static testing technique a. Error guessingb. Walkthroughc. Data flow analysisd. Inspections
7. Which of the following statements about component testing is not true?a. Component testing should be performed by developmentb. Component testing is also know as isolation or module testingc. Component testing should have completion criteria plannedd. Component testing does not involve regression testing
8. During which test activity could faults be found most cost effectively? a. Executionb. Designc. Planningd. Check Exit criteria completion
9. Which, in general, is the least required skill of a good tester?a. Being diplomaticb. Able to write softwarec. Having good attention to detaild. Able to be relied on
10. The purpose of requirement phase is a. To freeze requirementsb. To understand user needsc. To define the scope of testingd. All of the above
11. The process starting with the terminal modules is called -a. Top-down integrationb. Bottom-up integrationc. None of the aboved. Module integration
12. The inputs for developing a test plan are taken from a. Project planb. Business planc. Support pland. None of the above
13. Function/Test matrix is a type of a. Interim Test reportb. Final test reportc. Project status reportd. Management report
14. Defect Management process does not includea. Defect preventionb. Deliverable base-liningc. Management reportingd. None of the above
15. What is the difference between testing software developed by contractor outside your country, versus testing software developed by a contractor within your country?a. Does not meet people needsb. Cultural differencec. Loss of control over reallocation of resourcesd. Relinquishments of control
16. Software testing accounts to what percent of software development costs?a. 10-20b. 40-50c. 70-80d. 5-10
17. A reliable system will be one that:a. Is unlikely to be completed on scheduleb. Is unlikely to cause a failurec. Is likely to be fault-freed. Is likely to be liked by the users
18. How much testing is enough a. This question is impossible to answerb. The answer depends on the risks for your industry, contract and special requirementsc. The answer depends on the maturity of your developersd. The answer should be standardized for the software development industry
19. Which of the following is not a characteristic for Testability? a. Operabilityb. Observabilityc. Simplicityd. Robustness
20. Cyclomatic Complexity method comes under which testing method. a. White boxb. Black boxc. Green boxd. Yellow box
21. Which of these can be successfully tested using Loop Testing methodology? a. Simple Loopsb. Nested Loopsc. Concatenated Loopsd. All of the above
22. To test a function, the programmer has to write a ______, which calls the function and passes it test data.a. Stubb. Driverc. Proxyd. None of the above
23. Equivalence partitioning is: a. A black box testing technique used only by developersb. A black box testing technique than can only be used during system testingc. A black box testing technique appropriate to all levels of testingd. A white box testing technique appropriate for component testing
24. When a new testing tool is purchased, it should be used first by: a. A small team to establish the best way to use the toolb. Everyone who may eventually have some use for the toolc. The independent testing teamd. The vendor contractor to write the initial scripts
25. Inspections can find all the following except a. Variables not defined in the codeb. Spelling and grammar faults in the documentsc. Requirements that have been omitted from the design documentsd. How much of the code has been covered
Answers:
1)- b 2)- b 3)- c 4)- d 5)- b 6)- a 7)- d 8 )- c 9) - b 10) - d 11) -b 12) - a 13) - c 14) - b 15) - b 16) - b 17) - b 18) - b 19) - d 20) - a 21) - d
What is the difference between Smoke testing and Sanity testing?
Smoke testing is after build releasing we will test high level functionalities working or not. Sanity testing is we will test all functionalities working properly or not.
Sanity Testing: Teswt Engineer cover basic functionality of the buld to validate " whether the build is stable for complete testing or not"
Smoke Testing: It is an extra shakeup in sanity process.
In this tesing, testing team rejects build with specific reasons where that build is not working
sanity testing is an Initial effort to check whether the application can be tested further without any interruption. Basic gui functionality,connectivity to database are concentrated here.
Smoke Testing:Its confusing question and answer too.
It covers most crucial functions of the application..
testing carried out check whether most crucial functions of the application work fine or not? dont bother about the in-depth coverage of each testset.
what are most crucial functions in the build, you should know it before coming to testing phase. or your manager will write a seperate high-level testcase for that.
Sanity Testing:-Tester conducts the Sanity test to ensure the stability of the application build.Tester finds weather the application build is stable for complete application or not.
Smoke Testing:-It covers the major functionality of the application without bothering with finer details.
Conceptually Smoke testing and sanity testing both are same,but perceptionally these are different.Smoke testing:Smoke testing is conducted with negative perception,it is the testing in which all the functionaliteis are avaliable are not is tested , to proceed for further overall testing.Sanity testing: This is also test for to check whether all the functionaliteis are available are not.But this testing is conducted with positive perception.
Smoke Sanity
1 Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested. A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep. 2 A smoke test is scripted--either using a written set of tests or an automated test A sanity test is usually unscripted. 3 A Smoke test is designed to touch every part of the application in a cursory way. It's is shallow and wide. A Sanity test is used to determine a small section of the application is still working after a minor change. 4 Smoke testing will be conducted to ensure whether the most crucial functions of a program work, but not bothering with finer details. (Such as build verification). Sanity testing is a cursory testing; it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing. 5 Smoke testing is normal health check up to a build of an application before taking it to testing in depth.
sanity testing is to verify whether requirements are met or not,
checking all features breadth-first.