Explore topic-wise InterviewSolutions in .

If software misses some feature or FUNCTION from what is there in requirement it is CALLED as DEFECT.

If software misses some feature or function from what is there in requirement it is called as defect.

TEST which focus on the boundary or limit CONDITIONS of the SOFTWARE being tested. (Some of these TESTS are stress tests).

Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

An approach to integration testing where the lowest level components are TESTED first, then used to facilitate the testing of HIGHER level components. The process is repeated until the component at the top of the HIERARCHY is tested.

An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

Testing an EXECUTABLE APPLICATION for PORTABILITY across system platforms and environments, usually for conformation to an ABI SPECIFICATION.

Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

The set of tests DERIVED USING basis path TESTING.

The set of tests derived using basis path testing.

A WHITE box TEST case DESIGN technique that uses the algorithmic flow of the PROGRAM to design TESTS.

A white box test case design technique that uses the algorithmic flow of the program to design tests.

A METALANGUAGE used to FORMALLY DESCRIBE the syntax of a LANGUAGE.

A metalanguage used to formally describe the syntax of a language.

The use of software tools, such as AUTOMATED TESTING tools, to IMPROVE software QUALITY.

The use of software tools, such as automated testing tools, to improve software quality.

A formalized set of software CALLS and ROUTINES that can be referenced by an application program in ORDER to access supporting system or NETWORK services.

A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.

VERIFYING a PRODUCT is accessible to the people having disabilities (deaf, blind, mentally disabled ETC.).

Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

Implement QA processes slowly over time. Use consensus to reach agreement on processes and adjust and experiment as an organization grows and MATURES. Productivity will be improved instead of stifled. Problem prevention will lessen the need for problem detection. Panics and burnout will decrease and there will be improved focus and less wasted EFFORT.

At the same time, attempts should be made to keep processes simple and efficient, minimize paperwork, promote computer-based processes and automated tracking and REPORTING, minimize time REQUIRED in meetings and promote training as part of the QA process.

However, no one, especially talented technical TYPES, like bureaucracy and in the short run things may slow down a bit. A typical scenario would be that more days of planning and development will be needed, but less time will be required for late-night bug fixing and calming of irate customers.

Implement QA processes slowly over time. Use consensus to reach agreement on processes and adjust and experiment as an organization grows and matures. Productivity will be improved instead of stifled. Problem prevention will lessen the need for problem detection. Panics and burnout will decrease and there will be improved focus and less wasted effort.

At the same time, attempts should be made to keep processes simple and efficient, minimize paperwork, promote computer-based processes and automated tracking and reporting, minimize time required in meetings and promote training as part of the QA process.

However, no one, especially talented technical types, like bureaucracy and in the short run things may slow down a bit. A typical scenario would be that more days of planning and development will be needed, but less time will be required for late-night bug fixing and calming of irate customers.

This is a common problem in the SOFTWARE industry, especially in new technology areas. There is no EASY solution in this situation, other than:

1. Hire good people.
2. Ruthlessly prioritize QUALITY issues and maintain focus on the customer.
3. EVERYONE in the organization should be clear on what quality MEANS to the customer.

This is a common problem in the software industry, especially in new technology areas. There is no easy solution in this situation, other than:

Because testing during the DESIGN phase can prevent defects later on. We RECOMMEND verifying three things:

1. Verify the design is good, efficient, compact, testable and maintainable.
2. Verify the design meets the requirements and is complete (specifies all relationships between modules, how to pass DATA, what happens in exceptional circumstances, starting state of each module and how to guarantee the state of each module).
3. Verify the design incorporates ENOUGH memory, I/O devices and quick enough runtime for the final PRODUCT.

Because testing during the design phase can prevent defects later on. We recommend verifying three things:

A 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 well designed this can simplify test design.

A 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 well designed this can simplify test design.

Quality Assurance ensures all PARTIES concerned with the project ADHERE to the process and procedures, standards and TEMPLATES and TEST READINESS reviews.

Quality Assurance ensures all parties concerned with the project adhere to the process and procedures, standards and templates and test readiness reviews.

Black BOX testing is FUNCTIONAL testing, not based on any knowledge of internal software DESIGN or code. Black box testing are based on requirements and functionality.

Black box testing is functional testing, not based on any knowledge of internal software design or code. Black box testing are based on requirements and functionality.

White box testing is BASED on KNOWLEDGE of the internal logic of an APPLICATION's code. TESTS are based on coverage of code STATEMENTS, branches, paths and conditions.

White box testing is based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths and conditions.

Functional TESTING is black-box type of testing GEARED to functional requirements of an APPLICATION. Test engineers should PERFORM functional testing.

Functional testing is black-box type of testing geared to functional requirements of an application. Test engineers should perform functional testing.

Usability testing is testing for 'user-friendliness'. Clearly this is subjective and DEPENDS on the targeted end-user or customer. User interviews, surveys, VIDEO recording of user sessions and other techniques can be used. Programmers and DEVELOPERS are USUALLY not appropriate as usability testers.

Usability testing is testing for 'user-friendliness'. Clearly this is subjective and depends on the targeted end-user or customer. User interviews, surveys, video recording of user sessions and other techniques can be used. Programmers and developers are usually not appropriate as usability testers.

Incremental integration TESTING is CONTINUOUS testing of an application as new functionality is recommended. This may REQUIRE that various aspects of an application's functionality are independent enough to work separately, before all parts of the program are COMPLETED, or that TEST drivers are developed as needed.Incremental testing may be performed by programmers, software engineers, or test engineers.

Incremental integration testing is continuous testing of an application as new functionality is recommended. This may require that various aspects of an application's functionality are independent enough to work separately, before all parts of the program are completed, or that test drivers are developed as needed.Incremental testing may be performed by programmers, software engineers, or test engineers.

Parallel/audit testing is testing where the user reconciles the output of the NEW SYSTEM to the output of the current system to VERIFY the new system PERFORMS the OPERATIONS correctly.

Parallel/audit testing is testing where the user reconciles the output of the new system to the output of the current system to verify the new system performs the operations correctly.

Upon completion of unit testing, integration testing begins. Integration testing is black box testing. The purpose of integration testing is to ensure distinct components of the APPLICATION still work in accordance to CUSTOMER requirements.TEST CASES are developed with the express purpose of exercising the interfaces between the components. This activity is carried out by the test team.Integration testing is considered complete, when actual results and expected results are either in line or DIFFERENCES are explainable/acceptable based on client input.

Upon completion of unit testing, integration testing begins. Integration testing is black box testing. The purpose of integration testing is to ensure distinct components of the application still work in accordance to customer requirements.Test cases are developed with the express purpose of exercising the interfaces between the components. This activity is carried out by the test team.Integration testing is considered complete, when actual results and expected results are either in line or differences are explainable/acceptable based on client input.

System testing is black box testing, performed by the Test Team, and at the START of the system testing the complete system is configured in a CONTROLLED ENVIRONMENT.The purpose of system testing is to validate an application's ACCURACY and completeness in performing the functions as designed.System testing simulates real life scenarios that occur in a "simulated real life" test environment and test all functions of the system that are required in real life.System testing is deemed complete when actual results and expected results are either in line or DIFFERENCES are explainable or acceptable, based on client input.

System testing is black box testing, performed by the Test Team, and at the start of the system testing the complete system is configured in a controlled environment.The purpose of system testing is to validate an application's accuracy and completeness in performing the functions as designed.System testing simulates real life scenarios that occur in a "simulated real life" test environment and test all functions of the system that are required in real life.System testing is deemed complete when actual results and expected results are either in line or differences are explainable or acceptable, based on client input.

Similar to system testing, the macro end of the test scale is testing a complete application in a SITUATION that mimics real world use, such as interacting with a database, using NETWORK COMMUNICATION, or interacting with other hardware, application, or system.

Similar to system testing, the macro end of the test scale is testing a complete application in a situation that mimics real world use, such as interacting with a database, using network communication, or interacting with other hardware, application, or system.

The objective of regression testing is to ensure the software REMAINS intact. A baseline SET of data and scripts is maintained and executed to verify changes introduced during the release have not "undone" any previous code. Expected RESULTS from the baseline are compared to results of the software under test. All discrepancies are highlighted and accounted for, before testing proceeds to the next level.

The objective of regression testing is to ensure the software remains intact. A baseline set of data and scripts is maintained and executed to verify changes introduced during the release have not "undone" any previous code. Expected results from the baseline are compared to results of the software under test. All discrepancies are highlighted and accounted for, before testing proceeds to the next level.

Sanity testing is performed whenever cursory testing is sufficient to prove the application is FUNCTIONING according to specifications. This level of testing is a subset of regression testing.It NORMALLY includes a SET of core tests of basic GUI functionality to demonstrate connectivity to the database, application SERVERS, printers, etc.

Sanity testing is performed whenever cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.It normally includes a set of core tests of basic GUI functionality to demonstrate connectivity to the database, application servers, printers, etc.

Load TESTING is testing an APPLICATION under heavy loads, such as the testing of a WEB site under a range of loads to DETERMINE at what point the system response time will degrade or fail.

Load testing is testing an application under heavy loads, such as the testing of a web site under a range of loads to determine at what point the system response time will degrade or fail.

Installation testing is testing FULL, partial, upgrade, or install/uninstall PROCESSES. The installation test for a release is conducted with the objective of demonstrating production readiness.
This test includes the INVENTORY of configuration items, performed by the application's System Administration, the EVALUATION of data readiness, and dynamic tests focused on basic system functionality. When necessary, a sanity test is performed, following installation testing.

Installation testing is testing full, partial, upgrade, or install/uninstall processes. The installation test for a release is conducted with the objective of demonstrating production readiness.
This test includes the inventory of configuration items, performed by the application's System Administration, the evaluation of data readiness, and dynamic tests focused on basic system functionality. When necessary, a sanity test is performed, following installation testing.

Security/penetration testing is testing how WELL the system is PROTECTED against UNAUTHORIZED internal or external access, or WILLFUL damage.This type of testing usually requires sophisticated testing techniques.

Security/penetration testing is testing how well the system is protected against unauthorized internal or external access, or willful damage.This type of testing usually requires sophisticated testing techniques.

Recovery/error TESTING is testing how WELL a system RECOVERS from crashes, hardware failures, or other CATASTROPHIC problems.

Recovery/error testing is testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

Compatibility TESTING is testing how well software PERFORMS in a particular hardware, software, operating SYSTEM, or NETWORK

Compatibility testing is testing how well software performs in a particular hardware, software, operating system, or network

Comparison TESTING is testing that compares SOFTWARE WEAKNESSES and STRENGTHS to those of competitors products.

Comparison testing is testing that compares software weaknesses and strengths to those of competitors products.

Acceptance testing is black BOX testing that gives the client/customer/project manager the opportunity to verify the system functionality and USABILITY PRIOR to the system being RELEASED to production.

The acceptance test is the responsibility of the client/customer or project manager, however, it is conducted with the full support of the project TEAM. The test team also works with the client/customer/project manager to develop the acceptance criteria.

Acceptance testing is black box testing that gives the client/customer/project manager the opportunity to verify the system functionality and usability prior to the system being released to production.

The acceptance test is the responsibility of the client/customer or project manager, however, it is conducted with the full support of the project team. The test team also works with the client/customer/project manager to develop the acceptance criteria.

Alpha TESTING is testing of an application when development is NEARING COMPLETION. MINOR design changes can still be made as a RESULT of alpha testing. Alpha testing is typically performed by a group that is independent of the design team, but still within the company, e.g. in-house software test engineers, or software QA engineers.

Alpha testing is testing of an application when development is nearing completion. Minor design changes can still be made as a result of alpha testing. Alpha testing is typically performed by a group that is independent of the design team, but still within the company, e.g. in-house software test engineers, or software QA engineers.

BETA testing is testing an application when development and testing are ESSENTIALLY completed and final bugs and problems NEED to be found before the final release. Beta testing is typically PERFORMED by end-users or others, not PROGRAMMERS, software engineers, or test engineers.

Beta testing is testing an application when development and testing are essentially completed and final bugs and problems need to be found before the final release. Beta testing is typically performed by end-users or others, not programmers, software engineers, or test engineers.

The TEST/QA TEAM Lead coordinates the testing ACTIVITY, communicates testing status to management and MANAGES the test team.

The Test/QA Team Lead coordinates the testing activity, communicates testing status to management and manages the test team.

Depending on the organization, the following ROLES are more or less standard on most testing projects: Testers, Test Engineers, Test/QA Team Lead, Test/QA Manager, System ADMINISTRATOR, DATABASE Administrator, Technical Analyst, Test Build Manager and Test Configuration Manager.

Depending on the organization, the following roles are more or less standard on most testing projects: Testers, Test Engineers, Test/QA Team Lead, Test/QA Manager, System Administrator, Database Administrator, Technical Analyst, Test Build Manager and Test Configuration Manager.

We, test engineers, are engineers who specialize in testing. We, test engineers, create test cases, procedures, scripts and generate data. We execute test procedures and scripts, analyze standards of measurements, evaluate results of system/integration/regression testing. We also:

• Speed up the work of the development staff.
• Reduce your organization's risk of legal LIABILITY.
• Give you the evidence that your software is correct and operates properly.
• Improve problem tracking and reporting.
• Maximize the value of your software.
• Maximize the value of the devices that USE it;
• Assure the successful launch of your product by discovering bugs and design flaws, before users get discouraged, before shareholders LOOSE their cool and before employees get bogged down.
• Help the work of your development staff, so the development team can devote its time to build up your product.
• Promote continual improvement.
• Provide documentation required by FDA, FAA, other regulatory agencies and your customers.
• Save money by discovering defects 'early' in the design process, before failures OCCUR in production, or in the field.
• Save the reputation of your COMPANY by discovering bugs and design flaws before bugs and design flaws damage the reputation of your company.

We, test engineers, are engineers who specialize in testing. We, test engineers, create test cases, procedures, scripts and generate data. We execute test procedures and scripts, analyze standards of measurements, evaluate results of system/integration/regression testing. We also:

Test Build Managers deliver current software versions to the test ENVIRONMENT, install the application's software and apply software patches, to both the application and the operating SYSTEM, set-up, maintain and BACK up test environment hardware.Depending on the project, ONE PERSON may wear more than one hat. For instance, a Test Engineer may also wear the hat of a Test Build Manager.

Test Build Managers deliver current software versions to the test environment, install the application's software and apply software patches, to both the application and the operating system, set-up, maintain and back up test environment hardware.Depending on the project, one person may wear more than one hat. For instance, a Test Engineer may also wear the hat of a Test Build Manager.

Test Build Managers, System Administrators, Database Administrators DELIVER CURRENT software versions to the test environment, install the application's software and APPLY software patches, to both the application and the operating system, set-up, MAINTAIN and back up test environment hardware.Depending on the project, one person may wear more than one hat. For instance, a Test Engineer may also wear the hat of a System Administrator.

Test Build Managers, System Administrators, Database Administrators deliver current software versions to the test environment, install the application's software and apply software patches, to both the application and the operating system, set-up, maintain and back up test environment hardware.Depending on the project, one person may wear more than one hat. For instance, a Test Engineer may also wear the hat of a System Administrator.

Test Build Managers, System Administrators and Database Administrators DELIVER current software VERSIONS to the test environment, install the application's software and apply software patches, to both the application and the operating system, set-up, maintain and BACK up test environment hardware. Depending on the project, one person may WEAR more than one hat. For instance, a Test Engineer may also wear the hat of a Database Administrator.

Test Build Managers, System Administrators and Database Administrators deliver current software versions to the test environment, install the application's software and apply software patches, to both the application and the operating system, set-up, maintain and back up test environment hardware. Depending on the project, one person may wear more than one hat. For instance, a Test Engineer may also wear the hat of a Database Administrator.

TECHNICAL Analysts perform TEST ASSESSMENTS and validate system/functional test REQUIREMENTS. Depending on the project, one person MAY wear more than one hat. For instance, Test Engineers may also wear the hat of a Technical Analyst.

Technical Analysts perform test assessments and validate system/functional test requirements. Depending on the project, one person may wear more than one hat. For instance, Test Engineers may also wear the hat of a Technical Analyst.

Test CONFIGURATION MANAGERS maintain test environments, scripts, software and test data. Depending on the project, one PERSON may wear more than one HAT. For INSTANCE, Test Engineers may also wear the hat of a Test Configuration Manager.

Test Configuration Managers maintain test environments, scripts, software and test data. Depending on the project, one person may wear more than one hat. For instance, Test Engineers may also wear the hat of a Test Configuration Manager.

The test schedule is a schedule that identifies all TASKS required for a SUCCESSFUL testing effort, a schedule of all test activities and resource requirements.

The test schedule is a schedule that identifies all tasks required for a successful testing effort, a schedule of all test activities and resource requirements.

One software testing methodology is the use a THREE STEP process of:

1. Creating a test strategy.
2. Creating a test plan/design and.
3. Executing TESTS.

This methodology can be used and molded to your organization's needs. ROB Davis believes that using this methodology is important in the development and ongoing maintenance of his clients' applications.

One software testing methodology is the use a three step process of:

This methodology can be used and molded to your organization's needs. Rob Davis believes that using this methodology is important in the development and ongoing maintenance of his clients' applications.

The general TESTING process is the creation of a test strategy (which sometimes includes the creation of test CASES), creation of a test plan/design (which usually includes test cases and test PROCEDURES) and the execution of TESTS.

The general testing process is the creation of a test strategy (which sometimes includes the creation of test cases), creation of a test plan/design (which usually includes test cases and test procedures) and the execution of tests.

The test strategy is a formal description of how a software PRODUCT will be tested. A test strategy is developed for all levels of TESTING, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test CASES, conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment.
Inputs for this process:

• A description of the required hardware and software components, including test tools. This information comes from the test environment, including test tool data.
• A description of ROLES and responsibilities of the resources required for the test and schedule constraints. This information comes from man-hours and schedules.
• Testing methodology. This is based on known standards.
• Functional and technical requirements of the application. This information comes from requirements, change request, technical and functional design documents.
• Requirements that the system can not provide, e.g. system limitations.

Outputs for this process:

• An approved and signed off test strategy document, test plan, including test cases.
• Testing ISSUES requiring resolution. Usually this requires additional negotiation at the project management level.

The test strategy is a formal description of how a software product will be tested. A test strategy is developed for all levels of testing, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test cases, conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment.
Inputs for this process:

Outputs for this process:

Security CLEARANCE is a process of DETERMINING your trustworthiness and reliability before granting you access to NATIONAL security information.

Security clearance is a process of determining your trustworthiness and reliability before granting you access to national security information.

The levels of classified access are CONFIDENTIAL, SECRET, TOP secret, and SENSITIVE compartmented INFORMATION, of which top secret is the highest.

The levels of classified access are confidential, secret, top secret, and sensitive compartmented information, of which top secret is the highest.

The best bet in this situation is for the testers to go through the process of REPORTING whatever bugs or blocking-TYPE problems INITIALLY SHOW up, with the focus being on critical bugs. Since this type of problem can severely affect schedules, and indicates deeper problems in the software development process (such as insufficient unit testing or insufficient integration testing, poor design, improper build or release procedures, etc.) managers should be notified, and provided with some DOCUMENTATION as evidence of the problem.

The best bet in this situation is for the testers to go through the process of reporting whatever bugs or blocking-type problems initially show up, with the focus being on critical bugs. Since this type of problem can severely affect schedules, and indicates deeper problems in the software development process (such as insufficient unit testing or insufficient integration testing, poor design, improper build or release procedures, etc.) managers should be notified, and provided with some documentation as evidence of the problem.