16
Commercial Database Applications Testing

Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered

Embed Size (px)

Citation preview

Commercial Database ApplicationsTesting

Test PlanTesting Strategy Testing Planning Testing Design (covered in other modules)Unit Testing (covered in other modules)System Testing System Integration Testing Acceptance Testing Regression TestingNegative Testing

Testing Strategy

Objectives:Vary depending on the project scenarioEnsure that all tests to be performed have

been identifiedFormal processes and procedures have been

developed to cover all test cases

Evaluation CriteriaTesting StrategyTesting strategy should include the following:

An outline of the aims and objectives agreed with the business and IT management

Detailed testing scenarios to be performedRoles and responsibilities assigned to each memberThe approach the organisation is going to follow to

ensure the testing phase is addressed accordingly Any requirements, either organisation specific or

regulatory which must be implemented during the testing phases

Testing Planning

ObjectivesEnsures that an implementation plan is

developed to cover Operational testing function

Done at the beginning of the software development.

Evaluation Criteria

When designing overall test plan consider stages Requirements stage Specification stage Design Stage Implementation StageOperational testing Post Implementation review

Design & Unit TestingCovered in:

CS22120Programming Modules

System TestingObjectives

Tests system in its entirety Ensures that the business function for which it

was originally intended is being metFunctional and performance testing

only complete and precise as designed from the design requirements

Evaluation CriteriaSystems TestingChecklist headings Function

System should meet specified requirements and hence supports business requirements

Load/StressSoftware should be tested at varying loads

VolumeHigh volumes of input data should be run under

continuous load conditions have been enteredHardware configuration and portability

Software should operate correctly across various hardware configurations

Evaluation CriteriaSystems Testing cont…Database Loading and data conversionSecurity

Security features should ensure access, integrity and recovery features operate as expected

PerformanceSystem should be operating as required under peak and

continuous loadsAvailability

IT service meets reliability objectives. If not, time taken to repair / downtime should be measured

Race ConditionsEntering transactions out of sequence to identify

whether software reacts correctly

System Integration TestingObjectives

Designed to confirm: All coding changes addressed to improve business

critical functions operate correctly Multiple applications or systems simultaneously

Evaluation CriteriaSystems Integration Testing

Integration Testing include: Point to Point

Very accurate and timely transmission of data between systems

End to End Testing Performed when a system is a chain has been

replaced or modified

Acceptance Testing

Objectives:After system testing and integration testingTo provide assurance that all system changes

and performance issues have been identified during previous test stages

Design changes meet original system / user specifications

Get Sign Off

Evaluation CriteriaAcceptance TestingIdeally carried after sign-off of system and

integration testing have been completed Acceptance testing procedures should

demonstrate:To users and computer operations staff

system as installed meets the contract conditions and/or acceptance test criteria such that the user is

prepared to authorise a system acceptance document.

The software does not affect either the functions or service levels of other IT services.

Regression TestingThe objective is to Replicate system transactions and processes

to ensure / verify that the “optimised/smarter” code functions correctly

Ensure no impact on any other modules within the overall system and therefore created further potential costly errors

Negative Testing

Used in all types of testingIt identifies how a system responds to incorrect

or inappropriate information being included within a text or numeric field.

Performed to ensure that the system is able to handle inconsistent information