1 / 15

Automated Software Testing

Automated Software Testing. A Perspective. Article by Kerry Zallar of testingstuff.com Presentation by Michael Miller. Automated Testing. What is automated testing? Why automate? When and when not to. Important facts about automation. Training. Questions?. What is automated testing?.

iona
Download Presentation

Automated Software Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Automated Software Testing • A Perspective Article by Kerry Zallar of testingstuff.com Presentation by Michael Miller

  2. Automated Testing • What is automated testing? • Why automate? • When and when not to. • Important facts about automation. • Training. • Questions?

  3. What is automated testing? • Human tasks performed automatically • Types • Performance • Data Integrity • Functional

  4. How? • Automated Test Suites • IBM Rational Test (SQABASIC) • MercurySoft WinRunner/Quicktest (C) • Other programmable testing environments (Perl, Shell, etc) • Automate throughout the lifecycle

  5. Capture/Playback Pushbutton Click, “Text=OK”,””

  6. Example Server must report both bad passwords, bad usernames, and the absence of either or both, and allow entry for valid credentials This gives a number of test cases, all of which can be automated, and run quickly

  7. Automated Script ‘Test for bad login credentials EditBox Click,”Text=UID”,”” InputKeys “MyBadLoginName Pushbutton Click,”Text=login”,”” Browser NewPage,””,”” VerifyTableCell (“Text=Login Failed”, “Row=2;Col=2”) ‘Test for valid login Pushbutton Click,”Return” Browser NewPage,””,”” EditBox Click,”Text=UID”,”” InputKeys “Testuser23” EditBox Click,”Text=Password”,”” InputEncKeys ”13ad4c93d1f” Pushbutton Click,”Text=login”,”” Browser NewPage,””,”” VerifyTableCell (“Text=Welcome TestUser 23”,”Row=2;Col=3”)

  8. Result • This test is: • Fast • Computer types faster than a person • It doesn’t make typos • Re-runnable any number of times.

  9. Why? • FAST • Shorter development cycle • The computer seldom makes mistakes (But users sure do)

  10. When • When a test is performed frequently • When precision is a must • When the machine can perform much faster than the tester

  11. When Not To • When human vision is required • When the test does not answer a Yes/No question • When a test is too complex

  12. Important Facts • Automation does not replace manual testing • Automating only at the end of development will not work • Automation must be planned like the software itself • Automation must be modularized

  13. Important Facts • Test cases and test automation are created by different people • Analysts vs. QA Engineers • Automation is an investment • IBM Rational Robot = $3954

  14. Training • Must know or learn a language, such as BASIC, or C • Must learn the fundamentals of automated testing • Must learn how to use a particular automation tool

  15. ?

More Related