Download as ODP, PPTX
Uploaded byPeter Presnell
I Smell A RAT- Rapid Application Testing
This document discusses various techniques for rapid application testing (RAT) such as unit testing, integration testing, smoke testing, system testing, regression testing, performance testing, and test-driven development. It emphasizes automating test plans and test execution to allow tests to be run multiple times for little additional cost. The goal of testing is to balance cost and risk by reusing automated tests that are fast and good predictors of issues while throwing more tests at critical areas.
More Related Content
Similar to I Smell A RAT- Rapid Application Testing
More from Peter Presnell
I Smell A RAT- Rapid Application Testing
- 1. I Smell ARAT Rapid Application Testing Peter Presnell (GBS)
- 2.
- 3. Contact Information Twitter: PeterPresnell
- 4. Blog: www.bleedyellow.com(www.planetlotus.org)
- 5.
- 6.
- 7. Sametime: Yellowbleederswww.bleed yellow .com
- 8. Effer Of TheIneffible Adjective Incapable of being expressed or described in words; inexpressible Not to be spoken because of its sacredness; unutterable
- 9. And So ToTesting.... “ Testing is an infinite process of comparing the invisible to the ambiguous in order to avoid the unthinkable happening to the anonymous ” James Bach
- 10. Are There Any Testers In The Room?
- 11. “ we haveas many testers as we have developers. And testers spend all their time testing, and developers spend half their time testing. We're more of a testing , a quality software organization than we're a software organization . ” Bill Gates (Information Week, May 2002)
- 12.
- 13. Test Planning Maketesting more of a science than an art
- 14. Unit Testing Applications work because each of the parts ( units ) do their job
- 15. Unit Testing LotusScript is easier to unit test than @Formula
- 16. OO LS is easier to unit test than Procedural LS
- 17. Java iseasier to unit test than SSJS
- 18. MY code is always easier to test than YOURS ! www.junit.org www.junit.org
- 19. Testing XPages? Medusawww.openntf.org
- 20. Integration Testing Validate the little bits with some big picture testing
- 21. Smoke Testing Thosetests which must always be executed every time
- 22. System Testing Whatdid we add ?
- 23. What did we change .
- 24. What did we fix ?
- 25. Regression Testing Ouch...did something else break?
- 26. Performance Testing Oneuser on a local workstation: OK 1,000 users on a shared prod. server: ???
- 27. Finding Memory Leakswww.yourkit.com
- 28. RAT: Kill BugsFaster
- 29. Rapid Application DevelopmentRAD is a methodology and NOT a speed contest
- 30. “Is That WhatYou Want”
- 31. XPages “ XPagesIs Less RAD Than Classic Notes” Peter Presnell, AUSLUG 2011
- 32.
- 33. Test Driven DevelopmentDefine your criteria for success before you start to write the solution
- 34. TDD: Example Requirement:Salary Field: Numeric TDD : When field contains non-numeric characters Fail …
- 35. When field iszero Fail ....
- 36. When field isnegative Fail …
- 37. When field isnot an integer Modify & Pass …
- 38.
- 39. Automated Test PlansMore time and effort should go into test planning than test execution . Rapid requires Automation
- 40. Automated Test ExecutionAutomation allows the same test to be run many times for little additional cost www.seleniumhq.org
- 41. The Art OfTrapping Notes Bugs?
- 42. DXL ... theanswer is out there
- 43. CRUD For eachForm/Object.... Can I Create , Read , Update , and Delete (where applicable)
- 44.
- 45.
- 46. UI Components Ensuringevery component behaves the way it should
- 47.
- 48.
- 49. UI State Forevery combination of Hide-When (Visible, Rendered) what can I see (or not see)
- 50.
- 51. Event Model What events do I have, and do they work at the correct time in the correct sequence ?
- 52.
- 53.
- 54. Event Model (ProgramLogic) www.aivosto.com
- 55. Styling Beauty isin the eye of the beholder
- 56.
- 57. Workflow Define andverify states and transitions
- 58. Building a “BeforeAnd After” Mousetrap
- 59. Common Scenarios Whowrote this $%&* code!
- 60. Migrating to a new release
- 61. Migrating to XPages
- 62. Adding a Mobile interface
- 63. True Or False?Our company's Notes applications are always well documented ?
- 64. True Or False?All of our Notes applications have formal test plans ?
- 65. True Or False?Most of our Notes applications have formal test plans ?
- 66. True Or False?Some of our Notes applications have formal test plans (I think)?
- 67. True Or False?None of our Notes applications have formal test plans ?
- 68. Ineffable? Does it still do what it did before ?
- 69. Before And AfterTesting Write One Set of Tests Compare Results
- 70. The Goal OfTesting
- 71. Cost Versus RiskKeep throwing more and more tests
- 72. Automated testsare faster (cheaper?)
- 73. Some tests arebetter predictors than others
- 74. Save all failed tests and re-use
- 75.
- 76. In Closing.... “Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code.” ~Dan Salomon
- 77.
Editor's Notes
- #5 Related Forms noun : i nefability, inefableness adverb : inefably