DOCSLIB.ORG

Software Testing Tools

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Software Testing Tools SOFTWARETESTINGTOOLS PenttiPohjolainen DepartmentofComputer ScienceandApplied Mathematics UniversityofKuopio March2002 2 CONTENTS 1Introduction ............................................................................................. 5 2References............................................................................................... 10 3DivisionoftheTools .............................................................................. 11 3.1TestDesignTools.........................................................................................................11 3.1.1TestCaseTools ...........................................................................................................11 3.1.2DatabaseTools.............................................................................................................12 3.1.3DataGenerators...........................................................................................................13 3.1.4GeneralTestDesign ...................................................................................................14 3.2GUITestDrivers...........................................................................................................16 3.3LoadandPerformanceTestingTools.................................................................25 3.4TestManagementTools ............................................................................................32 3.4.1CORBA .........................................................................................................................32 3.4.2C/C++.............................................................................................................................33 3.4.3Others.............................................................................................................................36 3.5TestImplementationTools ......................................................................................48 3.5.1Java .................................................................................................................................48 3.5.2C/C++.............................................................................................................................51 3.5.3Others.............................................................................................................................53 3.6TestEvaluationTools.................................................................................................58 3.6.1Java .................................................................................................................................58 3.6.2C/C++.............................................................................................................................60 3.6.3Others.............................................................................................................................65 3.7StaticAnalysisTools ..................................................................................................69 3.7.1Java .................................................................................................................................69 3.7.2C/C++.............................................................................................................................71 3.7.3Others.............................................................................................................................75 3 4 1Introduction Thisworkstartedfromthesubjectofmyprograduthesis“Thenewestmethodsandtoolsfor softwaretesting”.Afteralongsearchtherewerenearly600(sixhundred)toolsfound.Iamsure, thattherearetoolsmuchmorethanthesenowoccurred.Averygoodaidtomewasthelistin Internet(www.testingfaqs.org),whichBrianMarickmadefamousandisnowmaintainedbyDanny Faught.OthersourceshavebeenInternetoverall,thebrochuresoftheproductsandtheliterature. Becausetheamountofthetoolswassolarge,Ihadtorestrictthemandtotakeuponlythemost interestingonce.Thedivisiontothemaingroupswas:Design,GUI(GraphicalUserInterface), LoadandPerformance,Management,Implementation,Evaluation,StaticAnalysisandoutsideof inspection:DefectTracking,WebSitesandMiscellaneous. Thelimitsbetweenthegroupsareoutoffocus,becausetherearemanytools,whichcanbelongto severalclasses(SeeFigure1.). Design StaticAnalysis Implementation Management GUI Evaluation Loadand Performance Figure1.TheDivisionofthetools 5 Ashortdescriptionofthemaingroups: TestDesignTools Toolsthathelpyoudecidewhattestsneedtobeexecuted.Testdataandtestcase generators. Total15tools. GUITestDrivers Toolsthatautomateexecutionoftestsforproductswithgraphicaluserinterfaces. Client/servertestautomationtools,includingloadtesters,alsogohere. Total28tools. LoadandPerformanceTools Toolsthatspecializeinputtingaheavyloadonsystems(especiallyclient-server systems).ThesetoolsareoftenalsoGUItestdrivers. Total21tools. TestManagementTools Toolsthatautomateexecutionoftestsforproductswithoutgraphicaluserinterfaces. Alsotoolsthathelpyouworkwithlargetestsuites. Total43tools. TestImplementationTools Miscellaneoustoolsthathelpyouimplementtests.Forexample,toolsthat automaticallygeneratestubroutinesgohere,asdotoolsthatattempttomakefailures moreobvious(assertiongenerators,etc.) Total27tools. TestEvaluationTools Toolsthathelpyouevaluatethequalityofyourtests.Codecoveragetoolsgohere. Total31tools. StaticAnalysisTools Toolsthatanalyseprogramswithoutrunningthem.Metricstoolsfallinthiscategory. Total33tools. Totalsum198tools. InPlugIT-projectinterestingtoolsareatleast:Regression,requirement,component,integration, object-oriented,coverage,testcaseandusecase. Searchingwiththesewordstherecent198toolstheresultswere: RegressionTools Regressiontestingtoolsareusedtotestsoftwareaftermodification.Dividingin groupsasabove(oneortwotypicalexamplespergrouparepresented)therewere: Design:None GUI:AutoTesterforWindows(No3)isspecificallymeanttosupportprojectteams inautomatingregressiontesting.Others4,6,12,15and27. LoadandPerformance:TeleprocessingNetworkSimulator(No20)canbeusedto automateregressiontesting.Others10and12. Management:TestManager(No2)providesaninteractivedevelopmentenvironment forworkingwithregressiontestsuites.OTF–OnObjectTestingFramework(No18) isatoolforSmalltalkobjects,inwhichregressiontestingisautomaticwithfull loggingofresults.Others1,4,5,10,14,16,27,28,29,37and38. Implementation:Junit(No5)isaregressiontestingframeworkusedbydevelopers whoimplementunittestsinJava.Others1,15and18. 6 Evaluation:Logiscope(No26)identifieseffectivenonregressionifprogramfiles havebeenmodified. StatisticAnalysis:ParaSoftJtest(No6)automaticallyperformsregressiontestingof Javacode. Total28tools. RequirementTools Requirement-basedorrequirementdefinitionrelatedtools. Design:Caliber-RBT(No1)isatestcasedesignsystemforrequirement-based testing.Others6and15. GUI:Panorama-2(No8)isatoolforrequirementanalysis.Another17. LoadandPerformance:SilkRealizer(No19)isatoolthatenablesusersdevelopeand deploysystemleveltestingsimulatingrealworldeventstoassurethatapplications willmeettherequirements. Management:AutoAdviser(No13)providesfromrequirementsthroughproductiona centralrepositoryfororganizingandmanagingbusinessrequirements,testsand associatedfiles.Others18,21,35and37. Implementation:None Evaluation:PanoramaC/C++(No15)isarequirementandtestcaseanalysistool. StaticAnalysis:None Total12tools. ComponentTools Tools,whichhavesomerelationshipswithcomponent-programming. Design:Inferno’s(No2)capabilitiesincludecreationofanintuitivelibraryof reusablecomponentsthatsupportshared-scriptsanddata-driven-scripts. GUI:None LoadandPerformance:None Management:SilkPilot(No1)letsyoutestthebehaviourofdistributedobjectswithin yourapplication’sservercomponents.AutoAdviser(No13)consolidatesyourtest librarycomponentsandprovidestestteammemberswithaccesstothosecomponents. Others2,32,40and42. Implementation:AssertMateforJava(No2)isasystemthataidsJavaengineersuse assertionstoensureproperimplementationofcomponentinterfaces.Another1. Evaluation:QC/Coverage(No16)helpsusersbyidentifyingcodecomponentsthat havenotbeenadequatelytested. StaticAnalysis:WhiteBox(No33)provideinsightintothecomplexityofdifferent componentsofthesoftware. Total11tools. IntegrationTools Toolsusedwithintegrationtesting. Design:ObjectPlanner(No13)allowssoftwaredevelopersandmanagerstocalculate theapproximatetimeschedulestoperformunitandintegrationtesting.Another15. GUI:SolutionEvaluationTool(No14)isusableintestingtheintegrationofnew applications. LoadandPerformance:None Management:Cantata(No3)isasolutionforunitandintegrationtestingofCand C++code.Others5,6,14,25,32and40. Implementation:Autotest(No14)isanautomatictestharnesstoolforintegration testing.Another15. Evaluation:Cantata++(No7)isaneffectivetoolforC++integrationtesting.Others 18and27. 7 StaticAnalysis:None. Total15tools. Object-orientedTools Toolsusedspeciallywithobject-orientedsystems.AllJavaandC++toolsfall automaticallyinthiscategoryalthoughthesearchhasnotfoundthemwithkeyword object. Design:T-VECTestGenerationSystem(No15)isintegratedinanenvironmentto supportthedevelopmentandmanagementofstructuredorobject-oriented requirementsspecifications.Another12. GUI:VermontHighTestPlus(No23)includesobject-levelrecord/playbackofall WindowsandVBcontrols.Others4,8,16,17,18and27. LoadandPerformance:None Management:TOOTSIE(No42)isatotalobject-orientedtestingsupport environment.Others1,2and18. Implementation:ObjectTester(No11)isasoftwaretooltoautomatethegenerationof C++unittestscripts.Others1and2. Evaluation:TotalMetricforJava(No1)isasoftwaremetricstooltocalculateand displayobject-orientedmetricsfortheJavalanguage. StaticAnalysis:ObjectDetail(No12)isasoftwaretooltohelpautomatethemetrics
Load more

Recommended publications
  • Types of Software Testing
    Types of Software Testing We would be glad to have feedback from you. Drop us a line, whether it is a comment, a question, a work proposition or just a hello. You can use either the form below or the contact details on the rightt. Contact details [email protected] +91 811 386 5000 1 Software testing is the way of assessing a software product to distinguish contrasts between given information and expected result. Additionally, to evaluate the characteristic of a product. The testing process evaluates the quality of the software. You know what testing does. No need to explain further. But, are you aware of types of testing. It’s indeed a sea. But before we get to the types, let’s have a look at the standards that needs to be maintained. Standards of Testing The entire test should meet the user prerequisites. Exhaustive testing isn’t conceivable. As we require the ideal quantity of testing in view of the risk evaluation of the application. The entire test to be directed ought to be arranged before executing it. It follows 80/20 rule which expresses that 80% of defects originates from 20% of program parts. Start testing with little parts and extend it to broad components. Software testers know about the different sorts of Software Testing. In this article, we have incorporated majorly all types of software testing which testers, developers, and QA reams more often use in their everyday testing life. Let’s understand them!!! Black box Testing The black box testing is a category of strategy that disregards the interior component of the framework and spotlights on the output created against any input and performance of the system.
    [Show full text]
  • Smoke Testing What Is Smoke Testing?
    Smoke Testing What is Smoke Testing? Smoke testing is the initial testing process exercised to check whether the software under test is ready/stable for further testing. The term ‘Smoke Testing’ is came from the hardware testing, in the hardware testing initial pass is done to check if it did not catch the fire or smoked in the initial switch on.Prior to start Smoke testing few test cases need to created once to use for smoke testing. These test cases are executed prior to start actual testing to checkcritical functionalities of the program is working fine. This set of test cases written such a way that all functionality is verified but not in deep. The objective is not to perform exhaustive testing, the tester need check the navigation’s & adding simple things, tester needs to ask simple questions “Can tester able to access software application?”, “Does user navigates from one window to other?”, “Check that the GUI is responsive” etc. Here are graphical representation of Smoke testing & Sanity testing in software testing: Smoke Sanity Testing Diagram The test cases can be executed manually or automated; this depends upon the project requirements. In this types of testing mainly focus on the important functionality of application, tester do not care about detailed testing of each software component, this can be cover in the further testing of application. The Smoke testing is typically executed by testers after every build is received for checking the build is in testable condition. This type of testing is applicable in the Integration Testing, System Testing and Acceptance Testing levels.
    [Show full text]
  • Parasoft Static Application Security Testing (SAST) for .Net - C/C++ - Java Platform
    Parasoft Static Application Security Testing (SAST) for .Net - C/C++ - Java Platform Parasoft® dotTEST™ /Jtest (for Java) / C/C++test is an integrated Development Testing solution for automating a broad range of testing best practices proven to improve development team productivity and software quality. dotTEST / Java Test / C/C++ Test also seamlessly integrates with Parasoft SOAtest as an option, which enables end-to-end functional and load testing for complex distributed applications and transactions. Capabilities Overview STATIC ANALYSIS ● Broad support for languages and standards: Security | C/C++ | Java | .NET | FDA | Safety-critical ● Static analysis tool industry leader since 1994 ● Simple out-of-the-box integration into your SDLC ● Prevent and expose defects via multiple analysis techniques ● Find and fix issues rapidly, with minimal disruption ● Integrated with Parasoft's suite of development testing capabilities, including unit testing, code coverage analysis, and code review CODE COVERAGE ANALYSIS ● Track coverage during unit test execution and the data merge with coverage captured during functional and manual testing in Parasoft Development Testing Platform to measure true test coverage. ● Integrate with coverage data with static analysis violations, unit testing results, and other testing practices in Parasoft Development Testing Platform for a complete view of the risk associated with your application ● Achieve test traceability to understand the impact of change, focus testing activities based on risk, and meet compliance
    [Show full text]
  • Email: [email protected] Website
    Email: [email protected] Website: http://chrismatech.com Experienced software and systems engineer who has successfully deployed custom & industry-standard embedded, desktop and networked systems for commercial and DoD customers. Delivered systems operate on airborne, terrestrial, maritime, and space based vehicles and platforms. Expert in performing all phases of the software and system development life-cycle including: Creating requirements and design specifications. Model-driven software development, code implementation, and unit test. System integration. Requirements-based system verification with structural coverage at the system and module levels. Formal qualification/certification test. Final product packaging, delivery, and site installation. Post-delivery maintenance and customer support. Requirements management and end-to-end traceability. Configuration management. Review & control of change requests and defect reports. Quality assurance. Peer reviews/Fagan inspections, TIMs, PDRs and CDRs. Management and project planning proficiencies include: Supervising, coordinating, and mentoring engineering staff members. Creating project Software Development Plans (SDPs). Establishing system architectures, baseline designs, and technical direction. Creating & tracking project task and resource scheduling, costs, resource utilization, and metrics (e.g., Earned Value Analysis). Preparing proposals in response to RFPs and SOWs. Project Management • Microsoft Project, Excel, Word, PowerPoint, Visio & Documentation: • Adobe Acrobat Professional
    [Show full text]
  • Survey of Verification and Validation Techniques for Small Satellite Software Development
    Survey of Verification and Validation Techniques for Small Satellite Software Development Stephen A. Jacklin NASA Ames Research Center Presented at the 2015 Space Tech Expo Conference May 19-21, Long Beach, CA Summary The purpose of this paper is to provide an overview of the current trends and practices in small-satellite software verification and validation. This document is not intended to promote a specific software assurance method. Rather, it seeks to present an unbiased survey of software assurance methods used to verify and validate small satellite software and to make mention of the benefits and value of each approach. These methods include simulation and testing, verification and validation with model-based design, formal methods, and fault-tolerant software design with run-time monitoring. Although the literature reveals that simulation and testing has by far the longest legacy, model-based design methods are proving to be useful for software verification and validation. Some work in formal methods, though not widely used for any satellites, may offer new ways to improve small satellite software verification and validation. These methods need to be further advanced to deal with the state explosion problem and to make them more usable by small-satellite software engineers to be regularly applied to software verification. Last, it is explained how run-time monitoring, combined with fault-tolerant software design methods, provides an important means to detect and correct software errors that escape the verification process or those errors that are produced after launch through the effects of ionizing radiation. Introduction While the space industry has developed very good methods for verifying and validating software for large communication satellites over the last 50 years, such methods are also very expensive and require large development budgets.
    [Show full text]
  • An Eclipse Plug-In for Testing and Debugging
    GZoltar: An Eclipse Plug-In for Testing and Debugging José Campos André Riboira Alexandre Perez Rui Abreu Department of Informatics Engineering Faculty of Engineering, University of Porto Portugal {jose.carlos.campos, andre.riboira, alexandre.perez}@fe.up.pt; [email protected] ABSTRACT coverage). Several debugging tools exist which are based on Testing and debugging is the most expensive, error-prone stepping through the execution of the program (e.g., GDB phase in the software development life cycle. Automated and DDD). These traditional, manual fault localization ap- testing and diagnosis of software faults can drastically proaches have a number of important limitations. The place- improve the efficiency of this phase, this way improving ment of print statements as well as the inspection of their the overall quality of the software. In this paper we output are unstructured and ad-hoc, and are typically based present a toolset for automatic testing and fault localiza- on the developer's intuition. In addition, developers tend to use only test cases that reveal the failure, and therefore do tion, dubbed GZoltar, which hosts techniques for (regres- sion) test suite minimization and automatic fault diagno- not use valuable information from (the typically available) sis (namely, spectrum-based fault localization). The toolset passing test cases. provides the infrastructure to automatically instrument the Aimed at drastic cost reduction, much research has been source code of software programs to produce runtime data. performed in developing automatic testing and fault local- Subsequently the data was analyzed to both minimize the ization techniques and tools. As far as testing is concerned, test suite and return a ranked list of diagnosis candidates.
    [Show full text]
  • Website Testing • Black-Box Testing
    18 0672327988 CH14 6/30/05 1:23 PM Page 211 14 IN THIS CHAPTER • Web Page Fundamentals Website Testing • Black-Box Testing • Gray-Box Testing The testing techniques that you’ve learned in previous • White-Box Testing chapters have been fairly generic. They’ve been presented • Configuration and by using small programs such as Windows WordPad, Compatibility Testing Calculator, and Paint to demonstrate testing fundamentals and how to apply them. This final chapter of Part III, • Usability Testing “Applying Your Testing Skills,” is geared toward testing a • Introducing Automation specific type of software—Internet web pages. It’s a fairly timely topic, something that you’re likely familiar with, and a good real-world example to apply the techniques that you’ve learned so far. What you’ll find in this chapter is that website testing encompasses many areas, including configuration testing, compatibility testing, usability testing, documentation testing, security, and, if the site is intended for a worldwide audience, localization testing. Of course, black-box, white- box, static, and dynamic testing are always a given. This chapter isn’t meant to be a complete how-to guide for testing Internet websites, but it will give you a straightfor- ward practical example of testing something real and give you a good head start if your first job happens to be looking for bugs in someone’s website. Highlights of this chapter include • What fundamental parts of a web page need testing • What basic white-box and black-box techniques apply to web page testing • How configuration and compatibility testing apply • Why usability testing is the primary concern of web pages • How to use tools to help test your website 18 0672327988 CH14 6/30/05 1:23 PM Page 212 212 CHAPTER 14 Website Testing Web Page Fundamentals In the simplest terms, Internet web pages are just documents of text, pictures, sounds, video, and hyperlinks—much like the CD-ROM multimedia titles that were popular in the mid 1990s.
    [Show full text]
  • Eclipse Project Briefing Materials
    [________________________] Eclipse project briefing materials. Copyright (c) 2002, 2003 IBM Corporation and others. All rights reserved. This content is made available to you by Eclipse.org under the terms and conditions of the Common Public License Version 1.0 ("CPL"), a copy of which is available at http://www.eclipse.org/legal/cpl-v10.html The most up-to-date briefing materials on the Eclipse project are found on the eclipse.org website at http://eclipse.org/eclipse/ 200303331 1 EclipseEclipse ProjectProject 200303331 3 Eclipse Project Aims ■ Provide open platform for application development tools – Run on a wide range of operating systems – GUI and non-GUI ■ Language-neutral – Permit unrestricted content types – HTML, Java, C, JSP, EJB, XML, GIF, … ■ Facilitate seamless tool integration – At UI and deeper – Add new tools to existing installed products ■ Attract community of tool developers – Including independent software vendors (ISVs) – Capitalize on popularity of Java for writing tools 200303331 4 Eclipse Overview Another Eclipse Platform Tool Java Workbench Help Development Tools JFace (JDT) SWT Team Your Tool Plug-in Workspace Development Debug Environment (PDE) Their Platform Runtime Tool Eclipse Project 200303331 5 Eclipse Origins ■ Eclipse created by OTI and IBM teams responsible for IDE products – IBM VisualAge/Smalltalk (Smalltalk IDE) – IBM VisualAge/Java (Java IDE) – IBM VisualAge/Micro Edition (Java IDE) ■ Initially staffed with 40 full-time developers ■ Geographically dispersed development teams – OTI Ottawa, OTI Minneapolis,
    [Show full text]
  • Configuration Fuzzing Testing Framework for Software Vulnerability Detection
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Columbia University Academic Commons CONFU: Configuration Fuzzing Testing Framework for Software Vulnerability Detection Huning Dai, Christian Murphy, Gail Kaiser Department of Computer Science Columbia University New York, NY 10027 USA ABSTRACT Many software security vulnerabilities only reveal themselves under certain conditions, i.e., particular configurations and inputs together with a certain runtime environment. One approach to detecting these vulnerabilities is fuzz testing. However, typical fuzz testing makes no guarantees regarding the syntactic and semantic validity of the input, or of how much of the input space will be explored. To address these problems, we present a new testing methodology called Configuration Fuzzing. Configuration Fuzzing is a technique whereby the configuration of the running application is mutated at certain execution points, in order to check for vulnerabilities that only arise in certain conditions. As the application runs in the deployment environment, this testing technique continuously fuzzes the configuration and checks "security invariants'' that, if violated, indicate a vulnerability. We discuss the approach and introduce a prototype framework called ConFu (CONfiguration FUzzing testing framework) for implementation. We also present the results of case studies that demonstrate the approach's feasibility and evaluate its performance. Keywords: Vulnerability; Configuration Fuzzing; Fuzz testing; In Vivo testing; Security invariants INTRODUCTION As the Internet has grown in popularity, security testing is undoubtedly becoming a crucial part of the development process for commercial software, especially for server applications. However, it is impossible in terms of time and cost to test all configurations or to simulate all system environments before releasing the software into the field, not to mention the fact that software distributors may later add more configuration options.
    [Show full text]
  • Software Testing: Essential Phase of SDLC and a Comparative Study Of
    International Journal of System and Software Engineering Volume 5 Issue 2, December 2017 ISSN.: 2321-6107 Software Testing: Essential Phase of SDLC and a Comparative Study of Software Testing Techniques Sushma Malik Assistant Professor, Institute of Innovation in Technology and Management, Janak Puri, New Delhi, India. Email: [email protected] Abstract: Software Development Life-Cycle (SDLC) follows In the software development process, the problem (Software) the different activities that are used in the development of a can be dividing in the following activities [3]: software product. SDLC is also called the software process ∑ Understanding the problem and it is the lifeline of any Software Development Model. ∑ Decide a plan for the solution Software Processes decide the survival of a particular software development model in the market as well as in ∑ Coding for the designed solution software organization and Software testing is a process of ∑ Testing the definite program finding software bugs while executing a program so that we get the zero defect software. The main objective of software These activities may be very complex for large systems. So, testing is to evaluating the competence and usability of a each of the activity has to be broken into smaller sub-activities software. Software testing is an important part of the SDLC or steps. These steps are then handled effectively to produce a because through software testing getting the quality of the software project or system. The basic steps involved in software software. Lots of advancements have been done through project development are: various verification techniques, but still we need software to 1) Requirement Analysis and Specification: The goal of be fully tested before handed to the customer.
    [Show full text]
  • Software Testing Training Module
    MAST MARKET ALIGNED SKILLS TRAINING SOFTWARE TESTING TRAINING MODULE In partnership with Supported by: INDIA: 1003-1005,DLF City Court, MG Road, Gurgaon 122002 Tel (91) 124 4551850 Fax (91) 124 4551888 NEW YORK: 216 E.45th Street, 7th Floor, New York, NY 10017 www.aif.org SOFTWARE TESTING TRAINING MODULE About the American India Foundation The American India Foundation is committed to catalyzing social and economic change in India, andbuilding a lasting bridge between the United States and India through high impact interventions ineducation, livelihoods, public health, and leadership development. Working closely with localcommunities, AIF partners with NGOs to develop and test innovative solutions and withgovernments to create and scale sustainable impact. Founded in 2001 at the initiative of PresidentBill Clinton following a suggestion from Indian Prime Minister Vajpayee, AIF has impacted the lives of 4.6million of India’s poor. Learn more at www.AIF.org About the Market Aligned Skills Training (MAST) program Market Aligned Skills Training (MAST) provides unemployed young people with a comprehensive skillstraining that equips them with the knowledge and skills needed to secure employment and succeed on thejob. MAST not only meets the growing demands of the diversifying local industries across the country, itharnesses India's youth population to become powerful engines of the economy. AIF Team: Hanumant Rawat, Aamir Aijaz & Rowena Kay Mascarenhas American India Foundation 10th Floor, DLF City Court, MG Road, Near Sikanderpur Metro Station, Gurgaon 122002 216 E. 45th Street, 7th Floor New York, NY 10017 530 Lytton Avenue, Palo Alto, CA 9430 This document is created for the use of underprivileged youth under American India Foundation’s Market Aligned Skills Training (MAST) Program.
    [Show full text]
  • Getting Started with Testcomplete 7
    * Windows and the Windows logo are trademarks of the Microsoft group of companies. 2 Table of Contents Table of Contents INTRODUCING AUTOMATED TESTING AND TESTCOMPLETE .....................................................3 Automated Testing......................................................................................................................................3 Test Types ...................................................................................................................................................3 TestComplete Projects and Project Items...................................................................................................4 TestComplete User Interface......................................................................................................................5 TestComplete Test Object Model................................................................................................................6 Checkpoints and Stores ..............................................................................................................................8 CREATING YOUR FIRST TEST..................................................................................................................9 1. Creating a Test Project.........................................................................................................................10 2. Defining Applications to Test ...............................................................................................................11 3. Planning
    [Show full text]