Quality Analyst

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.

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.

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 Case is a document that describes step by step process how to test the application.

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

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

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.

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.

Software development life cycle includes the following different stages:

★ Requirement phase

★ Design phase

★ Coding (programming)

★ Testing

★ Release (Production)

★ Maintenance (Support)

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.

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)

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.

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