• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Software Testing
 

Software Testing

on

  • 7,146 views

Learn about Software Testing

Learn about Software Testing

Statistics

Views

Total Views
7,146
Views on SlideShare
7,140
Embed Views
6

Actions

Likes
6
Downloads
0
Comments
7

1 Embed 6

http://www.slideshare.net 6

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

17 of 7 previous next Post a comment

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Hi can you pls send me this presentation to my mail id : brijeshkatkamwar4@gmail.com

    Very usefull and nice presentation :)
    Are you sure you want to
    Your message goes here
    Processing…
  • Hi ,
    It is a very imporant and impressive slide. Please send me the same at my email id at spshruti4@gmail.com
    Are you sure you want to
    Your message goes here
    Processing…
  • May Name is Sharif. I am very much impressed with the Slide Show. I request you to send me one copy as I am in need.

    cabdaoui@gmail.com
    Are you sure you want to
    Your message goes here
    Processing…
  • May Name is Sharif. I am very much impressed with the Slide Show. I request you to send me one copy as I am in need.
    Are you sure you want to
    Your message goes here
    Processing…
  • hi my name is krishnangshu u have made an excellent presentation can u pleaseeeee send it to my email id my id is krishnangshu@gamil..com it wiil be very help full since i dont have internet at home
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Rapid Business Driven Testing ver. 1.0.0 Page Student Study Guide

Software Testing Software Testing Presentation Transcript

  • NYC Technology Forum Introduction to Test Automation 11/2/07 All rights reserved Not to be reproduced without permission Bill Rinko-Gay Solutions Director, Software Quality Management John Stephens Practice Director, Software Quality Management
    • Get familiarized with basic concepts of Test Automation
    • Understand what it takes to implement effective Test Automation
    • Introduce techniques to emphasize maintainability
    Objectives
  • What is Test Automation?
  • Benefits of Automated Testing Examples
    • Run automated tests unattended (overnight)
    • Reliable, consistent testing
    • Increased speed in test execution
    • Increased test coverage
  • General Misconceptions About Automated Testing
    • Automation is simply “record and playback”
    • Automation is the “silver bullet” to solve all testing problems
    • Return on Investment will be achieved immediately
    • Automation will replace all manual test cases
  • What is Test Automation?
    • An enhancement on manual testing
    • Utilizes technology to provide repeatable, consistent testing of the Application Under Test (AUT)
    • Reduces costs and time for regression testing
  • Primary Goal of Automated Testing
    • To reduce number of tests to be run manually, not to eliminate manual testing altogether
    Automated Testing is an enhancement upon existing methodology and manual process
  • So, You Want to Implement Test Automation…
  • Challenges in Automated Testing
    • Test Automation is a development effort!
    • Automation is time consuming to create (and maintain, if poorly implemented)
    • Limitations of the testing tools and developer expertise
    • Automation of the wrong tests for the given constraints
    • Unrealistic expectations
  • Test Automation Checklist
    • Criteria for Automation
    • Tool – AUT compatibility
    • Test Automation Requirements
    • Implementation Design
    • Stable, isolated test environment
    • Test data
    • Implementation and coding standards
    • Maintenance
  • What to Automate? Choosing Ideal Manual Test Cases
  • Criteria for Automating a Test Case Why Automate? Selecting the right tests to automate is very critical to effective implementation!! Repetitiveness Test Cases that are to be performed repeatedly Test Cases that are business-critical and/or high risk Criticality Tedious Test Cases that are tedious to perform manually Time Consuming Test Cases that require considerable amount of time to perform manually
  • Test Automation Checklist
    • Criteria for Automation
    • Tool – AUT compatibility
    • Test Automation Requirements
    • Implementation Design
    • Stable, isolated test environment
    • Test data
    • Implementation and coding standards
    • Maintenance
  • Tool - AUT Compatibility
    • Conduct Proof of Concept of Tool on AUT
    • Navigate through functional areas to test
    • Verify Object Recognition of AUT
    • Determine whether tool selection is valid
  • Test Automation Checklist
    • Criteria for Automation
    • Tool – AUT compatibility
    • Test Automation Requirements
    • Implementation Design
    • Stable, isolated test environment
    • Test data
    • Implementation and coding standards
    • Maintenance
  • Test Automation Requirements Definition The set of criteria that the automated test suite must meet to be successful - the requirements for an automation project.
  • Test Automation Requirements What are the Success Criteria for the project?
    • Meeting the goals and objectives of the automation effort
    • Tool capabilities
    • Capabilities and skills of the test automation team
    Example Requirement: The test tool shall test the login functionality of a web application, on a Windows 2000 platform, and run unattended simultaneously on three PCs.
  • Planning for Test Automation Test Automation Requirements help drive and determine the approach and design of the implementation. Test Automation Requirements Test Automation Design/Approach
  • Test Automation Checklist
    • Criteria for Automation
    • Tool – AUT compatibility
    • Test Automation Requirements
    • Implementation Design
    • Stable, isolated test environment
    • Test data
    • Implementation and coding standards
    • Maintenance
  • Test Automation Methodology Analysis & Strategy Execution & Results Management Construction Design
    • Automation Architecture encompasses the environment for execution and development of an automated test suite. It is the overall scheme in which the test scripts will be developed.
    Implement a Test Automation Architecture
  • Designing the Test Automation Architecture Maximizing Maintainability
  • Automation Architecture Design Options
    • Capture/replay
    • Framework-based
    • Data-driven
    • Keyword-driven
    • Hybrid
  • Design Goals
    • Evaluate feasible design options for implementation
    • Anticipate likely changes to AUT
    • Consider skill level of team members developing and/or inheriting the automated scripts
    • Design of automated tests should address test automation requirements
  • Typical Design Components Subscripts Startup Script Data Table Driver Script Function Library
      • Compiled module containing application-specific routines and functions
        • A script that initiates automated test execution
    A script that performs a discrete portion of a business process to be tested
      • A script that sets up and standardizes test automation environment
    Data sources (such as spreadsheets) used to store test data for use during test execution
  • Test Automation Checklist
    • Criteria for Automation
    • Tool – AUT compatibility
    • Test Automation Requirements
    • Implementation Design
    • Stable, isolated test environment
    • Test data
    • Implementation and coding standards
    • Maintenance
  • Automation Test Environment
    • Stable and isolated environment is important for reliable execution of automated tests
    • GUI must be identical to Production
  • Test Automation Checklist
    • Criteria for Automation
    • Tool – AUT compatibility
    • Test Automation Requirements
    • Implementation Design
    • Stable, isolated test environment
    • Test data
    • Implementation and coding standards
    • Maintenance
  • Test Data Strategy
    • Create a test environment that is restorable to a known constant, such that the test cases can be repeated each time
    • Identify the procedure required for backup and recovery of data
    Test Data is critical to reliable automated testing!!
  • Creating Test Data Various Methods
    • Create test data through application by doing data entry
    • Import test data from production environment, if available
    • Develop automated test scripts to generate test data as prerequisite
  • Test Automation Checklist
    • Criteria for Automation
    • Tool – AUT compatibility
    • Test Automation Requirements
    • Implementation Design
    • Stable, isolated test environment
    • Test data
    • Implementation and coding standards
    • Maintenance
  • Coding Standards
    • Specify coding practices and naming conventions
    • May be based on standards in place for project’s AUT developers
  • Test Automation Checklist
    • Criteria for Automation
    • Tool – AUT compatibility
    • Test Automation Requirements
    • Implementation Design
    • Stable, isolated test environment
    • Test data
    • Implementation and coding standards
    • Maintenance
  • Maintenance
    • Start small and build on
    • Build modular components
    • Stay within scope of automation requirements
    • Adhere to defined standards and conventions
    Emphasize robustness and flexibility
  • Maintenance
    • Must be a good tester
    • Has programming background
    • Must be aware of maintenance and reliability
    • Must be motivated to develop and create automated test scripts
    Building an Automation Test Team Ideal characteristics of an Automation Engineer:
    • Get familiarized with basic concepts of Test Automation
    • Understand what it takes to implement effective Test Automation
    • Introduce techniques to emphasize maintainability
    Learning Objectives Revisited
  • Q&A