Silktest Reviewers Guide

SilkTest Reviewer’s Guide 1

software quality optimizationTM

V E R I F I C A T I O N

c o n f i d e n c eby

SilkTest

R E V I E W E R ’ S G U I D E

®


This document is designed to assist you in your evaluation of SilkTest® from Segue Software. SilkTest is the industry’sleading functional and regression testing solution. The Reviewer’s Guide contains tips on what to look for in an automatedtesting solution and describes how SilkTest can help you begin or advance your automated testing efforts.

If you are new to SilkTest or have minimal experience, you will want to start at the beginning, with Maximize Your TestInvestment on page 3. You may be especially interested in the following sections: What to Look for in an Automated TestingSolution on page 3 and Developing Automation on page 9.

If you have automation experience, you may want to pay particular attention to the following sections: DevelopingAutomation on page 9, Moving Automation to the Next Level: Advanced Techniques on page 11 and MaintainingAutomation: Coping with Change on page 12.

ABOUT THE SILKCENTRAL

SOFTWARE QUALITY OPTIMIZATIONTM (SQOTM) PLATFORM

Segue offers SilkCentral - an integrated platform to define, measure, manage and improve software quality from develop-ment through deployment and into production. The SilkCentral platform provides a single point of control into all qualityactivities and up-to-the-minute visibility into application quality status, thus integrating all quality stakeholders through-out the software application lifecycle. SilkCentral serves as the foundation for Segue’s SQO strategy and incorporates all ofthe existing Silk family of products, as well as other third-party solutions, into one, cohesive environment. Segue’s highlyrespected Silk product line is fully integrated into SilkCentral, each test automation product serving as an engine to drive aspecific quality function within the platform. For example, functional/regression testing and load testing are provided bySegue’s flagship products, SilkTest® and SilkPerformer®, respectively.

R E A D I N G T H I S G U I D E

SilkTest is an easy-to-use test automation solution that enables users to be highly productive

in their software test automation efforts.

T A B L E O F C O N T E N T SThe SilkTest Reviewer’s Guide contains the following:

3 Maximize Your Test Investment

4 Why Choose SilkTest

7 How SilkTest Works

9 Developing Automation

11 Moving Automation to the Next Level

12 Maintaining Automation: Coping with Change

13 Running Tests and Analyzing Results

14 Software Quality Optimization (SQO) throughout

the Application Lifcycle

15 Specific SilkTest Integrations


Manually testing software is a time-consuming and oftentedious process, one that cannot guarantee testing consis-tency across releases and platforms. Additionally, time con-straints hinder the ability to manually test and retest appli-cations before they are released. Inevitably the question re-mains: “Did any critical bugs go undetected?”

Why Automated Testing?A viable alternative or supplement to manual testing is au-tomated testing. Automated tests offer several advantages,primarily productivity and repeatability. Automation pro-vides a reduction in the time taken to perform testing and anincrease in the predictability of test runs. With manual test-ing, human error can lead to falsely identifying defects.

Another advantage of automating tests is that multiple testscan be generated quickly from a single, base test. Automa-tion tools offer programmatic aids such as data-driven test-ing to generate multiple similar tests using different data,whereas using manual testers to create large numbers ofrepetitive tests is impractical.

Automated testing leads to better use of both your QA staffand computer resources. Testers are freed up to put moreeffort where it counts - writing and accumulating new teststo expand test coverage of both new and existing applica-tion functionality. The vast majority of defects are foundwhen developing new tests. While QA personnel are writingnew tests, computers can be used to run unattended auto-mated tests around the clock.

What to Look for in an Automated Testing SolutionThe key to an automated testing tool is how effective it is inhelping you quickly determine application quality. Thismeans that the automated testing tool should ensure that:

Tests can run unattended regardless of how theapplication behaves during test execution

Tests can run unmodified on any supported platformin need of testing

Tests can run as soon as possible after thesoftware is available

Results are analyzed in a timely manner

The consistent benefit in all of these factors is increasingproductivity. True unattended testing does not require hu-man intervention to keep the test suite running, regardless

of whether or not any errors occur during test execution.This means no one needs to spend time overseeing thetest runs.

Tests that are portable across platforms eliminate the needto spend time tweaking the tests to adjust to differences thatthe various configurations might introduce.

Tests that are insulated from application changes, both atthe interface and functional level, require little or no time tomodify in order to run right away. This is an importantpoint, given that the applications you need to test arecontinually evolving; if they were not you would no longerbe testing them. Lastly, accurate, easily accessed andanalyzed test result information is the final piece to timelyquality assessment.

M A X I M I Z E YO U R T E S T I N V E S T M E N T

KEY BENEFITSLeverage existing skill sets to achieve high levels of automationproductivity

Maximize testing opportunities by running tests unattended 24x7

Reduce the risk of application errors by maximizing test coverage

Meet demanding release schedules with shortened test cycles


SilkTest has many benefits and features that will appealto users of any skill level, but let us focus on the features thatare most influential in helping you make timely, applicationquality assessments:

Built-in, customizable Recovery System forunattended testing

Flexible, robust, object-oriented 4Test scriptinglanguage, enabling you to test across multipleplatforms, browsers and technologies with oneset of scripts

Agents for simultaneous distributed testing

Reporting

Direct database access and validation

Workflow elements for test creation andcustomization

Customizable Recovery SystemSilkTest has a built-in, highly customizable RecoverySystem that lets tests run unattended, regardless of thebehavior of the Application Under Test (AUT).

After the completion of each individual test in a series to beexecuted, the Recovery System restores the application toan easily defined initial or base state, including restarting theapplication in the event of an application crash.

Portability Across PlatformsSilkTest uses 4Test, which is an object-oriented, purpose-built scripting language, to define tests. Many constructsexist within 4Test that are automatically exploited by SilkTestto enable out-of-the-box script portability across platforms,browsers and other variables, such as screen resolution.This means little or no time is spent modifying the testsbefore running them in different environments or underdifferent operating conditions.

W H Y C H O O S E S I L K T E S T

For example, different browsers, such as Microsoft InternetExplorer, Netscape Navigator and AOL, have similarlynamed buttons that perform the same function, such as thebutton for refreshing the current page. With SilkTest, inmost cases, you can use the same scripts and window decla-rations to interact with the application, regardless of whichbrowser is being used to run the application.

Browser Icon

MICROSOFT INTERNET EXPLORER

NETSCAPE NAVIGATOR

AOL

The object-oriented aspects of 4Test, as well as otherfeatures such as window tagging (see Application GUI andSilkTest Objects on page 7 for more information), provideopportunities for abstraction of data and functions sothat when the application changes, tests can be run withminimal modification.

For example, the relocation of a link on a Web page wouldrequire no test modification. If the link was changed to abutton, reclassifying the element from a link to a button,which is done in seconds with 4Test, is all that wouldbe required to enable any tests accessing that UI elementto run.


Agents for Distributed TestingSilkTest also offers a cost effective way to distribute testsover multiple computers and run them in parallel, therebyshortening the overall test execution cycle. The key driver ofthis capability is the SilkTest Agent. The Agent is installedon the same machine as the AUT, and drives and monitorsthe application.

In a simple, non-distributed configuration, the SilkTestgraphical user interface (GUI), a SilkTest Agent and the AUTall reside on the same machine. In a networked environ-ment, any number of agents can be installed and run onremote machines (controlled by a single SilkTest GUI) inorder to distribute testing for concurrent test execution andreduce test cycle time. The ability to have multiple SilkTestAgents controlled by a single SilkTest GUI is necessary inorder to correctly test logical transactions that are performedby application components distributed over multiple ma-chines.

ReportingOnce results from a test run are available, SilkTest offersmany out-of-the-box mechanisms for results analysis,including charting, graphing, summary reporting, failureand bitmap analysis and updating of expected test results.With extensions to the Recovery System, you can comple-ment the standard results analysis capabilities with e-mailnotifications, XML reports, linkage to issue trackingsystems and obtaining real time test execution status from abrowser. All of these features combine to facilitate a timelyassessment of the quality of the software release.

Direct Database AccessYou can also use SilkTest to access and manipulatedatabases for a variety of purposes, such as:

Verifying an application’s database results withoutusing the AUT

Setting the server database to a known state

Reading information from the database to use asinput to a test or to control test execution flow

Exercising certain database functions that arepresent in a GUI that runs directly on the servermachine and is not a client application, for example,administrative functions used for setting up thedatabase

For more information about accessing databases,see Intermediate Automation and Verifying Databasecontent on page 10.


Workflow Bar for Test Creation & CustomizationSilkTest offers workflow bars to guide you as you createand customize tests. Use the Basic Workflow bar to createrecorded tests and the Data Driven Workflow bar tocreate data driven versions of these tests. Both workflowbars offer users a chance to become productive quickly,allowing for point-and-click creation of highlyreusable, easy-to-maintain automated tests.

The Basic Workflow and Data Driven Workflow bars areshown below. We will take a look at both of these Workflowbars in subsequent sections.

Data Driven Workflow

Supported TechnologiesSilkTest has your application covered, regardless of whetherit is a browser-based application using all the latest bells andwhistles, a standalone Java application or a traditional cli-ent/server application. The following is a representative listof the technologies SilkTest supports:

Browsers, including Internet Explorer, Netscape andAOL using DHTML, HTML, XML, JavaScript, ActiveXand Applets

Standalone Java applications

.NET

PalmOS® platform

DLLs

Visual Basic

Siebel 7

3270/5250 and AS/400

PowerBuilder

Windows 32 applications

Databases

For a complete list, see the SilkTest release notes or contactSegue’s technical support.

Basic Workflow


ArchitectureApplication GUIs are composed of objects such as win-dows, menus and buttons that a user manipulates using akeyboard and a mouse to initiate application operations.SilkTest interprets these objects and recognizes thembased on the class, properties and methods that uniquelyidentify them.

During testing, SilkTest interacts with the objects to submitoperations to the application automatically (simulatingthe actions of a user) and then verifies the results of eachoperation.

The simulated user, SilkTest, drives the application.

Your Action SilkTest Records

Pick a menu item identifier.Pick ()

Check a checkbox identifier.Check ()

Write text identifier.SetText ()

Close a dialog identifier.Close ()

SilkTest consists of two distinct components that execute inseparate processes:

The SilkTest Host software

The SilkTest Agent software

The Host software is the SilkTest component you use todevelop, edit, compile, run and debug your test scripts andtestplans. The machine that runs this component is oftenreferred to as the host machine.

H O W S I L K T E S T W O R K S

Host Machinewith SilkTest

4Test Code

GUI Commands

ApplicationUnder Test

The SilkTest Agent is the component of SilkTest that inter-acts with the GUI of the AUT.

The Agent translates the commands in 4Test scripts intoGUI-specific commands, driving and monitoring the AUT.The Agent and the AUT are required to be on the same box.

Application GUI and SilkTest ObjectsIn order for SilkTest to interact with the objects of the GUI,it is common, but not required, to have a counterpartobject declared in SilkTest. SilkTest object declarations arecontained in include or frame files; it is these objects againstwhich 4Test script statements, contained in script files, arerecorded or written. This separation of object declarationsand script statements provides for easier porting and main-tenance of your tests.

Each object declaration has a class, a tag and an identifier.The diagram on the next page shows several object declara-tions for the page gmo.segue.com, Segue’s sampleWeb application. The home page has the 4Test built-inclass BrowserChild, while the heading on the page,“GMO Online” has the built-in class HtmlHeading.The tag portion is used to describe the physical or othercharacteristics that uniquely match a 4Test object to its coun-terpart in the GUI.


Default values for the identifier and tag of an object declara-tion are customizable, and even the defaults that SilkTestgenerates may be altered. For example, it is possible todefer until test execution time the determination of the tagvalues, such as by calling a function that retrieves informa-tion stored in a spreadsheet. Many of the most successfulSilkTest customers have exploited the power of theSilkTest tagging mechanism to create object declarationsthat are highly insulated from changes that their GUIcounterparts might have undergone, promoting ease ofautomation maintenance.

Users have a choice as to when the SilkTest object declara-tions are initially constructed. One way is to navigateto application windows/pages and statically capture decla-rations for objects contained on the active window/pageusing SilkTest’s declaration recorder. Subsequent test

recordings that exercise previously declared objects result inscript statements that reference those pre-existing objects.Alternatively, with SilkTest 6.0 and later versions, testrecorders can be directed to generate both the object decla-rations and test statements that reference them duringrecording, eliminating the need to pre-record declarations.

Scripting Without Window DeclarationsFinally, users can choose to use SilkTest’s dynamicinstantiation feature to reference GUI objects in a test. Inthis case, a SilkTest object declaration is not required.Instead, syntax that is composed of the class and tag of anobject is used in order to reference GUI objects within a test.This and other mechanisms are covered later as part of thediscussion on testing dynamic content.

[ +] HtmlImage Logo[ ] tag “Logo”

[ +] HtmlHeading GMOOnLine[ ] tag “GMO OnLine”

[ +] HtmlPushButton AboutTheGMOSite[ ] tag “About The GMO Site”

[ +] HtmlLink PleaseLetUsKnowHowYouLik[ ] tag “Please let us know how

you like our site”

ClassIdentifier

Tag


Depending upon your automated testing goals and the skilllevels within your organization, you may use SilkTest todevelop test automation in a variety of ways. For example,you may have business analysts, quality assurance engi-neers – from novices to experts – or software engineerstaking a role in ensuring software quality. Using SilkTest,you can create and leverage automation among all theseskill sets.

Introductory Automation Using the BasicWorkflowTo get started, you may choose SilkTest’s Basic Workflow,which guides you through the process of creating a test. TheBasic Workflow offers a starting point, enabling you to cre-ate recorded tests to get up and running quickly. Thisworkflow will be used quite frequently if your automationgoals are centered on the record/playback approach toautomated testing.

The Basic Workflow allows users to create a project, createone or more tests and play those tests back. The tests thatare created contain references to 4Test objects created bySilkTest’s test recorder while you interact with the applica-tion. After using the Basic Workflow for test creation, usersmight choose to examine the recorded actions and see how4Test, SilkTest’s scripting language, is used.

You can also feel confident that the tests created will run tocompletion, even if an unexpected application error occursduring test playback. The Basic Workflow automaticallyconfigures SilkTest’s built-in Recovery System, gathering allthe information required to start your application andreturn it to the desired base state before executing each testin the series.

Intermediate Automation Using the Data DrivenWorkflow and AutoCompleteOnce you have created a test using the Basic Workflow, youwill probably want to make it data driven. A test createdusing the Basic Workflow typically contains hard-codedapplication data and functionality. The Data DrivenWorkflow assists you in creating a functionally equivalent,data driven version of a test. The Data Driven Workflowcreates a modified test that replaces hard-coded data refer-ences with references to 4Test record fields. The values forthese record fields are bound to database table elements.Data driven tests are then executed repeatedly overmultiple data sets. Using this workflow to make your testsmore general, in terms of the application and verificationdata they use when they are run, increases test reusability.

D E V E L O P I N G A U T O M A T I O N

Using the Basic Workflow bar, youcreate a project, automaticallyenable and test extension settings,configure the recovery system andrecord and run a testcase.

Click the Enable Extensionsbutton at any time to enableSilkTest to recognize yourapplication.

The Recovery Systemgathers all the informationto start your applicationand return it to the desiredBase State.

Click to recordyour testcase.

Run one ormultipletestcases.

Begin by creating anew SilkTest project.This will organize allthe resourcesassociated with atest set.


Data driven tests:

Are highly reusable; adding new tests only requiresadding new data

Make it easier for you to maintain test automation dueto a smaller number of distinct tests; a single datadriven test that uses multiple data sets replacesseveral individual, similar tests that differ only in thedata they use

Users may also need to modify recorded tests in order tointroduce logic into the test. For example, a single test coulduse logic statements to properly deal with a confirmationdialog that the application might present when saving files.In order to help introduce test logic and other testcode customizations, SilkTest offers AutoComplete.AutoComplete makes it easier to work with 4Test, signifi-cantly reducing the potential for scripting errors anddecreasing the need to type text into 4Test files by automati-cally completing functions, members, application states anddata types.

Intermediate Automation and VerifyingDatabase ContentSilkTest can drive a server application’s GUI by meansof the SilkTest Agent exactly as it drives a client application.In addition, the DB Tester feature of SilkTest provides directaccess (using SQL) from a test script to any database sup-ported by ODBC drivers. The SQL commands are submit-ted by means of several SilkTest database functions that donot require the services of the SilkTest Agent. These data-base functions enable you to read and writedatabase records without using the client application. Thus,client test results can be verified without assuming theability of the client to perform the verification.

The database functions, among other things, allow you toconnect to a database, submit an SQL statement, read datafrom selected record(s) and, subsequently, disconnect fromthe database.


For more advanced development of automated tests, SilkTestgives you the power to develop custom test automationusing features such as the object-oriented 4Test scriptinglanguage, user-defined classes and DBTester. More advancedfeatures of SilkTest enable you to:

Test DLLs

Test dynamic content

Test custom windows

Create custom automation frameworks

Testing DLLsUsing SilkTest, the testing of DLLs can be automated toensure that functions contained within the DLL behave asthey should. You can pass various types of arguments toDLLs, including arguments that can be modified by the DLLfunction. In addition to the standard 4Test data types,SilkTest also supports a number of C data types, enablingthe thorough testing of application DLLs.

Working with Dynamic ContentWhen testing applications in which the content is generateddynamically, such as the results page of a Web search engine,you will want to make use of SilkTest’s uniquedynamic instantiation feature.

Dynamic instantiation is a special syntax composed of theclass and tag of an object. If you record a testcase against aGUI object for which there is no 4Test window declaration(or if you want to write a testcase from scratch against suchan object), SilkTest uses dynamic instantiation to uniquelyidentify that GUI object. This technique is ideal for testingthe more dynamic aspects of an application’s GUI.

Additionally, 4Test methods are available to interrogate theobject contents of a window or Web page. Most of thesemethods return lists of objects that can subsequently beiterated through, allowing users to process each object inthe list as needed. For instance, users can write a genericlink-testing capability simply by recursing through thevarious links on each page of a Web site. Again, in thisscenario, there is no need to have SilkTest object declara-tions for the numerous links; in fact, doing so would beimpractical.

Recognizing Custom WindowsSilkTest identifies objects by their class names and theunderlying software that creates and manipulates the

object. When you record window declarations, if SilkTestfinds that a given object’s definition varies from what isconsidered to be standard, for example the MFC library, itdesignates the object as a custom window and assigns it tothe class CustomWin.

This may occur if a standard control was given a non-standard name. For example, a standard text field controlmight have been named EnterTextRegion instead of thestandard name TextField. In this case, you can simply classmap the control to the standard name. If, on the other hand,the control is a custom control, that is, the software in theapplication that creates and manipulates the object is notfrom a standard library, a new class can be recorded torecognize this control.

Creating Custom Automation FrameworksFor optimal automation, SilkTest offers users a rich libraryof classes and functionality that can be extended in order toprovide an automation framework that promotes easierdevelopment and maintenance of tests. Organizations thatpursue this methodology have the mindset that automationdevelopment is akin to software development. In thisscenario, quality engineers might be tasked to build theautomation framework, creating custom classes and meth-ods that encapsulate business and other reusable functions.Based on this framework, business analysts, who are morefamiliar with the Application Under Test, can focus oncreating new tests that leverage the automation framework.

Additionally, SilkTest can be used to build and runkeyword-driven test architectures, which are completely datadriven and use custom-defined keywords to launch scriptsand input test data. Quality assurance engineers build adriver script, which calls scripts that match on keywords ina spreadsheet. Each keyword is associated with reusablebusiness functions that run when the script encounters thekeyword. Since the spreadsheet contains all the input andverification data, business analysts and testers can interactwith the spreadsheet to define tests, freeing up QAengineers to create additional automation via new businessfunctions, if necessary, and keywords.

With its ability to provide users of any skilllevel with the tools they need, SilkTest greatlyfacilitates the transition from manual testingto basic automation as well as moresophisticated automation infrastructures.

M O V I N G A U T O M A T I O N T O T H E N E X T L E V E L :A D V A N C E D T E C H N I Q U E S


Applications are constantly changing. Much of the successderived from automated testing is gained when little work isrequired in modifying the automation to adapt to changesmade in the AUT. Some of the key components of SilkTestthat showcase its ability to help you cope with applicationchanges are:

Object-oriented scripting language

Customizable object abstraction layer

Separation of test objects from test code

Application states (appstates)

The benefits of object-oriented programming, chiefly thoserelated to maintainability, have long been touted by the soft-ware industry. These same benefits also apply to automa-tion developed with SilkTest. As mentioned earlier, some ofthe most resilient and robust automation built by SilkTestcustomers is focused on a logical object abstraction layerthat greatly improves the portability and minimizes the main-tenance of the underlying automated tests. The frame orinclude files that contain the 4Test object declarations ma-

nipulated by tests define the object abstraction layer. Theobjects themselves are tagged, either using default tagginginformation set by the user or by custom tagging techniques.Many of the changes to an application’s GUI require nomodifications to the object layer, such as simple relocationof a control on the page or dialog that contains it. OtherGUI changes, such as changing a Web page to use a linkinstead of a button, are reconciled in the object layer simplyby modifying the class portion of the appropriate object’stag; in this case, the object would change from a 4TestHtmlPushButton to a 4Test HtmlLink. SilkTest also includesthe concept of application states, which can either be re-corded or scripted and are typically used to capture repeatedapplication interactions. Both application states and actualtests can be based on application states. This extraction ofthe navigational aspects of a test insulates the test fromapplication changes and provides a single place in the auto-mation that needs to stay synchronized with the applica-tion.

M A I N T A I N I N G A U T O M A T I O N : C O P I N G W I T H C H A N G E


Running TestsOnce you have created your tests, there are a number ofways to specify, from within the SilkTest GUI, what tests toexecute. If you are using testplans and have a testplan openwithin SilkTest, you can use the testplan marking feature toselect for execution:

Individual tests

A collection of tests associated with specific attributes

The entire testplan

The failed tests when examining test execution results

Additionally, you can exploit the numerous data driven testfeatures within SilkTest to run a single test iteratively overmultiple data sets. If you are not using testplans, and youhave a script file that contains tests within it, you can chooseto run individual tests, or build a test driver script to controlwhat tests to execute. The driver script can be as basic as onethat contains hard-coded test case names and calls them –similar to calling a 4Test function. Alternatively, the drivercan read data source information to determine what tests toexecute. An advanced feature is the use of the ’@’ referenceoperator of SilkTest, which in this scenario would allowfor test names to be built dynamically and then calledto execute.

Results FileWhen you run a single test or a collection of tests, SilkTestcreates a results file. When a results file is the activewindow in SilkTest, a Results menu appears that allows youto manipulate the results file and locate errors. By default, aresults file displays a standard summary at the top of thefile, including the name of the script or testplan; themachine the tests were run on; the number of tests run; thenumber of errors and warnings, if any; actual errors; andtiming information. You can opt to show or hide this infor-mation as needed. The results file also displays themost current execution of the script or testplan. A historymechanism is also provided to save multiple results sets.

To expedite results analysis, you can easily navigate fromthe results file to identify failure sources, use the Bitmap toolfor analyzing application appearance errors and use theDifference Viewer to evaluate application logic errors andupdate, as needed, expected result values. Numerous capa-bilities exist for managing results file information, such asexporting the data for printing, sending the results toSilkCentral Issue Manager, Segue’s issue tracking system,and generating various reports.

Extending Results AccessSilkTest also provides a pre-built set of functions, option-ally invoked by the Recovery System, that enable storingtest run information in a data source such as MicrosoftSQL Server. To complement this, the Results Viewer featureprovides standard ASP pages containing queries andpre-built reports so that test results stored by these func-tions are easily viewed in Internet Explorer.

Advanced Test Execution ProcessingAs mentioned above, SilkTest includes functions for use bythe Recovery System to store results information from testexecutions in a data source. This is a specific example ofleveraging the hooks provided by the Recovery System.However, users can define any type of functionality theywould like to have as part of test executions. For instance,email notifications containing test status information,including bitmap captures and any defect numbers, can besent to application developers to expedite application erroranalysis. The 4Test library is rich with functions for obtain-ing information about tests being executed, including testname, script/testplan file name, arguments passed to thetest(s) and so forth. When you combine the built-in hooksprovided by the Recovery System and the openness of the4Test scripting language, it is easy to see that SilkTest can bemolded to fit your organization’s goals for processing testexecutions.

R U N N I N G T E S T S A N D A N A L Y Z I N G R E S U L T S


Though functional and regression testing may be an initialpriority for your organization, quality does not begin andend with functional testing. Ultimately, quality needs to ex-tend to other areas such as requirements management, unittesting, performance and load testing, test management and,finally, application performance management (APM) oncethe application is in production.

Segue’s SQO solutions enable companies to deploy high-quality software, reduce the business risk associated withpoor quality applications and maximize return on softwareand technology investments. Leading businesses around theworld, including many of the Fortune 500, rely on Segue’sinnovative Silk family of products to protect their businessservice levels, competitive edge and brand reputation. Andbecause quality is not solely about implementing a testautomation product, Segue supports its SQO solutions with

SOFTWARE QUALITY OPTIMIZATION (SQO) THROUGHOUT THE

APPLICATION LIFECYCLEa full range of consulting, training and support services - alldesigned to ensure the success of each customer's specificquality initiatives.

SilkTest is one of the testing engines that integrate with theSilkCentral Software Quality Optimization Platform. Inaddition to SilkTest, Segue’s SQO offerings include:

SilkCentral Test Manager, for overall management ofquality activities

SilkCentral Issue Manager, for managing softwaredefects and their resolutions

SilkCentral Performance Manager, for applicationperformance management

SilkTest, for functional and regression testing

SilkPerformer, for load and performance testing

SilkPerformer Component Test Edition, for testingremote components under concurrent access


SilkTest seamlessly integrates with other Segue productssuch as:

SilkCentral Test Manager for more advanced, process-oriented test management that includes requirementsverification and validation, test execution schedulingand reporting capabilities

SilkCentral Issue Manager for workflow-oriented issuetracking

SilkPerformer for generation of load testing scripts

SilkCentral Performance Manager for driving criticaltransactions that need to be monitored in a productionenvironment

SilkTest’s SilkPerformer recorder feature allows you to gen-erate SilkPerformer scripts within SilkTest. The SilkTestSilkPerformer recorder is a scaled-down version of

SPECIFIC SILKTEST I N T E G R A T I O N S

SilkPerformer’s Recorder. The benefits provided by this in-tegration are substantial:

You save time and effort, by recording a functionaltest and a load test that captures identical applicationbehavior at the same time.

You can prepare many load tests and then passthem off to the few machines at your sitededicated to heavy load testing.

If your company is anticipating the purchase ofSilkPerformer, you can have load tests readyin advance of procuring the load testing solution.

SilkTest also integrates with Version Manager™ fromSerena™ (formerly known as Merant’s PVCS® VersionControl Manager) for managing test files and source codecontrol.

A D D I T I O N A L I N F O R M A T I O N

For more information about SilkTest, including a product demonstration or product evaluation, please visit the SilkTestproduct page on www.segue.com.

Segue, the Segue logo, SilkTest, 4Test and SilkPerformer are registered trademarks and Software Quality Optimization, SQOand SilkCentral are trademarks of Segue Software, Inc. All other marks are the property of their respective owners.

Copyright © July 2005 Segue Software. All rights reserved.

Documents

Silktest Reviewers Guide