Fundamentals

Fundamentals

1) Conducting
2) Software Development Life Cycle
3) Phases of Software Development Life Cycle
4) SDLC Models
5) Software Test Levels
6) Software Test Types
7) Software Test Design Techniques
8) Important phases inwards Software Test Process or Life cycle
9) Important tasks inwards Test Planning Phase
10)  Important tasks inwards Test Design Phase
11) Important tasks inwards Test Execution Phase
12) Important tasks inwards Test Closure Phase
13) Important Organizations for Software Quality Standards     
14) Important Software Test Documents
15) Important Job Titles inwards
------------------------------------------------------------

1) Conducting
 

tin hold upwards done inwards 2 ways 1 is Manual Testing, around other is Test Automation or Automated Testing. You tin utilisation both Manual Testing too Automated Testing to Test the Computer Software too Mobile Software.

Testing reckoner software manually inwards social club to honor defects without using Automation tools or automation scripts is called equally Manual Testing.

Testing Computer Software past times using Automation tool or Automation script is Called equally Automated Testing or Test Automation.


2) Software Development Life Cycle
 

SDLC (Software Development Life Cycle) is the procedure of developing software through concern needs, analysis, design, implementation, testing too unloosen & maintenance.

SDLC is also called equally Software evolution process.


3) Phases of Software Development Life Cycle

SDLC phases too stage names may vary from 1 model to another, exactly purpose is close all same,

Phases of SDLC are:

i) Requirements Gathering

ii) Analysis too Planning

iii) Software Design

iv) Coding/Implementation

v) Testing

vi) Release too Maintenance

4)
Software Development Life Cycle Models
 

A good defined too designed approach to railroad train Software. 

Or

SDLC model is a methodology or process that is beingness selected for the development of the Software project.


Important SDLC models are:

i) Waterfall Model

ii) V Model

iii) Spiral Model

iv) Agile Models (Agile Methodologies) etc...


5) Software Test Levels
 

Test Level: Influenza A virus subtype H5N1 grouping of Test activities that are organized too managed together.

We convey Four levels of Testing for General or independent Software applications

i) Unit Testing 

Testing of private software components.
Testers: Developers

ii) Integration Testing Testing integration or interfaces betwixt components, interactions to unlike parts of the scheme such equally an operating system, file scheme too hardware.
Testers: Developers or Independent Testers

iii) System Testing Testing an integrated System to verify that it meets specified requirements.
Testers: Independent Testers

iv) Acceptance Testing    

    
    a) User Acceptance Testing 
    Testers: Customers /End users

    b) Operational Acceptance Testing
    System Administration staff.

    c) Certification Testing
    Testers: Certified Testers

For distributed Software applications nosotros convey Five levels of Testing

i) Unit Testing

ii) Component Integration Testing

iii) System Testing

iv) System Integration Testing

v) Acceptance Testing

6) Software Test Types
 

Test Type: Influenza A virus subtype H5N1 grouping of Test activities aimed at testing a cistron or scheme focused on a specific objective.

Basically nosotros convey 2 Types of Testing,

i) Functional Testing
    Functionality Testing
    Security Testing

ii) Non Functional Testing
    Performance Testing
    Usability Testing
    Configuration Testing
    Reliability Testing
    Recovery Testing
    Localization Testing etc...

7) Software Test Design Techniques
 

Basically nosotros convey 2 types of Test pattern techniques,

i) Static Techniques
ii) Dynamic Techniques

i) Static Techniques
Static testing is the testing of the software piece of job products manually, or amongst a fix of tools, exactly they are non executed.

Example: Reviews, Walk trough, Inspection etc...

ii) Dynamic Techniques
 

Testing that involves the execution of the software of a cistron or system.

a) White box Test pattern techniques   
    Statement testing
    Condition testing
    Decision testing etc...

b) Black box Test pattern techniques   
    Equivalence partitioning / Equivalent Classes
    Boundary Value Analysis
    Decision tables
    State transition Testing
    Use representative Testing etc...

c) Experience based Techniques   
    Error Guessing
    Exploratory Testing etc...


Note:
Exhaustive testing (Testing amongst all possible inputs too preconditions) is impractical, too then inwards social club to bring down the Input too Output domains nosotros utilisation Test pattern techniques. 

8) Important phases inwards Software Test Process or Life cycle

i) Test Planning
ii) Test Design
iii) Test execution
iv) Test Closure.

9) Important tasks inwards Test Planning Phase

Important tasks inwards Test Planning phase are:

Understanding too Analyzing the Requirements
Risk Analysis
Test Strategy implementations
Test Estimations(Scope, Time, Available resources, Budget etc...)
Team formation
Test computer programme documentation
Configuration management planning
Creating RTM document
Define Test Environment Setup etc... 


10) Important tasks inwards Test Design Phase

Important tasks inwards Test Design phase are:

Understanding Requirements
Creating Test Scenarios
Test Case documentation
Test Data collection


11) Important tasks inwards Test Execution Phase
 

Verify Test Environment setup
Create exam batches
Test Execution
        • Smoke Testing /BVT/BAT
        Comprehensive Testing
        Defect Reporting
        Defect Tracking

        • Sanity Testing
        Select Test cases for Regression Testing
        Regression testing cycle 1
        Defect Reporting
        Defect Tracking

        • Sanity Testing
        Select Test cases for Regression Testing
        Regression testing cycle 2
        .
        .
        .
        Final Regression

12) Important tasks inwards Test Closure Phase
 

Collect all Artifacts
Evaluate the Exit Criteria
Test Summary Report
Sending Test deliverables to customer
Improvement suggestions for hereafter projects.

13) Important Organizations for Software Quality Standards      
 

ISO (Terminology, Process guidelines etc...)
IEEE (Terminology, Test Documentation standards)
CMM/CMMI (Process)

14) Important Software Test Documents


Important Software Test documents are:

i) Test Policy
A high marking (company level) document describes principles, approach too major objectives of the scheme regarding Testing.

ii) Test Strategy
A high marking document of the Test Levels to hold upwards performed too the Testing inside those levels for an Organization.

iii) Test Plan
A document describing the scope, approach, resources, too schedule of intended activities.

iv) Test Scenario
An item or trial of a cistron or scheme that could hold upwards verified past times 1 or to a greater extent than Test cases.

v) Test Case
A fix of input values, execution preconditions, expected resultant too execution post service weather developed for a detail objective or Test condition.

vi) Test Data
Data that exits earlier a exam is executed too that effects or is effected past times the cistron or System nether test.

vii) Defect Report
A document reporting of pismire flaw inwards a cistron or System that tin movement the cistron or scheme to neglect to perform its required function.

viii) Test Summary Report
A document summarizing testing activities too Result. It also contains evaluation of the corresponding exam items against move criteria.


15) Important Job Titles inwards  

Job Titles may vary from 1 companionship to another,

i) Test Lead

ii) Tester / Test Engineer 
------------------------------------------------------------

Sumber http://www.gcreddy.com/
Post a Comment (0)
Previous Post Next Post