• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Testing -Don Gilman
 

Testing -Don Gilman

on

  • 413 views

 

Statistics

Views

Total Views
413
Views on SlideShare
413
Embed Views
0

Actions

Likes
0
Downloads
3
Comments
0

0 Embeds 0

No embeds

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
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Testing -Don Gilman Testing -Don Gilman Presentation Transcript

    • Software Testing in Small Teams Don R. Gilman, P.E.: Energy Systems Lab – TEES Advanced Gaming Systems Inc
    • The Presenters
      • Don
      • Professionally programming/managing IT applications since 1984
      • Contributed to over one million units of various computer games
      • Licensed Professional Software Engineer (one of about 35 in the entire US)
      • Member of the Software Engineering Task Force for the Texas PE Board
      • Manager, Software Engineering Group – Energy Systems Laboratory – TEES
    • Presentation Overview
      • What is testing?
      • What are the levels of testing?
      • Types of testing:
      • Who tests?
      • Case Studies
        • Unit Testing
        • eCalc Automated Testing
        • A Computer Game
      • Summary
      • Questions
    • What IS Testing?
      • IEEE : The process of operating a system or component under specification conditions, observing and recording the results, and making an evaluation of some aspect of the system or component.
      • Boehm : Verification and Validation
        • Verification – are we building it right?
        • Validation – are we building the right thing?
    • Testing is NOT
      • Code inspections
      • Design reviews
      • Configuration management
      • Bug tracking
      • These are, along with testing , are part of Software Quality Assurance (SQA). Together these improve the quality of the product
    • Types of Testing:
      • Scope
        • Unit
        • Module
        • Integration
        • Interface
        • Coverage
      • Purpose
        • Functional
        • Stress
      • Execution
        • Manual
        • Automated
      • Phases/Triggers
        • Nightly Builds
        • Defect Removal
        • Change Order Completion
        • Alpha
        • Beta
    • Who Tests?
      • Developers
        • Unit testing
      • QA Team
        • Module testing, automated testing
      • Software
        • Automated testing
      • Designers
        • Engineers, Analysts
      • Users
        • Unpleasant but true
    • Who … some thoughts
      • All New Members
        • To train
        • To get fresh test paths
        • In Industry – not a good model
        • In Gaming – a great way to recruit
      • Release/QA Folks
        • Typically Engineers or Accountants
        • CompSci typically make lousy testers
    • Case Study: Unit Testing What is Unit Testing?
      • Lowest Level of Testing
      • Programmer Safety Net
      • Instant Feedback
      • Documentation
    • Case Study: Unit Testing Good Unit Tests:
      • Tests functionality not edge cases
        • GOOD: 100 points damage to demon == death
        • BAD: referencing null demon throws exception
      • Capture the meaning behind the code in tests
    • Case Study: Unit Testing xUnit Tool:
      • Unit testing tools in many languages
        • .NET: NUnit
        • Java: junit
        • C++: CppUnit
      NUnit
    • Case Study: e 2 Calc
    • Case Study: e 2 Calc
    • Case Study: e 2 Calc
    • Case Study:Games
    • Case Study: Games
      • Manual Testing
        • Coder
        • Core team
      • Public Alpha/Beta Testing
        • Sometimes process andfocus areas listed on websites
      • Tools
        • Command lines for auto logging
        • Screen dumps
        • Saved games
        • Debug compiles
        • Game vs game – with new log analysis tools
    • Case Study: Games
    • Case Study: Games
    • Case Study: Games
    • Summary
      • Writing automated tests is one of the most difficult programming assignments
      • Design to Test
      • Let the computer do the dirty work
      • Not everyone is wired to do this – only the successful succeed.
      It’s done means it is DONE! Accurate deliveries Reliable Production Correct Code Maintainable Code
    • Resources
      • Software Development Magazine ( www.sdmagazine.com )
      • CrossTalk ( www.stsc.hill.af.mil /crosstalk )
      • Better Software ( www.stickyminds.com )
      • The Rational Edge ( www.rational.com )
      • SEI ( www.seir.sei.cmu.edu )
      • TDD, an Introduction: ( www.agiledata.org/essays/tdd.html#Figure1StepsOfTDD )
      • Object Mentor – TDD: ( www.objectmentor.com/writeUps/TestDrivenDevelopment )
    • SE Books we’ve read that matter
      • How to Win Friends and Influence People , Carnegie
      • Software Requirements , Wiegers
      • Agile Project Management , Jim Highsmith
      • Planning Extreme Programming , Beck/Fowler
      • Agile Project Management w Scrum Schwaber
      • Mythical Man Month , Brooks
      • Test Driven Development: By Example , Kent Beck
      • MS Solutions Framework Papers
      • Decline and Fall of the American Programmer , Yourdan
      • The E-Myth Revisited , The E-Myth Manager , Gerber
    • Questions?