Mirasoft Group Software Testing Services

Mirasoft Group Testing Competence

Perform full-cycle of software testing

Elaboration of test specifications

Development of test scripts for automatic

testing

Validation and verification of working product

Review services (such as architecture review

and code review).

Wide range of testing tools 12 types of testing (functional, performance, …) Testing as a part of project and dedicated testing Testing on different phases Testing Skills at a Glance

Testing in Development Life Cycle (simplified) Inputs: Project scope, SRS, SDP, SDD, Work Products. Outputs: Test Plans, Surveys, Protocols, Test Scripts, Reports, etc. Offer Customer + Contractor Requirements (SRS) Customer + Contractor Design Specification Contractor Code Contractor Unit-Testing Contractor Verification Contractor Acceptance (validation) Customer + Contractor User’s Request Accepted System Testing

Legend: STS = software Test Survey = software test specification CC = change control = change management Product Testing. Sub-processes Planning Product Testing

Identify Test Team

Identify Test environment

Determine Test Strategy

Determine Test types and levels

Elaborate Test considerations

Estimate Test Schedule and Efforts

Document Test Plan

Review Test Plan with Project Team

Approve Test Plan

Designing Tests

Design Test Cases

Design Test Data

Design Test Scenarios

Document STS

Review STS

Approve STS

Preparing Test Facilities

Prepare Test Data Acquire or Develop Test Tools

Develop Test Automation

Verify Test Tools and Test Automation

Testing

Prepare Test Environment

Prepare Test Protocol

Test Product /Components

Record Test Results

Submit CC Issues Analyze and Report Test Results

Resolving Test Issues

Resolve CC

Issues

Track CC Issues up to Closure

Define Test Strategy & Plan Test Objectives

Demonstrate usability

Check interfaces

Prevent defects

Verify product requirements

Resources

Equipments

Time

People

Skills

Risks

Quality Requirements

Impact of Failure

Likelihood of defects

TEST PLAN STRATEGY Test Tools

Software, which will be used

Test Environment

Equipments

System environment

Simulations

Work product items

Product items, which

should be tested

Test Types & Levels

Unit, Functional, Regression,….

System, Load, Performance….

Test Requirements

Contractual Provisions

Requirements stages and methodologies

Evaluation Activities (security, scalability, etc)

Customer’s Needs Product New Validation Validation (by CMMI-SW) confirms that the product, as provided, will fulfill its intended use. In other words, validation ensures that “you built the right thing.” Validation

Functional Testing

Negative Testing

Load Testing

Business Cycle Testing

Automatic Testing

Testing Types

Test Types and Levels (Mirasoft Group Projects' Experience) Ad hoc Functional Performance Load Stress Installation Usability Configuration … Unit Integration Regression System Acceptance Alpha Beta

Equivalent Decomposition

Boundary Values Analysis

Conditions’ Transition Analysis

Negative Testing

…

Functional Testing Methods

Emulation of next situations (examples):

Hardware problems

Insufficient memory (RAM)

Insufficient free space (HDD)

Unexpected power off

Network problems

Network cable is unplugged

Host is unreachable

Database problems

Database is down

Corrupted database

Maximum connections reached

Stress Testing

Testing of different sequences of actions

for assumed business usage of the product

Example for command line tool business testing: Business Cycle Testing Requirements Instructions Expected results 1. Creating of DB connection, schedule the scan (Input file 1) Execute cli.bat –f business_2_1.xml Database connection and scheduled scan are successfully created. Success message is logged. 2: Make change in target DB Change permissions for some DB user Permissions for some DB user is changed 3. Generating of the report of scanning (Input file 2) Execute cli.bat –f business_2_2.xml Xml report file is successfully generated. Success message is logged. 4. Cleaning of scheduler, deleting of DB connection (Input file 3) Execute cli.bat –f business_2_3.xml Scan schedule and database connection are successfully deleted from the system. Success message is logged.

Test Cases which operates with big amounts of data (e.g. 10 times bigger than assumed for standard usage)

Large input/configuration files

Big number of records for lists

Large text in input controls

Large files for upload/download

Example for command line tool Volume testing Volume Testing Requirements Instructions Expected results TC 1 Big input file Prepare big input file. Specify files with 100, 500, and 1000 tasks. Run Project1 by turn. There are no unexpected exceptions during the application’s work. All tasks are done. TC 2 Big Project1 log file Prepare Project1 log file with 1000 lines. There are no unexpected exceptions during the application’s work. Correct information is placed in Project1 report. TC 3 Big Project2 report file Specify big value of Runs parameter (500, 1000 last scans). Run CLI by turn. There are no unexpected exceptions during the application’s work. Correct information is placed in Project1 report.

Financial Reasonability Cost Time Manual Testing Breakpoint achievement (example): script should be run >10 times Automated Testing Automatic Testing Breakpoint

ORGANIZATION OF TESTING PROCESS

Full cycle of QA for Database security system (12 persons intended):

Manual and Automated Functional testing (more than 3k Test Cases)

Automated regression testing

Bugs and Enhancements Reporting

Business cycle testing

Performance/Load testing

Tools used:

Mercury Quality Center

Mercury Quick Test Professional

Own Test Engine

Bugzilla

Newsgroups

Example of QA / Testing Project

Platforms:

Tools:

Windows, Linux, Mac, UNIX (HP, Sun), Mainframes (S/390, AS/400)

.NET, XML/XSL, COM/DCOM, JSP, EJB, Web Services, J2EE/CORBA

Object/Transaction Oriented, Mainframe

Client-Server, Distributed

Manual and Automated Testing: Mercury Interactive (QTP, Win/Load

Runner, Quality Center), Rational Test Suite, NUnit, Junit, Apache Jmeter,

own tools.

Bug Tracking: MS Outlook/Excel, Mozilla Bugzilla, Mercury Test

Director/Quality Center, Benjamin, Star Team, PVCS Tracker , MIS

(internal change management and defect tracking system)

Documentation storing, version control : Microsoft Source Safe, CVS,

Star TeamPVCS (Tracker, V ersion Manager)

Testing Tools & Platforms

We use bug tracking tools and test protocols that help programmers, project managers, test engineers, customers and top management to report, diagnose and remove bugs promptly. All found defects should be registered in bug tracking system. Life cycle of some bug s includes such statuses as : New (or submitted); Assigned (or opened); Resolved; Verified; Closed. We use MS Outlook as bug tracking system. Bug Tracking & Change Control

Design Test Cases ( example ) Interface Specification Test Specification Designing Tests IUnknown Indicator IDispatch IInput IOutput IUnknown Indicator IDispatch IInput IOutput IUnknown TestDriver

Grey Box Black Box White Box Testing Methodologies Testing Tools & Platforms Problem Report Result Input Output Require- ments User’s Guide Standards Test Specifi- cation Expected Output Compare Test Protocol Passed  Failed  Require- ments Design Standards Code Problem Report Result Input Output Test Speci- fication Compare Test Protocol Passed  Failed  Expected Output Require- ments Standards Design Problem Report Result Input Output Test Speci- fication Compare Test Protocol Passed  Failed  Expected Output

Software Requirements Specification (SRS)

Software Development Plan (SDP)

Software Design Document (SDD)

CC Issues

Work Products to be tested

Inputs:

Software Test Plan (STP)

Software Test Survey (STS)

Test Checklists

Test Protocols

Test Reports

Problem Report (PR) Issues

Test data

Test scripts

Test Tools

Outputs: Product Testing. Process Flowchart

Determine Test Types and Levels (example) Unit Integration Regression System Acceptance Alpha Beta Ad hoc Functional Performance Load Volume Stress Security Reliability Configuration Compatibility Usability Installation Other ( Localization, Business case, Documentation, …)

Unique Test-cases Test-cases Repeatability % Script should be run > 10 times Releases F requency Automated Testing Break Point Factors

Thank you for your attention! Mirasoft Group Kiev , Ukraine +380 44 4929960 [email_address] www.mirasoft-group.com