Role of a Quality Analyst

8/7/2019 Role of a Quality Analyst

http://slidepdf.com/reader/full/role-of-a-quality-analyst 1/31

Role of a Quality AnalystRole of a Quality Analyst



What is Quality AssuranceWhat is Quality Assurance

´The Quality assurance process is a

process for providing adequate

assurance that the software

products and processes in the

project life cycle conform to their

specified requirements and adhereto their established plans.µ



What is Quality ControlWhat is Quality Control

Quality control is a set of product

specifications which prioritizes and

links the product development

process so that it assures high quality as defined by the end-user.



Difference between QADifference between QA

and QCand QC

QC QA

Focused on improving

product quality

Focused on processes

and procedures

Verifies specificattributes of the product

Defn of work proceduresand guidelines

Specific products and

services

Sets measurement

program to evaluate

process

Focuses on inspection,testing and removal of

defects

Identifies weakness inthe process and improves

them

Responsibility of worker Responsibility of

Management

Doing good!! Doing right!!



The QA PhilosophyThe QA Philosophy

The inherent philosophy of Quality

Assurance for software systems

development is to ensure the system

meets or exceeds the agreed uponrequirements of the end-users; thus

creating a high-quality, fully-functional

and user-friendly application.



Quality AttributesQuality Attributes



Is There a Difference betweenIs There a Difference between

TestingTesting and Qualityand Quality AAssurance(QA)?ssurance(QA)?

The goals of testing and QA are

different:

The goal of testing is to find the

errors.

The goal of QA is to prevent the

errors in the program.



Phases of the TestingPhases of the Testing

ProcessProcess

1. Master test plan

2. Test requirements development

3. Test case design4. Test case development

5. Test execution

6. Results analysis



The Master Test PlanThe Master Test Plan

The testing group project plan

² Written for a testing phase

² Inputs: Development project plan, system

specifications Purpose

² Describes the scope, approach, resources,

and schedule of the testing activities

² Identifies features to be tested, testing tasks,people responsible for tasks, risks associated

with plans



Master Test PlanMaster Test Plan

Requirements and limitations ² Defines the goals of the testing process, technical

requirements imposed by the customer, by developers, or bythe product itself.

Items to be tested ² Identifies the software features and the combination of

features that will or will not be tested Testing approach

² Specifies the major activities, techniques, and tools which are used to test the designated group of features.

Success/failure criteria ² Defines criteria to determine whether test cases pass or fail

Exit Criteria ² Determines when to suspend, resume and exit the test cycle

Test environment ² Required hardware, software, configurations, operating

systems



Role and responsibilities ² Identifies the groups, staffing, and skills required for

managing, designing, and executing the testingproject.

Schedule ² Includes milestones in the testing project

Risks and contingencies ² Identifies high-risk issues and contingency plans



Test RequirementsTest Requirements

DevelopmentDevelopment

Writing test requirements

System Decomposition ² Divide system into manageable units

based on functionality, modules, or business areas

Specify test requirements

² Types of input (without specific data) ² Interactions

² Environment conditions

² Positive / negative requirements



Writing Test RequirementsWriting Test Requirements

Input sources

² Specification document (if exists)

² Internal/external documentation

² Interview developers ² Training materials

² Software itself

Tools

² Microsoft Word

² QSS Doors

² TBI Caliber



Designing TestsDesigning Tests

Design test cases that cross over requirements

² More efficient

² Minimize number of required tests ² Greater chance of detecting bugs

Create tests that cross over functional areas, based on possibleuser scenarios.

Find the ¶golden path· between sizeand maintainability



Test ContentTest Content

Developing a test

² Starting/environment conditions

² Test cases

Specific input data Expected results for each input

(Verification points)

² Test procedures (actions)

Reviewing a test ² Test design requires review and/or

debugging



Levels of TestLevels of Test

Basic/Sanity ² Most risky areas

² Most visible/frequently performed by users

² Address positive requirements

Medium/Standard ² The majority of the tests

² Combine positive/negative requirements

² Address requirements with high chance of customer execution

Advanced ² Mainly negative requirements

² Risky areas, but less likely to be reached by customer

² Complicated sequences





Order of Test ExecutionOrder of Test Execution

1. Big fixes verification

Perform even if no tests exist

Check fix and ¶around· fix

2. Change verification

New features

Modified features

3. Test cycle execution

Cycle- a group of tests executed

together with a common objective



Other Kinds of TestingOther Kinds of Testing

Black box testing

White box testing

Unit testing

Incremental integrationtesting

Integration testing Functional testing

System testing

End-to-end testing

Regression testing

Acceptance testing

Load testing Stress testing

Performance testing

Usability testing

Alpha testing

Beta testing

Mutation testing

Comparison testing

User acceptance testing

Ad-hoc testing Exploratory testing

Compatibility testing

Security testing

Recovery testing

Install/Uninstall testing



Independent VerificationIndependent Verification

and Validationand Validation

Software IV&V is a systems engineering processemploying rigorous methodologies for evaluatingthe correctness and quality of the softwareproduct throughout the software life cycle

Independent ² Technical: IV&V prioritizes its own efforts

² Managerial: Independent reporting route to ProgramManagement

² Financial: Budget is allocated by program andcontrolled at high level such that IV&V effectiveness isnot compromised

Verification (Are we building the product right?)

Validation (Are we building the right product?)



IV&V ApproachIV&V Approach



IV&V ActivitiesIV&V Activities



QA across the SDLCQA across the SDLC



Software used to Test aSoftware used to Test a

Quality SystemQuality System

TestDirector

Winrunner

QuickTest Professional

Loadrunner



TestDirector TestDirector

TestDirector provides the

framework for the entire testing

process

TestDirector affects the testing

process and organization

² Requirement Engineering

² Test Case Development ² Test Set Scenarios

² Defect Tracking



Mapping Customer Mapping Customer

Methodology to TDMethodology to TD

TestDirector implementation plan musttake into account:

Current state of the customer ² Project deadline

² Project status (stability, completeness)

² Technology

² Existing process & methodology

² Potential volume of testware

Customer expectations ² Short-term goals

² Long-term goals



Winrunner Winrunner

Creates automated scripts for GUI,

functional and regression testing of

the AUT

Uses multiple verification types to

ensure sound functionality



QuickTest ProfessionalQuickTest Professional

Provides the industry·s best solution for

functional test and regression test

automation

Introduces next-generation ́ zero-configurationµ Keyword Driven testing

technology in QuickTest Professional 8.2

Preserves your investments in Mercury

WinRunner test scripts, by leveraging TSL assets from QuickTest

Professional/WinRunner integration



LoadRunner LoadRunner

Prevents costly performance problems inproduction by detecting bottlenecks before anew system or upgrade is deployed

LoadRunner is used when:

² Trying to find how many users can be added withoutdecreasing system performance

² Which server to use for supporting multiple users

² Finding if the system response time meets therequirements

² Assessing whether the system is reliable enough to go

into production

² Finding what is the cause of performance degradation



Examples of QAExamples of QA

RequirementsRequirements



No More Questions PleaseNo More Questions Please

Role of a Quality Analyst

Documents