Latest Quality Analysis Interview Preparation Guide

Download PDF

★ Alpha testing is performed by the In-House developers. After alpha testing the software is handed over to software quality assurance team, for additional testing in an environment that is similar to the client environment.

★ Beta testing 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 quality assurance team perform alpha testing. The public, a few select prospective customers or the general public performs beta testing.

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 previous build then this is called as Bug Leakage.

Bug release:
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.

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.
Example: "9.4.123.2" (Release Number.Version Number.Build Number.Patch Number)

Priority:
Concern with application from the business point of view.
Like: How quickly we need to fix the bug?
How soon the bug should get fixed?
Severity:
Concerns with functionality of application. It deals with the impact of the bug on the application.

Software development life cycle includes the following different stages:
★ Requirement phase
★ Design phase
★ Coding (programming)
★ Testing
★ Release (Production)
★ Maintenance (Support)

The systems (or software) development life cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.

Use case includes cover page, revision history, table of contents, floe of events (normal flow and alternative flow), exceptions, special requirements, pre-conditions and post-conditions.

A use case is a document that describes the user action and system response for a particular functionality.

A test case includes test case ID, steps description, expected output, actual output, pass/fail, remarks.

A Test Case is a document that describes step by step process how to test the application.

A Test Plan includes Heading, Revision History, Table of Contents, Introduction, Scope, Approach, Overview, different types of testing that will be carried out, what software and hardware will be required, issues, risks, assumptions and sign off section.

A Test Plan is a document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks and who will do each task (roles and responsibilities) and any risks and its solutions.

Beta testing 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 quality assurance 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 quality assurance team, for additional testing in an environment that is similar to the client environment.

Example: 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.

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.

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.

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 previous build then this is called as Bug Leakage.

The choice of SDLC depends on the various factors, how stable are the requirements:
When the requirements are very clearly know, documented and not subject to change then we can follow the waterfall model.
Most of the companies follow the V mode for the development because this model includes both verification and validation activities and testing is involved in earlier phase.

Iterative model can be used to build application where requirement changes after a period of times or application features or added on with smaller release. When the client is ready for the delivery of the product in parts or phases.

The reasons for choosing automation testing over manual testing are following:
★ Frequency of use of test case
★ Time Comparison (automated script run much faster than manual execution.)
★ Re-usability of Automation Script
★ Adaptability of test case for automation
★ Exploitation of automation tool

Following are some challenges of software testing
★ Application should be stable enough to be tested
★ Testing always under time constraint
★ Understanding requirements, Domain knowledge and business user perspective understanding
★ Which tests to execute first?
★ Testing the Complete Application
★ Regression testing
★ Lack of skilled testers
★ Changing requirements
★ Lack of resources, tools and training

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 that 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.

Quality assurance team assures the quality by monitor the whole development process. Quality assurance tracks the outcomes and adjusting process to meet the expectation.

The role of quality assurance is discussed below:
★ Quality assurance team is responsible for monitoring the process to be carried out for development.
★ Responsibilities of quality assurance team are planning testing execution process.
★ Quality assurance Lead creates the time tables and agrees on a Quality Assurance plan for the product.
★ Quality assurance team communicated quality assurance process to the team members.
★ Quality assurance team ensures trace ability of test cases to requirements.