• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Test Complete

on

  • 3,313 views

In this slide show you will learn what is test complete, what can you test with it, how to create projects, tested application, create/record tests, test execution order, run tests, identify objects, ...

In this slide show you will learn what is test complete, what can you test with it, how to create projects, tested application, create/record tests, test execution order, run tests, identify objects, checkpoints.

Statistics

Views

Total Views
3,313
Views on SlideShare
3,261
Embed Views
52

Actions

Likes
3
Downloads
0
Comments
0

3 Embeds 52

http://testcomplete.weebly.com 37
http://www.weebly.com 11
https://is-tc.azurewebsites.net 4

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Test Complete Test Complete Presentation Transcript

    • Test CompletePresentation
    • AgendaWhat is, what to test?Test Complete IDECreate projects, tested applicationCreate/record tests, tests executionorder, run testsIdentify objectsCheckpointsWork
    • What is Test Complete? Automated testing tool that lets youcreate, manage and run tests for anyWindows, Web Can test applications that were created inC#, C++, Delphi, Java, or any otherdevelopment language Automate your tests and you can run themanytime, day or night by using acontinuous integration tool or by usingTask Scheduler
    • SmartBear http://smartbear.com/ User guide:http://support.smartbear.com/viewarticle/32760/?st=0 Forum:http://smartbear.com/forums/f81/general-testcomplete-discussions Screencasts and Videos:http://support.smartbear.com/screencasts/testcomplete/
    • Decide What Test Cases to Automate Impossible to automate all testing, in this casewe should automate Repetitive tests that run for multiple builds Tests that tend to cause human error Frequently used functionality that introduces high riskconditions Tests that are impossible to perform manually Tests that run on several different hardware orsoftware platforms and configurations Tests that take a lot of effort and time when manualtesting
    • Divide Your Automated Testing Efforts Identify the level of experience and skills foreach of your team members and divide yourautomated testing efforts accordingly Writing automated test scripts requires expertknowledge of scripting languages Test Complete‘s keyword tests feature (TC7)=simple series of keywords with a specifiedaction. With keyword tests, you can simulatekeystrokes, click buttons, select menu items, callobject methods and properties
    • Keyword Testing
    • Types of software testingUnitLoad (WEB)Keyword-DrivenManual
    • Test Complete IDE (1) Test Complete’s desktop is organized into anumber of panels (View  Select Panels) Project Explorer panel: displays a tree of projectitems, their child elements and test log nodes :Project Suite, Projects, Project Items, Project ItemsElements
    • Test Complete IDE (2) Project Workspace panel: placeholder for differenteditors that let you view and modify the contents ofthe project suite, project, project item or its child itemyou are exploring using the Project Explorer panel
    • Test Complete IDE (3) Object browser panel: lets you explore whatproperties, fields, methods and events yourapplication has. The tree view on the left contains alist of processes that are currently running in theoperating system and their windows. All processesare direct children of System (the Sys object inscripts), and windows are children of the process thatopened them
    • Test Complete IDE (4) Object spy:lets youexplore andcaptureonscreenobjects bymoving themouse to themon screen.
    • Test Complete IDE (5) Debugging panels: Call Stack, Locals, Breakpoints,Watch List
    • Create Projects Project Suite  Right-click  Add new Item File  New  New Project Choose programming language Default content contains Events Unit test Keyword test
    • Tested Application (1) Each project may have a list of testedapplications
    • Tested Application (2) Launch tested application Workspace  Right-click Run Selected Scripts Recording
    • Creating Tests Define the test goal: functionalities to betested, create a simple test aimed at oneobjective only Plan testing steps: decide which actions thetest will perform Check test results: decide how to determinethat the test passed successfully or failed Logging the result: file, images, test completelog Create you test
    • Recording Tests To start the recording, select Script | Recordfrom Test Complete’s main menu or pressRecord on the Test Engine toolbar
    • Editing and Writing Scripts (1) First record a script and then modify it Create new scripts manually without recordinganything Syntax highlighting (for each of the supportedlanguages, the Code Editor uses syntax colorhighlighting - different fonts and colors for different codeelements, making them easier to locate anddistinguish.) Outlining Code templates Code navigation (CTRL+function)
    • Specifying Execution Order for Tests Create the desired test items, specify theirexecution flow and modify properties on the TestItems page of the project editor Double click Project and enter order inWorkspaceTest Items
    • Running the Created Test Run from Application Menu:solution, project, script Run from Tested Items Run from Code Editor Run from Project Explorer
    • Analyzing Test Results Test Log
    • Log Test Log
    • Checkpoints Comparison (or verification) operation that isperformed during testing Perform verifications of different kinds: If you test a new control, you may need to verify thatafter a user performs actions, certain control’sproperties contain the appropriate values. Theoperation that will check the property value is called aproperty checkpoint. If the tested application exports data to a file, you mayneed to compare this file with a baseline copy. Thischeck is called a file checkpoint. Similarly, to verify thatthe application changes the database as expected, youcreate a database checkpoint.
    • Object Checkpoints Verifying several properties of the object with asingle test command Object checkpoints obtain the specified object inyour application (this object must exist at thatmoment), verify that some or all properties of theobject and, optionally, its child objects containthe expected values and report the results. The baseline data used by the object checkpointfor comparison is stored in the Stores | Objectscollection of your project. Objects.CheckpointName.Check
    • Property Checkpoints Verifies that an object property has the expectedvalue in the tested application. For example, itverifies the text in a text box or the state of acheck box. This helps you check whether yourtested application works correctly. In scripts, property checkpoints are performedusing the aqObject.CheckProperty method:aqObject.CheckProperty(Aliases.Orders.MainForm.OrdersView,"wItem(5, 0)", cmpContains, "Mark Twain")
    • Table Checkpoints Quite often applications use controls that displayinformation in a tabular form. During testing, youmay need to verify that these controls contain theappropriate data. Use table checkpoints to verify data in thefollowing controls: Microsoft DataGridViewcontrols, Microsoft DataGrid .NETcontrols, Microsoft PropertyGridcontrols, Developer Express XtraGridcontrols, Developer Express QuantumGridcontrols etc
    • File Checkpoints During testing, you may need to check whether afile stores the appropriate data. This may beneeded if your application exports some data, forexample, the customers list, to a file and youneed to check whether the exporting procedurefunctions properly File.Check
    • Region Checkpoints One of the most common testing tasks is to verifythat an application’s window or control isdisplayed correctly. This can be done bycomparing the actual image of the object with thepreviously captured baseline image stored in yourtest project. Regions.Compare
    • Work (1) Create a new solution with a project. OpenNotepadFont dialog and set Times New RomanBold 36. Reopen dialog and check if the valueswere stored. Create a new solution with a project. Add astested applicationc:UsersPublicDocumentsTestComplete 9SamplesWorking With GridsMicrosoftDataGridDataGridSamplebinReleaseDataGridSample.exe. Create a test that modifies the tablecontent and performs a table checkpoint.
    • Work (2) Create a new solution with a project. AddDataGridSample.exe as a Tested Application. Copy allcontent of the grid in a notepad, save the file and performa file checkpoint. Write in logs all steps that you areperforming. Use aqFile object to work with files Create a function to report the testing results as .mht infoder Reports (relative to current project path) Use Project["ConfigPath"] to take the path for the project Use aqFileSystem to delete folder Reports if exists Use Log.SaveResultsAs function to store the results Run this project from Task Scheduler ActionProgram/script: “…TestComplete.exe" Actionargument“…ProjectSuite1.pjs" /r /e