Your SlideShare is downloading. ×
Software testing with Rational Teamtest
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Software testing with Rational Teamtest

970
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
970
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Software testing with Rational Teamtest Ashish Soni Lecturer, ITP [email_address]
  • 2. Outline
    • Miscellaneous testing facts
    • What is software testing?
    • Why do we test?
    • What methods and tools are available to test applications
    • Demo
    • Future
    • Conclusion and questions
  • 3. Interesting facts
    • Recent studies show that :
      • C++ : 25% more defects than C
      • A OO C++ defect takes 2-3 times as long to debug regardless of defect complexity
      • Inheritance engenders 6 times more defects
      • Java: multi-threading and inheritance: nearly impossible to write correctly and worse to test!!
      • No of lines of code in applications growing rapidly, e.g. Windows 3.1 – Windows XP
  • 4. What is software testing?
    • Finding out If something works or not
    • Determine if overall objectives are being met
    • Testing involves operation of a system or application under controlled conditions and evaluating the results
  • 5. Software Testing
    • Testing is the feedback mechanism in the software development process.
    • It tells you where corrections need to be made to stay on course at any given iteration of a development effort. It also tells you the current quality of the system being developed
  • 6. Why do we need to test?
    • Real life examples:
      • First US mission to Venus failed
        • (Reason: missing comma in a FORTRAN do loop)
      • Australia: Man jailed because of computer glitch. He was jailed for traffic fine although he had paid it 5 years ago
      • June 1996: Ariane-5 space rocket, self-destruction, $500 million.
      • (reason: reuse of software from Ariane-4 without recommended testing)
  • 7. Why testing?
    • Software is never correct no matter what development technique is used
    • Any software must be verified
    • Important to control the quality of the product
    • Very expensive:
      • In a lot of cases 50% of development costs
  • 8. Software quality
    • Software quality can be measured across 4 dimensions
    • Reliability
    • Functionality
    • Application performance
    • System performance
  • 9. Software development era
    • Over the past decade software development has changed radically
    • Client server era – annual releases of new versions of products
    • We also knew how many users we had since all users were employees
    • If system went down it could be restored from backup or orders were taken manually
  • 10. E-business
    • The big change right now is E-business Which includes e-commerce and ERP
    • Business process automated using the web.
    • Users are customers and not Employees!!
    • We cant send a broadcast to users saying “don’t login for one hour until we reboot the system” 
    • Lost customers = Lost Revenue ~ bankruptcy
    • This makes testing very important.
  • 11. Release checklist
    • Does the application operate without crashing, hanging or causing exceptions?
    • Does it meet your business requirements?
    • Has it been tested thoroughly to meet the demands of your customers?
    • Can you track your progress against requirements, defects and other metrics?
    • Does everyone on the team have the same critical testing information?
  • 12. Methodologies of testing
    • Glass box Testing
    • White box Testing
    • Structural Testing
    • All three methodologies involve testing internal code structures, loops etc.
  • 13. Methodologies
    • Black box and functional testing
      • Involves testing functionality of the application, interfaces etc.
  • 14. Web application testing methodologies
    • Performance
    • Functional
    • reliability
  • 15. Rational Team test
    • Suite of tools to automate the testing process
    • Provides tools for
      • Functional testing
      • Performance testing
      • Test case management
      • Defect Tracking and change requests
  • 16. Rational Team test
    • Major tools in test suite:
      • Rational Test Manager: Used to Manage all test activities:
        • Planning
        • Design
        • Development
        • Execution
        • analysis
      • Rational Robot: used to develop and execute functional tests for your windows and web applications
  • 17. Rational Team Test
    • Rational Administrator:
      • Used to create and manage rational projects
    • Rational Clearquest:
      • Used to track any kind of change activity associated with software development, these include enhancement requests, defect report etc.
  • 18. Rational Team Test
    • Rational Quality Architect:
      • Used to test middleware components built using EJB and com.
      • Virtual testing : scalability and workload , server response times
      • Functional and performance testing
  • 19. Rational Team Test
    • Site Check
      • Used to manage internet and intranet websites
  • 20. Installation and Setup guidelines
    • Standard Install
    • Build and setup examples provided with team test
    • Create a Project in Rational Administrator and associate various artifacts with the project
  • 21. Create Project
  • 22.  
  • 23. Project Artifacts
  • 24. Create Test Data Store
  • 25. Create Clearquest DB
    • You can use any of the Database below
      • Microsoft access
      • Microsoft SQL server
      • Oracle
    • Choice of DB depends on number of users of application
    • Pre-requisite: the Database has to be created before it can be associated
  • 26. Contd..
  • 27. Project status and details
  • 28. Rational Test manager
    • Once project has been created we are now ready to create test plans and test cases
    • You can associate test plans and test cases with your requirements
  • 29. Testing phases in RUP
    • 5 testing steps in RUP:
      • Planning – involves Test Plans
      • Designing – involves Test cases
      • Implementing – involves scriptst
      • executing
      • evaluating
  • 30. Testing lifecycle
  • 31. Test Manager
  • 32. Create a Test Plan
  • 33. Contd..
  • 34. Create test case folder
  • 35. Contd..
  • 36. Configure Test case folder
  • 37. Contd..
  • 38. Create Test Case
  • 39. Contd.
  • 40. Contd..
  • 41. Test cases
    • For each Test case you can:
      • Associate iteration
      • Associate configuration
      • Select manual or automated implementation
      • If automated then you can select appropriate test script
      • Specify pre and post conditions
      • Specify acceptance criteria
  • 42. Test Case properties
  • 43. Execute tests
    • You can execute test cases from Test Manager by selecting the “Run” option.
  • 44. Contd.
  • 45. Test manager
    • Lots more you can do with Test Manager!!
    • Execute other Rational applications
    • Please read documentation on rational CD.
  • 46. Rational Robot
    • Set of components for automating the testing of windows client /server and internet applications
    • Can record and playback:
      • GUI scripts: functional testing
      • VU scripts: performance testing
    • Proprietary language used to write scripts
    • Can use java or visual basic to write custom scripts
  • 47. Rational Robot
  • 48. Advanced Features
    • Performance testing using “virtual test” agents deployed on several client machines
    • Accepting test inputs from datapools : this requires knowledge of sqabasic language
    • Please refer to Rational documentation on CD for language details
  • 49. Rational Site Check
    • Internet and intranet website testing
    • Checks for broken links, structure etc
    • Can deploy website to target destination using Site check
  • 50. Demo
  • 51. Contd..
  • 52. Other Rational Tools
    • Rational test Factory – used to automatically detect bugs
    • Quality architect – EJB and COM testing
  • 53. Current issues
    • In addition to reliability and functionality software has to be secure!
    • Various hacks are made possible because of poor programming practices and inadequate testing (e.g buffer overflow)
    • Most hacked software : Microsoft IIS 
    • Shorter deadlines
    • Bug fixes open up new weaknesses in software
  • 54. Secure Programming Practices
    • Building Secure software – Addison wesley
    • www.shmoo.com – very good secure programming guidelines
  • 55. Additional resources
    • www.rational.com
    • Getting the most from your automated testing tool ( article rational edge magazine)
    • Automated Testing – silver bullet? ( article rational edge magazine)
  • 56. Did you know that:
    • Software testing consultants cost!
      • Junior level test engineer: $80 - $100 (1-2 yrs of experience)
      • Medium level test engineer - $100 - $150/ hr
      • Senior level test engineer : $150- $300/hour
    • If testing for security these figures go even higher
  • 57. Questions??