1 / 45

IBM RATIONAL TOOLS FOR TESTING Presentation: V ítek Linduška Demo: Václav Novotný

IBM RATIONAL TOOLS FOR TESTING Presentation: V ítek Linduška Demo: Václav Novotný. Agenda. Manual Tester Functional Tester Performance Tester ClearQuest. Manual Tester. Why Teams use Manual Testing?. Recruitment of subject-matter experts and end-users to test.

shea
Download Presentation

IBM RATIONAL TOOLS FOR TESTING Presentation: V ítek Linduška Demo: Václav Novotný

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. IBM RATIONAL TOOLS FOR TESTING Presentation: Vítek LinduškaDemo: Václav Novotný

  2. Agenda • Manual Tester • Functional Tester • Performance Tester • ClearQuest

  3. Manual Tester

  4. Why Teams use Manual Testing? Recruitment of subject-matter experts and end-users to test Strict regulatory or process requirements aren’t met with automation tools Poor or non-existent test automation-ready interfaces

  5. Challenges of Manual Testing “More time is spent maintaining test documentation than on executing tests.” • Labor Intensive • Too much time is spent creating and maintaining manual test documentation “We struggle to document even a minimum set of tests.”

  6. Challenges of Manual Testing “Our results are unreliable due to human error.” • Labor Intensive • Too much time is spent creating and maintaining manual test documentation • Unreliable • Inadvertent human-error often skews test results “Our tests aren’t detailed enough for the testers to consistently execute them.”

  7. Challenge Creating and maintaining manual tests is labor intensive and difficult with tools such as Microsoft Word or Excel. Share test content Challenge 1: Labor Intensive • Resolution • Implement a solution that promotes the best practice of modular tests which can share common content • Leverage existing Word or Excel test documents to quick-start test development

  8. Challenge Human error often skews tests results Challenge 2: Unreliable • Resolution • Assist testers with the tasks most prone to error – data entry and data verification • Build manual tests that are clear, concise and easy for the tester to follow

  9. Leverage Existing Test DocumentsImport from Word or Excel Microsoft Word documents • Jump-start adoption of Rational Manual Tester by leveraging existing assets • Bulk import manual tests documented in Word or Excel Rational Manual Tester test Microsoft Excel spreadsheets

  10. Assisted Data Entry and Data VerificationReduces human error • Store critical data used during the test as part of the test instructions Test execution window

  11. Assisted Data Entry and Data VerificationReduces human error • Store critical data used during the test as part of the test instructions • Automate data entry during test execution to speed entry and reduce errors Test execution window Application under test

  12. Assisted Data Entry and Data VerificationReduces human error • Store critical data used during the test as part of the test instructions • Automate data entry during test execution to speed entry and reduce errors • Automate data validation during test execution to ensure accurate results

  13. Enables Shared Content Across Multiple TestsReduces test maintenance and ensure consistency • Create commonly used test statements once • Reuse statements across multiple tests through simple drag and drop • Maintenance of shared content is efficient with single-point updating of shared content • Ensures consistency and reduces test maintenance

  14. On-Screen Prompted Test ExecutionImmediate and accurate results collection • On-screen prompting of test steps • Immediately record test results and attach images or files for clarity • Tool will assist with data entry and data verification • Results recorded in permanent log

  15. Spread-Sheet Ready Test ResultsUse with any 3rd party reporting tool • Results easily exported to common file format • Import into any 3rd party tool for evaluation and consolidation with other test data

  16. Functional Tester

  17. Manual testing can’t keep pace! ...the new tests... ...take more time Build 1 Build 2 Build 3, 4, 5 … Challenge of Manual Testing with Short Test Cycles • Manual testing alone can’t keep pace with the rapid development of applications • Quality will be sacrificed to keep on schedule Rerun the first tests and... Tests Time

  18. Challenges of Functional Testing “Our testers are not experienced in building automated tests.” • Controlling cost of test automation • Inexperienced testers face steep learning curve for tools • Test maintenance outpaces testing “Application UI changes are always breaking our test scripts.”

  19. Challenges of Functional Testing “Our script language limits our ability to overcome some automation obstacles.” • Control cost of test automation • Inexperienced testers face steep learning curve for tools • Test maintenance grows with project • Testing Tools Lack Flexibility • Power users hands are tied by tool limitations “I need one tool for both my expert and novice testers.”

  20. Challenges of Functional Testing “How do I keep my team in connected with the project team?” • Control cost of test automation • Inexperienced testers face steep learning curve for tools • Test maintenance grows with project • Testing Tools Lack Flexibility • Power users hands are tied by tool limitations • Test Team Integration • Managing script changes with parallel development • Sharing test assets with the larger software team “We’re geographically distributed and we’re worried about parallel script development .”

  21. Challenge Overcome the complexity of test automation to ensure teams spend more time on high value quality assessment rather than on low return test maintenance. Challenge 1: Controlling the cost of Automation • Resolution • Provide technologies to enable novice testers to craft complex tests with no programming • Data driven wizard • Dynamic data verification • Reduce script maintenance • Wizard driven global updates to centralized object map

  22. Challenge Fulfill both standard test needs as well as expert requirements to ensure usage limited only by the imagination of the project team. Challenge 2: Tools Lack Flexibility • Resolution • Provide two test script development languages • Java • Visual Basic .NET • Give professional testers the flexibility to overcome testing challenges in the language of their choice

  23. Challenge Accommodate the requirements of both dedicated, independent QA teams as well as integrated project teams to ensure high operational integrity. Challenge 3: Test Team Integration • Resolution • Provide version control support in the box with ClearCase LT • Provide integrations for standard version control features • Check In/Out • Compare withPrevious Versions • Show change history

  24. TesterSees ToolSees DeterminesMatch Reduce Test Script MaintenanceReliable Playback with Script Assure Version 1.0 Version 2.0 No User Intervention Required With ScriptAssureTM

  25. Performance Tester

  26. Challenges of Performance Testing • Complex Tools & Complex Task • Tool complexity and lack of experience intimidates many first time users “We don’t have a lot of experience building good load tests.” “Most load test tools are much more complicated than we require.”

  27. Challenges of Performance Testing • Complex Tools & Complex Task • Tool complexity and lack of experience intimidates many first time users • Testing Tools Lack Flexibility • Power users hands are tied by tool limitations “We don’t have a good understanding of what exactly is occurring during a load test.” “We have highly technical performance testers that need to customize their tests.”

  28. Challenge Tool complexity and lack of experience intimidates many first time users Challenge 1: Complex Tools & Complex Task • Resolution • Remove the need for programming • Tests are represented in a tree view as a sequential flow web pages • User interface enables • Data pooling • Data correlation • Looping • Conditional events

  29. Challenge Power users hands are tied by tool limitations Challenge 2: Tools Lack Flexibility • Resolution • Tests may call custom Java code provided by the user • Offers flexibility for power users to perform complex tasks • Expose behind the scenes details which are hidden from novice users by default • Provide the flexibility to overcome any testing obstacles

  30. Performance Problem Identification During Test Page Performance ReportShows average response time per page. Highest bar = Performance Problem • Performance Testing finds bottlenecks • Next logical question is Why? • Root Cause Analysis provides to tools to answer this question

  31. Performance Problem Identification During Test • Performance Testing finds bottlenecks • Next logical question is Why? • Root Cause Analysis provides to tools to answer this question

  32. Response Time Breakdown Response data broken down by tier and by transaction component (JDBC, JSP, Servlet, etc…) • Feature: • Breakdown page response times into composite element response time • Benefit: • Breakdown data drills down to highlight slowest components of a given page. Breakdown into tiers and components is a unique competitive advantage for RPT.

  33. Deep Diagnostic DataProviding the details you need to solve the performance problem mystery Execution Statistics Shows response time for every method UML Sequence diagram showing method calls between classes with timing information. User can drill down to source code.

  34. ClearQuest

  35. Eclipse Based Test Management Joins Functional and Performance Tester to complete transition of testing tools to eclipse platform Native and web clients also available Key Functional Areas Test Planning Create test plans, test cases and configured test cases Test Execution Create suites or run individual test cases Test Reporting Extensive query and reporting facilities to measure test progress Test Management with ClearQuestEclipse, Windows and Web Clients for test project tracking

  36. Lifecycle TraceabilityQuery one source for all aspects of project progress • Query to find • Test results associated to requirements • Defects associated to test results • Defects associated to tests associated to requirements • Traceability from requirements to tests and defects closes the loop on the software development cycle Defects Requirements Tests

  37. Leverage existing reports orCreate new reports with Crystal Reports To provide the information you need for decision making Lifecycle TraceabilityQuery one source for all aspects of project progress Test Verdicts Test Case Trending

  38. Instant access for remote users Access for alternative platforms No additional licenses required Perfect for test planning and reporting ClearQuest Web InterfaceDistributed access for test planning and reporting

  39. Automatic replication and synchronization of ClearQuest repositories Access current information, regardless of location Automatic recovery of repositories in the event of system failure maintains data integrity Transmission of only incremental changes for improved network performance ClearQuest MultiSiteReplication and synchronization for geographically distributed teams `

  40. Centralized User ManagementLDAP authentication for common user id support Reduce administration with centralized user management – maintain only one list of user idsLDAP authentication supports common user ids for ClearQuest and RequisitePro Rational ClearQuest Authorization Rational ClearQuest LDAP Rational RequisitePro Authorization Rational RequisitePro LDAP 3.0 Compliant Server Rational ClearQuest User DBLogon Dialog

  41. Compliance and ControlUsing Audit Trails and eSignatures to track change • Audit Trails can track changes to individual records • Provides immutable change log of all record change activity • e-Signature requirement can be added to any event on any artifact • Will record who changed a record, when and how the record was changed • e-Signature provides immutable evidence of process completion e-Signature Approval Requirement Test Case TestExecution ValidateResults Approve

  42. Configure and Enforce Your ProcessCustomize appearance and behavior of all forms and processes • Customize everything • Modify forms • Configure State Transition • Add fields and control behavior • Extend your system with custom coded hooks • Extend functionality using pre-defined Packages • eSignatures • Audit Trail • Many, many more…

  43. Collect and report on results from Rational test execution engines Rational Manual Tester Rational Functional Tester Rational Performance Tester Collect and report on results from Eclipse Test and Performance Tools Project jUnit tests Manual tests URL tests Open API Extensibility SPI Dynamics QAInspect Extensible Test EcosystemIntegrated with Rational, open source and 3rd party test automation tools

  44. Rational Software Quality Solutions BUSINESS SOFTWARE QUALITY SOLUTIONS Test and Change Management Defects Change Test Requirements Rational RequisitePro Rational ClearQuest Rational ClearQuest Rational ClearQuest Test Automation OPERATOINS DEVELOPMENT Functional Test Developer Test Performance Test Rational Functional Tester Plus Rational PurifyPlus Rational Performance Tester Automated Manual Rational Test RealTime Rational Functional Tester Rational Manual Tester Rational Robot Quality Metrics Quality Reports Detailed Test Results Project Dashboards

  45. WAKE UP, IT’S DEMO TIME!

More Related