Explore topic-wise InterviewSolutions in .

• The waterfall model is the oldest and the most widely used paradigm.
• However, many projects rarely follow its sequential flow. This is due to the inherent problems associated with its rigid format, Namely.
• It only incorporates iteration indirectly, THUS changes may cause considerable confusion as the project progresses.
• As The client usually only has a vague idea of exactly what is required from the SOFTWARE product, this WM has DIFFICULTY accommodating the natural UNCERTAINTY that exists at the beginning of the project.
• The customer only sees a working version of the product after it has been CODED. This may result in disaster if any undetected problems are precipitated to this stage.

• TESTING is inherent to every phase of the waterfall model.
• It is an enforced disciplined approach.
• It is documentation driven, that is, documentation is PRODUCED at every STAGE.

Time spent early in the software production cycle can lead to greater economy at LATER stages. It has been shown that a bug FOUND in the early stages (such as REQUIREMENTS specification or design) is cheaper in terms of money, effort and time, to fix than the same bug found later on in the process. ([McConnell 1996], p. 72, estimates that a requirements defect that is left undetected until construction or maintenance will cost 50 to 200 times as much to fix as it would have cost to fix at requirements time.) To take an extreme example, if a PROGRAM design turns out to be impossible to implement, it is easier to fix the design at the design stage than to realize months later, when program components are being integrated, that all the work done so far has to be scrapped because of a broken design.

Time spent early in the software production cycle can lead to greater economy at later stages. It has been shown that a bug found in the early stages (such as requirements specification or design) is cheaper in terms of money, effort and time, to fix than the same bug found later on in the process. ([McConnell 1996], p. 72, estimates that a requirements defect that is left undetected until construction or maintenance will cost 50 to 200 times as much to fix as it would have cost to fix at requirements time.) To take an extreme example, if a program design turns out to be impossible to implement, it is easier to fix the design at the design stage than to realize months later, when program components are being integrated, that all the work done so far has to be scrapped because of a broken design.

The waterfall model phases are followed in order:
1. REQUIREMENTS specification. 
2. Design. 
3. Construction (AKA implementation or CODING). 
4. INTEGRATION. 
5. Testing and debugging (AKA VALIDATION). 
6. Installation. 
7. Maintenance.

The waterfall model phases are followed in order:
1. Requirements specification. 
2. Design. 
3. Construction (AKA implementation or coding). 
4. Integration. 
5. Testing and debugging (AKA Validation). 
6. Installation. 
7. Maintenance.

The WATERFALL model derives its NAME DUE to the cascading effect from one phase to the other. In this model each phase well defined starting and ENDING point, with IDENTIFIABLE deliveries to the next phase.

The waterfall model derives its name due to the cascading effect from one phase to the other. In this model each phase well defined starting and ending point, with identifiable deliveries to the next phase.

BUTTERFLIES are composed of three pieces — TWO wings and a body. Each part REPRESENTS a piece of software testing, as under.

• Test ANALYSIS.
• Test DESIGN.
• Test Execution.

Butterflies are composed of three pieces — two wings and a body. Each part represents a piece of software testing, as under.

From the TESTING point of view, all of the models are deficient in various ways:

• The TEST activities first start after the IMPLEMENTATION. The connection between the various test stages and the basis for the test is not clear.
• The TIGHT link between test, debug and change tasks during the test phase is not clear.

From the testing point of view, all of the models are deficient in various ways:

Many of the PROCESS models currently used can be more generally connected by the ‘V’ model where the ‘V’ describes the graphical arrangement of the individual phases. The ‘V’ is also a synonym for VERIFICATION and Validation.
By the ordering of ACTIVITIES in time sequence and with abstraction levels the connection between development and test activities becomes clear. Oppositely LAYING activities complement one another (i.e.) server as a base for test activities. For example, the system test is CARRIED out on the basis of the results specification phase.

Many of the process models currently used can be more generally connected by the ‘V’ model where the ‘V’ describes the graphical arrangement of the individual phases. The ‘V’ is also a synonym for Verification and Validation.
By the ordering of activities in time sequence and with abstraction levels the connection between development and test activities becomes clear. Oppositely laying activities complement one another (i.e.) server as a base for test activities. For example, the system test is carried out on the basis of the results specification phase.

The WATERFALL model is a sequential software development process, in which progress is SEEN as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, ANALYSIS, Design (validation), CONSTRUCTION, Testing and MAINTENANCE.

The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design (validation), Construction, Testing and Maintenance.

Top-down and bottom-up are strategies of information processing and KNOWLEDGE ordering, mostly involving SOFTWARE, but also other humanistic and scientific theories. In PRACTICE, they can be seen as a style of thinking and teaching. In many cases top-down is used as a SYNONYM of ANALYSIS or decomposition, and bottom-up of synthesis.

Top-down and bottom-up are strategies of information processing and knowledge ordering, mostly involving software, but also other humanistic and scientific theories. In practice, they can be seen as a style of thinking and teaching. In many cases top-down is used as a synonym of analysis or decomposition, and bottom-up of synthesis.

In the Spiral Model, a cyclical and prototyping view of software DEVELOPMENT is shown. Test are EXPLICITLY mentioned (risk analysis, validation of requirements and of the development) and the test phase is divided into stages. The test activities include MODULE, integration and ACCEPTANCE tests. However, in this model the testing also follows the coding. The exception to this is that the test plan should be constructed after the design of the system. The spiral model also IDENTIFIES no activities associated with the removal of defects.

In the Spiral Model, a cyclical and prototyping view of software development is shown. Test are explicitly mentioned (risk analysis, validation of requirements and of the development) and the test phase is divided into stages. The test activities include module, integration and acceptance tests. However, in this model the testing also follows the coding. The exception to this is that the test plan should be constructed after the design of the system. The spiral model also identifies no activities associated with the removal of defects.

The INFORMATION flow defined as part of the business modeling phase is refined into a set of DATA objects that are needed to support the business. The characteristics (called ATTRIBUTES) of each OBJECT are identified and the relationships between these objects are defined.

The information flow defined as part of the business modeling phase is refined into a set of data objects that are needed to support the business. The characteristics (called attributes) of each object are identified and the relationships between these objects are defined.

Test plan is a document that contains the scope, approach, test design and test strategies. It INCLUDES the following:
1. Test case identifier.
2. Scope.
3. Features to be tested.
4. Features not to be tested.
5. Test strategy.
6. Test Approach.
7. Test Deliverables.
8. Responsibilities.
9 . Staffing and TRAINING.
10. Risk and Contingencies.
11. APPROVAL.

While A test case is a noted/documented set of steps/activities that are carried out or executed on the software in order to confirm its functionality/behavior to certain set of inputs.

Test plan is a document that contains the scope, approach, test design and test strategies. It includes the following:
1. Test case identifier.
2. Scope.
3. Features to be tested.
4. Features not to be tested.
5. Test strategy.
6. Test Approach.
7. Test Deliverables.
8. Responsibilities.
9 . Staffing and Training.
10. Risk and Contingencies.
11. Approval.

While A test case is a noted/documented set of steps/activities that are carried out or executed on the software in order to confirm its functionality/behavior to certain set of inputs.

Test Plan is a document which is prepared with the details of the testing priority. A test Plan generally includes:

1. Objective of Testing
2. Scope of Testing
3. Reason for testing
4. Timeframe
5. Environment
6. Entrance and EXIT criteria
7. Risk FACTORS involved
8. DELIVERABLES.

Test Plan is a document which is prepared with the details of the testing priority. A test Plan generally includes:

1. Prepare the AUTOMATION Test PLAN
2. Identify the scenario
3. Record the scenario
4. Enhance the scripts by INSERTING check points and Conditional LOOPS
5. Incorporated Error Handler
6. Debug the script
7. FIX the issue
8. Rerun the script and report the result.

1. Prepare the automation Test plan
2. Identify the scenario
3. Record the scenario
4. Enhance the scripts by inserting check points and Conditional Loops
5. Incorporated Error Handler
6. Debug the script
7. Fix the issue
8. Rerun the script and report the result.

There can be some FUNCTIONALITY which cannot be tested in an automated tool so we MAY have to do it manually. therefore MANUAL testing can never be replaced. (We can write the SCRIPTS for negative testing also but it is hectic task).When we talk about real ENVIRONMENT we do negative testing manually.

There can be some functionality which cannot be tested in an automated tool so we may have to do it manually. therefore manual testing can never be replaced. (We can write the scripts for negative testing also but it is hectic task).When we talk about real environment we do negative testing manually.

choosing of a tool defends on many things .
1. APPLICATION to be tested.
2. Test environment.
3. Scope and limitation of the tool.
4. Feature of the tool.
5. Cost of the tool.
6. Whether the tool is compatible with your application which means tool should be able to INTERACT with your application.
7. EASE of use.

choosing of a tool defends on many things .
1. Application to be tested.
2. Test environment.
3. Scope and limitation of the tool.
4. Feature of the tool.
5. Cost of the tool.
6. Whether the tool is compatible with your application which means tool should be able to interact with your application.
7. Ease of use.

We need to concentrate on the features of the TOOLS and how this COULD be BENEFICIAL for our PROJECT. The additional NEW features and the enhancements of the features will also help.

We need to concentrate on the features of the tools and how this could be beneficial for our project. The additional new features and the enhancements of the features will also help.

FAST ,RELIABLE,COMPREHENSIVE,REUSABLE.

FAST ,RELIABLE,COMPREHENSIVE,REUSABLE.

1. The choice of automation TOOL for certain TECHNOLOGIES.
2. Wrong SET of test AUTOMATED.

1. The choice of automation tool for certain technologies.
2. Wrong set of test automated.

Testing activities start from the elaboration phase. The VARIOUS testing activities are preparing the TEST plan, Preparing test cases, Execute the test CASE, Log the bug, validate the bug & take appropriate action for the bug, Automate the test cases.

Testing activities start from the elaboration phase. The various testing activities are preparing the test plan, Preparing test cases, Execute the test case, Log the bug, validate the bug & take appropriate action for the bug, Automate the test cases.

Automate all the HIGH priority test CASES which needs to be executed as a part of regression testing for each BUILD CYCLE.

Automate all the high priority test cases which needs to be executed as a part of regression testing for each build cycle.

The common PROBLEMS are:
1. Maintenance of the old script when there is a feature CHANGE or enhancement.
2. The change in technology of the APPLICATION will affect the old SCRIPTS.

The common problems are:
1. Maintenance of the old script when there is a feature change or enhancement.
2. The change in technology of the application will affect the old scripts.

5 types of scripting techniques:

• LINEAR
• Structured
• SHARED
• DATA DRIVEN
• Key Driven

5 types of scripting techniques:

1. PROPER code GUIDING STANDARDS.
2. Standard format for defining functions, exception handler etc.
3. COMMENTS for functions.
4. Proper errorhandling mechanisms.
5. The appropriate synchronization techniques.

1. Proper code guiding standards.
2. Standard format for defining functions, exception handler etc.
3. Comments for functions.
4. Proper errorhandling mechanisms.
5. The appropriate synchronization techniques.

Testing tools for regression and load/stress testing for regression testing like, QTP, load runner, RATIONAL robot, WINRUNNER, silk, test COMPLETE, Astra are AVAILABLE in the market. For defect tracking BugZilla, Test Runner are available.

Testing tools for regression and load/stress testing for regression testing like, QTP, load runner, rational robot, winrunner, silk, test complete, Astra are available in the market. For defect tracking BugZilla, Test Runner are available.

As I know it, TEST CASE DESIGN is about formulating the steps to be carried out to verify something about the application under test. And this cannot be automated. However, I agree that the PROCESS of putting the test RESULTS into the excel sheet.

As I know it, test case design is about formulating the steps to be carried out to verify something about the application under test. And this cannot be automated. However, I agree that the process of putting the test results into the excel sheet.

Hard-to-create ENVIRONMENTS like “out of memory”, “invalid input/reply”, and “corrupt REGISTRY entries” MAKE applications behave poorly and existing automated tools can’t force these condition - they simply TEST your application in “NORMAL” environment.

Hard-to-create environments like “out of memory”, “invalid input/reply”, and “corrupt registry entries” make applications behave poorly and existing automated tools can’t force these condition - they simply test your application in “normal” environment.

1.Good LOGIC for PROGRAMMING.
2. ANALYTICAL SKILLS.
3.Pessimestic in Nature.

1.Good Logic for programming.
2. Analytical skills.
3.Pessimestic in Nature.

1. The inability of WINRUNNER to identify the third party control like infragistics controls.
2. The CHANGE of the location of the table object will CAUSE object not found error.
3. The inability of the winrunner to execute the script against multiple langauges.

1. The inability of winrunner to identify the third party control like infragistics controls.
2. The change of the location of the table object will cause object not found error.
3. The inability of the winrunner to execute the script against multiple langauges.

Testing tools can be used for :

• Sanity tests(which is repeated on every BUILD).
• stress/Load tests(U simulate a LARGE no of USERS,which is manually IMPOSSIBLE).
• REGRESSION tests(which are done after every code change).

Testing tools can be used for :

To find this, select the suite of tests which are most IMPORTANT for your APPLICATION. First RUN them with automated tool. Next SUBJECT the same tests to careful MANUAL testing. If the results are coinciding you can say your testing tool has been performing.

To find this, select the suite of tests which are most important for your application. First run them with automated tool. Next subject the same tests to careful manual testing. If the results are coinciding you can say your testing tool has been performing.

We can create a textfile in a CERTAIN LOCATION, and update the auto generated value each time we run the TEST and compare the currently generated value with the previous one will be one SOLUTION.

We can create a textfile in a certain location, and update the auto generated value each time we run the test and compare the currently generated value with the previous one will be one solution.

We can USE VERIFICATION points(rational Robot) to validate the fields .Ex.Using OBJECTDATA,objectdata properties VP we can validate fields.

We can use Verification points(rational Robot) to validate the fields .Ex.Using objectdata,objectdata properties VP we can validate fields.

No. The TESTING Tools will be in the AMBIGUITY to determine which BROWSER is opened by which TOOL.

No. The Testing Tools will be in the ambiguity to determine which browser is opened by which tool.

Configuration MANAGEMENT is a process to control and document any CHANGES made during the LIFE of a project. Revision control, Change Control, and Release Control are IMPORTANT aspects of Configuration Management.

Configuration management is a process to control and document any changes made during the life of a project. Revision control, Change Control, and Release Control are important aspects of Configuration Management.

The basic DIFFERENCE in webtesting is here we have to test for URL's coverage and links coverage. Using WinRunner we can conduct webtesting. But we have to make SURE that Webtest option is selected in "Add in Manager". Using WR we cannot test XML objects.

The basic difference in webtesting is here we have to test for URL's coverage and links coverage. Using WinRunner we can conduct webtesting. But we have to make sure that Webtest option is selected in "Add in Manager". Using WR we cannot test XML objects.

If SRS is not there we can perform EXPLORATORY testing. In Exploratory testing the BASIC MODULE is EXECUTED and depending on its results, the next plan is executed.

If SRS is not there we can perform Exploratory testing. In Exploratory testing the basic module is executed and depending on its results, the next plan is executed.

By using ENDURANCE Testing . Endurance Testing MEANS CHECKING for memory leaks or other problems that may occur with prolonged EXECUTION.

By using Endurance Testing . Endurance Testing means checking for memory leaks or other problems that may occur with prolonged execution.

QUALITY assurance involves the entire software development PROCESS and TESTING involves OPERATION of a system or application to evaluate the results under certain conditions. QA is ORIENTED to prevention and Testing is oriented to detection.

Quality assurance involves the entire software development process and testing involves operation of a system or application to evaluate the results under certain conditions. QA is oriented to prevention and Testing is oriented to detection.

Memory leaks means INCOMPLETE deallocation - are bugs that happen very often. Buffer overflow means data sent as INPUT to the server that overflows the BOUNDARIES of the input area, thus CAUSING the server to misbehave. Buffer overflows can be used.

Memory leaks means incomplete deallocation - are bugs that happen very often. Buffer overflow means data sent as input to the server that overflows the boundaries of the input area, thus causing the server to misbehave. Buffer overflows can be used.

Stress testing means increasing the load ,and checking the PERFORMANCE at each LEVEL. Load testing means at a time GIVING more load by the EXPECTATION and checking the performance at that level. Volume testing means first we have to apply initial.

Stress testing means increasing the load ,and checking the performance at each level. Load testing means at a time giving more load by the expectation and checking the performance at that level. Volume testing means first we have to apply initial.

The SPECIFICATION of tests that are conducted from the end-user perspective. Use cases tend to FOCUS on operating software as an end-user would CONDUCT their day-to-day ACTIVITIES.

The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.

A COMPANY COMMITMENT to develop a process that achieves HIGH quality product and customer SATISFACTION.

A company commitment to develop a process that achieves high quality product and customer satisfaction.

An approach to INTEGRATION testing where the COMPONENT at the TOP of the component hierarchy is tested first, with lower level COMPONENTS being simulated by stubs. Tested components are then used to test lower level components. The PROCESS is repeated until the lowest level components have been tested.

An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.

Computer programs USED in the TESTING of a SYSTEM, a COMPONENT of the system, or its documentation.

Computer programs used in the testing of a system, a component of the system, or its documentation.

A collection of tests used to validate the behavior of a product. The SCOPE of a Test Suite varies from organization to organization. There may be SEVERAL Test Suites for a particular product for example. In most cases HOWEVER a Test Suite is a high LEVEL CONCEPT, grouping together hundreds or thousands of tests related by what they are intended to test.

A collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.

A document specifying the TEST approach for a software FEATURE or combination or FEATURES and the inputs, predicted results and execution conditions for the associated TESTS.

A document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests.

Commonly USED to refer to the INSTRUCTIONS for a particular TEST that will be carried out by an AUTOMATED test tool.

Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool.

A DOCUMENT PROVIDING DETAILED instructions for the EXECUTION of one or more test cases.

A document providing detailed instructions for the execution of one or more test cases.