Explore topic-wise InterviewSolutions in .

Beta testing: It is performed by end user. So that they can MAKE sure that the product is bug free or working as per the requirement. IN-house developers and software QA team PERFORM alpha testing. The public, a few SELECT prospective customers or the general public PERFORMS beta testing.

Beta testing: It is performed by end user. So that they can make sure that the product is bug free or working as per the requirement. IN-house developers and software QA team perform alpha testing. The public, a few select prospective customers or the general public performs beta testing.

ALPHA TESTING: is performed by the IN-House developers. After alpha testing the software is handed over to software QA team, for additional testing in an ENVIRONMENT that is SIMILAR to the client environment.

Alpha testing: is performed by the IN-House developers. After alpha testing the software is handed over to software QA team, for additional testing in an environment that is similar to the client environment.

Regression Testing: When changes in the code of the software are made to fix the previous BUG. Then testing needs to be perform to ensure that it will not generate a new bug in the application and it works as specified and that it has not negatively impacted any FUNCTIONALITY that it offered previously. Regression Testing is important because of following reason:

• That the application works even after the ALTERATION in the code were made.
• The original functionality continues to work as specified even after doing changes in the software application.
• The alteration to the software application has not INTRODUCED any new bugs.

Regression Testing: When changes in the code of the software are made to fix the previous bug. Then testing needs to be perform to ensure that it will not generate a new bug in the application and it works as specified and that it has not negatively impacted any functionality that it offered previously. Regression Testing is important because of following reason:

Data DRIVEN is an automation testing part in which test input or output VALUES, these values are read from data files. It is performed when the values are changing by the time. The different data files may include data pools, csv files, EXCEL files. The data is then loaded into variables in recorded or manually coded SCRIPTS. For data driven testing we use Parameterzing and Regular expression Technique.

Ex: To evaluate login functionality, we use different user name and PASSWORD combinations, variables are used to access different username and password. The list of username and password are stored in a data table or excel sheet.

Data Driven is an automation testing part in which test input or output values, these values are read from data files. It is performed when the values are changing by the time. The different data files may include data pools, csv files, Excel files. The data is then loaded into variables in recorded or manually coded scripts. For data driven testing we use Parameterzing and Regular expression Technique.

Ex: To evaluate login functionality, we use different user name and password combinations, variables are used to access different username and password. The list of username and password are stored in a data table or excel sheet.

Bug release: is when a build is handed to testing team with KNOWING that defect is present in the release. The priority and severity of bug is low. It is done when customer want the APPLICATION on the TIME. Customer can tolerate the bug in the released then the delay in getting the application and the cost involved in REMOVING that bug. These bugs are mentioned in the Release Notes handed to client for the future improvement chances. 

Bug release: is when a build is handed to testing team with knowing that defect is present in the release. The priority and severity of bug is low. It is done when customer want the application on the time. Customer can tolerate the bug in the released then the delay in getting the application and the cost involved in removing that bug. These bugs are mentioned in the Release Notes handed to client for the future improvement chances. 

Bug Leakage: When customer or END USER DISCOVERED a bug which can be DETECTED by the TESTING team. Or when a bug is detected which can be detected in pervious build then this is called as Bug Leakage.

Bug Leakage: When customer or end user discovered a bug which can be detected by the testing team. Or when a bug is detected which can be detected in pervious build then this is called as Bug Leakage.

RELEASE: is a number given to installable software that is handed over to customer by the developer or tester.

The information of BUILD, release and version are displayed in software HELP page. Using this build and release customer can let the customer team KNOW which release version build thet are using.

RELEASE: is a number given to installable software that is handed over to customer by the developer or tester.

The information of build, release and version are displayed in software help page. Using this build and release customer can let the customer team know which release version build thet are using.

BUILD: is a NUMBER GIVEN to installable SOFTWARE that is given to testing team for testing by the development team. Build number assigned are incremental and sequential.

BUILD: is a number given to installable software that is given to testing team for testing by the development team. Build number assigned are incremental and sequential.

BUILD: is a NUMBER given to installable software that is given to testing team for testing by the development team. Build number assigned are incremental and sequential.

RELEASE: is a number given to installable software that is handed over to customer by the developer or TESTER.

The information of build, release and VERSION are displayed in software help page. Using this build and release customer can let the customer team know which release version build thet are using.

eg "9.4.123.2" (Release Number.Version Number.Build Number.Patch Number)

BUILD: is a number given to installable software that is given to testing team for testing by the development team. Build number assigned are incremental and sequential.

RELEASE: is a number given to installable software that is handed over to customer by the developer or tester.

The information of build, release and version are displayed in software help page. Using this build and release customer can let the customer team know which release version build thet are using.

eg "9.4.123.2" (Release Number.Version Number.Build Number.Patch Number)

SOFTWARE problem are listed below:

1. PURCHASING the license of TOOL (QTP, selenium, QC, LR)
2. Lack of skilled Tester to RUN the tool
3. Expectation that automated tests will find a LOT of new defects
4. Maintenance of automated tests
5. Technical problems of tools

Software problem are listed below:

• High Priority and Low Severity: Company logo is not properly displayed on their website.
• High Priority and High Severity: Suppose you are doing online shopping and FILLED payment INFORMATION, but after SUBMITTING the FORM, you get a message like "Order has been CANCELLED."
• Low Priority and High Severity: If we have a typical scenario in which the application get crashed, but that scenario exists rarely.
• Low Priority and Low Severity: There is a mistake like "You have registered success" instead of successfully, success is written.

Bug Life Cycle:

When a tester finds a bug .The bug is assigned with NEW or OPEN status.

The bug is assigned to development project manager who will analyze the bug .He will check whether it is a valid defect. If it is not valid bug is rejected, now status is REJECTED.

If not, NEXT the defect is checked whether it is in scope. When bug is not part of the CURRENT release .Such defects are POSTPONED

Now, Tester checks whether similar defect was raised EARLIER. If yes defect is assigned a status DUPLICATE

When bug is assigned to developer. During this stage bug is assigned a status IN-PROGRESS

Once code is fixed. Defect is assigned with FIXED status.

Next the tester will re-test the code. In CASE the test case passes the defect is CLOSED

If the test case FAILS again the bug is RE-OPENED and assigned to the developer. That's all to Bug Life Cycle.

Bug Life Cycle:

When a tester finds a bug .The bug is assigned with NEW or OPEN status.

The bug is assigned to development project manager who will analyze the bug .He will check whether it is a valid defect. If it is not valid bug is rejected, now status is REJECTED.

If not, next the defect is checked whether it is in scope. When bug is not part of the current release .Such defects are POSTPONED

Now, Tester checks whether similar defect was raised earlier. If yes defect is assigned a status DUPLICATE

When bug is assigned to developer. During this stage bug is assigned a status IN-PROGRESS

Once code is fixed. Defect is assigned with FIXED status.

Next the tester will re-test the code. In case the test case passes the defect is CLOSED

If the test case fails again the bug is RE-OPENED and assigned to the developer. That's all to Bug Life Cycle.

Priority: concern with application from the BUSINESS POINT of view.

It answers: How quickly we need to fix the bug? Or How soon the bug should GET FIXED?

Severity: concern with functionality of application. It deals with the IMPACT of the bug on the application.

Priority: concern with application from the business point of view.

It answers: How quickly we need to fix the bug? Or How soon the bug should get fixed?

Severity: concern with functionality of application. It deals with the impact of the bug on the application.

The difference between smoke and sanity testing is described below:

• Sanity testing is performed when new BUILD is released after fixing bugs where as smoke testing is performed to check the major functionalities of the APPLICATION.
• Sanity is performed by the TESTER or the developer but smoke testing can be performed by the tester or developer.
• Smoke testing is performed EARLIER where as sanity is performed after the smoke testing.
• Sanity testing is narrow and deep approach of testing and smoke testing is FOCUSED testing based on major functionalities.

The difference between smoke and sanity testing is described below:

• VERIFICATION is Static Testing where as Validations is Dynamic Testing.
• Verification TAKES place before validation.
• Verification evaluates plans, DOCUMENTS, requirements and specifications, where as Validation evaluates product.
• Verification inputs are checklist, ISSUES list, walkthroughs and inspection, where as in Validation testing of actual product.
• Verification OUTPUT is set of documents, plans, specifications and requirement documents where as in Validation actual product is output.

A GOOD time to start the QA is from the BEGINNING of the PROJECT startup. This will lead to plan the process which will make sure that product coming out meets the customer quality expectation. QA also plays a MAJOR role in the communication between teams. It gives time to step up the testing environment. The testing phase starts after the test plans are written, reviewed and approved.

A good time to start the QA is from the beginning of the project startup. This will lead to plan the process which will make sure that product coming out meets the customer quality expectation. QA also plays a major role in the communication between teams. It gives time to step up the testing environment. The testing phase starts after the test plans are written, reviewed and approved.

SOFTWARE Testing: is the process of ENSURING that PRODUCT which is developed by the developer meets the user requirement. The MOTIVE to perform testing is to find the bugs and make SURE that they get fixed.

Software Testing: is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.

Quality Control (QC): Concern with the quality of the product. QC FINDS the defects and suggests IMPROVEMENTS. The PROCESS set by QA is implemented by QC. The QC is the RESPONSIBILITY of the tester.

Quality Control (QC): Concern with the quality of the product. QC finds the defects and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.

QUALITY Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is FOLLOWED to produce a quality PRODUCT. QA tracks the outcomes and ADJUSTS the process to MEET the expectation.

Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.

Quality Assurance (QA): QA refers to the planned and systematic WAY of monitoring the quality of process which is followed to produce a quality product. QA tracks the OUTCOMES and adjusts the process to meet the expectation.

Quality Control (QC): Concern with the quality of the product. QC finds the DEFECTS and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.

Software Testing: is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.

Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.

Quality Control (QC): Concern with the quality of the product. QC finds the defects and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.

Software Testing: is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.

WinRunner has two types of recording modes:

1. Context Sensitive recording – records the operations that are preformed in an application by identifying the GUI objects.
2. ANALOG recording – records the inputs from keyboard, MOUSE CLICKS, the X and y coordinates that are TRAVELLED by the mouse pointer across the screen.

WinRunner has two types of recording modes:

Once the test is executed, a REPORT of the results is displayed by WinRunner. The report shows all checkpoints, error and SYSTEM messages that were ENCOUNTERED during EXECUTION. The test results window is USED to account for any mismatches detected at checkpoints.

Once the test is executed, a report of the results is displayed by WinRunner. The report shows all checkpoints, error and system messages that were encountered during execution. The test results window is used to account for any mismatches detected at checkpoints.

A software process or software development process is a method or structure EXPECTED to be FOLLOWED for the development of software. There are several tasks and ACTIVITIES that TAKE place in this process. DIFFERENT processes like waterfall and iterative exists. In these processes; tasks like analysis, coding, testing and maintenance play an important role.

A software process or software development process is a method or structure expected to be followed for the development of software. There are several tasks and activities that take place in this process. Different processes like waterfall and iterative exists. In these processes; tasks like analysis, coding, testing and maintenance play an important role.

Process areas in Capabilty MATURITY model describe the features of a products development. These process areas help to identify the LEVEL of maturity an ORGANIZATION has attained. These mainly include:

• Project planning and monitoring
• Risk Management
• REQUIREMENTS development
• Process and Product quality assurance
• Product integration
• Requirement management
• Product integration
• Configuration management

Process areas in Capabilty Maturity model describe the features of a products development. These process areas help to identify the level of maturity an organization has attained. These mainly include:

The key practices of software-producing and acquiring organizations needs significant interpretation or tailoring prior to application. The tailoring involves the identification of process artifacts, process tailoring, and their relationships to project artifacts. Subsequent to this process, the nature of various KINDS of tailoring used is explored in the definition and development of software process DESCRIPTIONS. Various techniques that are appropriate to each TYPE of tailoring are then discussed. The approach is built on Software Process Framework, which serves for providing guidance for designing, ANALYZING, and reviewing the process of software for consistency with the Software Capability Maturity Model.

Various tailoring plans are implemented by including mandatory processes, process waivers, tailored processes / procedures, LIFECYCLE models. The tailoring plans are reviewed at enterprise level but owned and updated only at the project level.

The key practices of software-producing and acquiring organizations needs significant interpretation or tailoring prior to application. The tailoring involves the identification of process artifacts, process tailoring, and their relationships to project artifacts. Subsequent to this process, the nature of various kinds of tailoring used is explored in the definition and development of software process descriptions. Various techniques that are appropriate to each type of tailoring are then discussed. The approach is built on Software Process Framework, which serves for providing guidance for designing, analyzing, and reviewing the process of software for consistency with the Software Capability Maturity Model.

Various tailoring plans are implemented by including mandatory processes, process waivers, tailored processes / procedures, Lifecycle models. The tailoring plans are reviewed at enterprise level but owned and updated only at the project level.