SQA Processes: How to Test Complete Application?

Is there any normal process to take a look at the applying as an entire? Or How can I take a look at the entire utility proper from the Requirement gathering section?

This tutorial consists of your entire steps to take a look at the applying: These are the usual SQA processes to be adopted in any utility testing.

SQA Processes: How to Test Complete Application?

Marketing Requirements

The advertising and marketing necessities embrace:

• Review of the Objectives set for the Last Released Build.
• Objectives remaining to be accomplished are carried ahead for the following launch.

Branching for the Development Cycle

Objective Settings for the Major and Customized Releases.

Target Date deliberate for the Releases and determination on your entire mission schedule that it’s required to obtain these goal dates.

A Detailed Project Plan and the Release of Design Specifications

This consists of the choice on Design Specifications (Products), evaluation of the design specs, and growth schedule. This includes the QA throughout the section of evaluation.

QA – Develop Test Plan based mostly on Design Specifications

Test Plan: This is a top-level doc that talks about how the product goes to be examined. This consists of aims, the strategy adopted whereas testing, options to be examined and never to be examined, danger standards, testing schedule, cross-platform assist, and the useful resource allocation for testing.

Feature Test Plan: This doc explains how the testing goes to be carried out for every kind of testing.

QA – Functional Test Specifications

This doc consists of technical particulars (Software necessities) required prior to testing. It is vital from the tester’s standpoint to perceive and plan the technical assets prior to testing.

Application Development: Considering the product options, the tester has to make his/her personal take a look at go well with.

QA – Writing of Test Cases (CM)

• Smoke (BVT) Test Cases
• Sanity Test Cases
• Regression Test Cases
• Extended Test Cases
• Negative Test Cases

Development

Installers Binding and Building

• Installers are constructed across the particular person product.
• Release Engg is chargeable for releasing the Builds.
• Release Engg collects recent/developed code from the developer’s initially/module clever.
• Installers have to maintain jar recordsdata updating, registry entries, and extra software program installations.

Build Procedure

• A construct consists of installers of the out there merchandise – a number of platforms.
• For every construct, one or 2 CDs are made/construct the identical is pushed to Pune/Chennai based mostly on the precedence.
• Each product construct is obtained within the type of zip recordsdata underneath http://pun-qaftp/ftproot/QA-Builds (Pune-Specific). The process goes alongside for Chennai. San Jose QA picks up builds from Nexus (Build Specific Server).
• The identical zip recordsdata want to be unzipped to get the specified installer, and the identical is put in Pun_fps1/QA/Builds folder. (Pune-Specific)

QA – Testing

• Smoke Test (BVT) to test the fundamental options of the product.
• Smoke Test outcomes have to be posted on http://Chaquita which is an official web site for posting Smoke Test outcomes and to share the fundamental testing info.
• Prepare a Smoke Test process.

QA – Extensive Testing

• Testing of recent options
• Document evaluation
• Cross-platform testing
• Stress testing and Memory Leakage testing.

QA- Bug Reporting

• Use of Trackweb’s “Soffront” because the Bug Tracking software.
• Further FET (Fixed Effectiveness testing) of the filed bugs.
• Exception examine and verification.

Development – Code freeze

• No extra new options are added at this level.

QA – Testing

• Candidate Builds and regression testing.

QA- Media Verification

• CDs are lower for the launched merchandise and the product is put in utilizing these CDs and it takes place in San Jose.

Decision to Release the Product

A evaluation assembly to analyze the efficiency of the product, which is about, and the identical is in contrast with the aims set.

Post-Release Scenario

• One department is stored for the post-release modification and therefore the product testing.
• A Post-Release evaluation assembly to resolve upon the aims for the following launch.

Please share your ideas within the feedback part beneath!