Explore topic-wise InterviewSolutions in .

Yes, because both HELP DETECT FAULTS and improve QUALITY.

Yes, because both help detect faults and improve quality.

Inspection

Inspection

In experience-based techniques, people's KNOWLEDGE, skills and background are a prime contributor to the test CONDITIONS and test cases. The experience of both technical and business people is important, as they bring different perspectives to the test analysis and DESIGN process. Due to previous experience with similar systems, they may have insights into what could go WRONG, which is very USEFUL for testing.

In experience-based techniques, people's knowledge, skills and background are a prime contributor to the test conditions and test cases. The experience of both technical and business people is important, as they bring different perspectives to the test analysis and design process. Due to previous experience with similar systems, they may have insights into what could go wrong, which is very useful for testing.

Re-testing ensures the ORIGINAL fault has been removed; REGRESSION testing looks for UNEXPECTED SIDE effects.

Re-testing ensures the original fault has been removed; regression testing looks for unexpected side effects.

For EXAMPLE MEMORY LEAKS.

For example memory leaks.

The purpose of TEST COMPLETION criterion is to DETERMINE when to STOP testing.

The purpose of test completion criterion is to determine when to stop testing.

A NEGATIVE test is when you put in an invalid INPUT and receives errors. While a positive TESTING, is when you put in a valid input and expect some action to be completed in ACCORDANCE with the SPECIFICATION. 

A negative test is when you put in an invalid input and receives errors. While a positive testing, is when you put in a valid input and expect some action to be completed in accordance with the specification. 

After the SOFTWARE has CHANGED or when the environment has changed REGRESSION TESTING should be performed.

After the software has changed or when the environment has changed Regression testing should be performed.

Structure-based TESTING techniques (which are also dynamic rather than STATIC) use the internal structure of the software to derive test cases. They are commonly called 'white-box' or 'glass-box' techniques (implying you can see into the system) since they require knowledge of how the software is implemented, that is, how it works.

For example; a structural technique may be concerned with exercising loops in the software. DIFFERENT test cases may be derived to exercise the loop once, twice, and MANY times. This may be done regardless of the FUNCTIONALITY of the software.

Structure-based testing techniques (which are also dynamic rather than static) use the internal structure of the software to derive test cases. They are commonly called 'white-box' or 'glass-box' techniques (implying you can see into the system) since they require knowledge of how the software is implemented, that is, how it works.

For example; a structural technique may be concerned with exercising loops in the software. Different test cases may be derived to exercise the loop once, twice, and many times. This may be done regardless of the functionality of the software.

INTEGRATION LEVEL TESTING

Integration Level Testing

LOAD TESTING

Load Testing

SECURITY TESTING

Security Testing

During TEST PLANNING.

During test planning.

An INPUT or output ranges of values such that only one value in the RANGE BECOMES a TEST CASE.

An input or output ranges of values such that only one value in the range becomes a test case.

The moderator (or review leader) leads the review process. He or she determines, in co-operation with the author, the type of review, approach and the composition of the review team. The moderator performs the ENTRY check and the follow-up on the REWORK, in order to control the quality of the INPUT and output of the review process. The moderator also SCHEDULES the MEETING, disseminates documents before the meeting, coaches other team members, paces the meeting, leads possible discussions and stores the data that is collected.

The moderator (or review leader) leads the review process. He or she determines, in co-operation with the author, the type of review, approach and the composition of the review team. The moderator performs the entry check and the follow-up on the rework, in order to control the quality of the input and output of the review process. The moderator also schedules the meeting, disseminates documents before the meeting, coaches other team members, paces the meeting, leads possible discussions and stores the data that is collected.

Because they SHARE the AIM of IDENTIFYING defects but differ in the TYPES of defect they find.

Because they share the aim of identifying defects but differ in the types of defect they find.

1. Equivalence Partitioning.
2. USE Case Testing.
3. Data FLOW ANALYSIS.
4. Exploratory Testing.
5. Decision Testing.
6. INSPECTIONS.

Data Flow Analysis and Inspections are static; Equivalence Partitioning, Use Case Testing, Exploratory Testing and Decision Testing are DYNAMIC.

Data Flow Analysis and Inspections are static; Equivalence Partitioning, Use Case Testing, Exploratory Testing and Decision Testing are dynamic.

1. Provide developers and other parties with FEEDBACK about the PROBLEM to enable identification, isolation and correction as necessary.
2. Provide ideas for test process improvement.
3. Provide a vehicle for assessing TESTER competence.
4. Provide testers with a MEANS of TRACKING the quality of the system under test.

Random testing often known as monkey testing. In such type of testing data is generated randomly often USING a TOOL or AUTOMATED mechanism. With this randomly generated input the SYSTEM is tested and results are analysed accordingly. These testing are less reliable; hence it is normally used by the beginners and to see whether the system will hold up under adverse EFFECTS.

Random testing often known as monkey testing. In such type of testing data is generated randomly often using a tool or automated mechanism. With this randomly generated input the system is tested and results are analysed accordingly. These testing are less reliable; hence it is normally used by the beginners and to see whether the system will hold up under adverse effects.

Because TESTING EVERYTHING is not FEASIBLE.

Because testing everything is not feasible.

A 'Test ANALYSIS' and 'Design' INCLUDES evaluation of the TESTABILITY of the requirements and SYSTEM.

A 'Test Analysis' and 'Design' includes evaluation of the testability of the requirements and system.

There are currently SEVEN different agile methodologies that I am AWARE of:

1. Extreme Programming (XP)
2. Scrum
3. Lean SOFTWARE Development
4. Feature-Driven Development
5. Agile Unified Process
6. Crystal
7. Dynamic SYSTEMS Development Model (DSDM)

There are currently seven different agile methodologies that I am aware of:

The BULK of the TEST DESIGN work BEGUN after the SOFTWARE or system has been produced.

The bulk of the test design work begun after the software or system has been produced.

INDEPENDENT TESTERS are UNBIASED and IDENTIFY different defects at the same time.

Independent testers are unbiased and identify different defects at the same time.

Testing the END to end FUNCTIONALITY of the system as a whole is defined as a FUNCTIONAL system testing.

Testing the end to end functionality of the system as a whole is defined as a functional system testing.

Component testing, ALSO KNOWN as unit, module and program testing, searches for defects in, and verifies the functioning of software (e.g. modules, programs, objects, classes, etc.) that are SEPARATELY testable. Component testing may be done in isolation from the rest of the system depending on the context of the development life cycle and the system. Most often stubs and DRIVERS are used to replace the missing software and simulate the interface between the software components in a simple manner. A stub is called from the software component to be tested; a DRIVER calls a component to be tested.

Component testing, also known as unit, module and program testing, searches for defects in, and verifies the functioning of software (e.g. modules, programs, objects, classes, etc.) that are separately testable. Component testing may be done in isolation from the rest of the system depending on the context of the development life cycle and the system. Most often stubs and drivers are used to replace the missing software and simulate the interface between the software components in a simple manner. A stub is called from the software component to be tested; a driver calls a component to be tested.

REGRESSION TESTING

Regression Testing

USER ACCEPTANCE TEST CASES.

User Acceptance Test Cases.

Testing TECHNIQUE: Is a process for ensuring that some aspects of the application system or unit functions PROPERLY there may be few TECHNIQUES but MANY tools.

Testing Tools: Is a vehicle for performing a test process. The tool is a resource to the tester, but itself is insufficient to conduct testing.

Testing technique: Is a process for ensuring that some aspects of the application system or unit functions properly there may be few techniques but many tools.

Testing Tools: Is a vehicle for performing a test process. The tool is a resource to the tester, but itself is insufficient to conduct testing.

Rapid Application Development (RAD) is formally a parallel development of FUNCTIONS and subsequent INTEGRATION. Components/functions are developed in parallel as if they were mini projects, the developments are time-boxed, delivered, and then assembled into a working prototype. This can very quickly give the customer SOMETHING to see and use and to provide FEEDBACK regarding the delivery and their requirements.

Rapid change and development of the product is possible using this methodology. HOWEVER the product specification will need to be developed for the product at some point, and the project will need to be placed under more formal controls prior to going into production.

Rapid Application Development (RAD) is formally a parallel development of functions and subsequent integration. Components/functions are developed in parallel as if they were mini projects, the developments are time-boxed, delivered, and then assembled into a working prototype. This can very quickly give the customer something to see and use and to provide feedback regarding the delivery and their requirements.

Rapid change and development of the product is possible using this methodology. However the product specification will need to be developed for the product at some point, and the project will need to be placed under more formal controls prior to going into production.

NONE, EXISTING TEST CASES can be USED.

None, existing test cases can be used.

4

4

The EXIT CRITERIA is DETERMINED on the BASES of 'Test PLANNING'.

The exit criteria is determined on the bases of 'Test Planning'.

It avoids AUTHOR BIAS in DEFINING effective tests.

It avoids author bias in defining effective tests.

Test case specification DEFINES the EXPECTED RESULTS of a test.

Test case specification defines the expected results of a test.

To IDENTIFY DEFECTS in any SOFTWARE WORK PRODUCT.

To identify defects in any software work product.

The LIKELIHOOD of an adverse event and the IMPACT of the event determine the LEVEL of risk.

The likelihood of an adverse event and the impact of the event determine the level of risk.

4, 5, 99

4, 5, 99

It HELPS PREVENT DEFECTS from being INTRODUCED into the CODE.

It helps prevent defects from being introduced into the code.