Overview
QTP is a UI automation framework designed mainly for Windows and Web-based applications. It works by identifying the objects in the application UI or a web page and performing the desired operations on them (like mouse clicks or keyboard events); it can also be used to capture object properties like name or handler ID etc. One of the most important topics in QTP is Object Identification.QTP uses a scripting language built on top of VBScript to specify the test procedure, and to manipulate the objects and controls of the application under test.
Though QTP is usually used for “UI Based” Test Case Automation, it can easily handle “Non-UI” based Test Cases. (e.g. API (Certification testing), Database Testing, etc.)
Some of the key features of QTP are:
QTP is a UI automation framework designed mainly for Windows and Web-based applications. It works by identifying the objects in the application UI or a web page and performing the desired operations on them (like mouse clicks or keyboard events); it can also be used to capture object properties like name or handler ID etc. One of the most important topics in QTP is Object Identification.QTP uses a scripting language built on top of VBScript to specify the test procedure, and to manipulate the objects and controls of the application under test.
Though QTP is usually used for “UI Based” Test Case Automation, it can easily handle “Non-UI” based Test Cases. (e.g. API (Certification testing), Database Testing, etc.)
Some of the key features of QTP are:
Plug-ins
Plug-ins are used to make recording more acceptable to a specific application, we use web plug-ins to automate test cases with respect to web applications. QTP has default plug-ins for ActiveX controls, web applications and VB objects. Plug-ins for other objects, such as Microsoft .NETobjects, are also available. Multimedia plug-ins and a plug-in for Windows Mobile are also available. In general, each QTP plug-in is available at an additional cost.
And QTP identifies the windows objects, even if we don’t select any plug-ins at the launching of the application .
Plug-ins are used to make recording more acceptable to a specific application, we use web plug-ins to automate test cases with respect to web applications. QTP has default plug-ins for ActiveX controls, web applications and VB objects. Plug-ins for other objects, such as Microsoft .NETobjects, are also available. Multimedia plug-ins and a plug-in for Windows Mobile are also available. In general, each QTP plug-in is available at an additional cost.
And QTP identifies the windows objects, even if we don’t select any plug-ins at the launching of the application .
License Models
Three types of licenses are available from HP:
1. Demo License : a 14-day demo license
2. Seat license : permanent seat license that is specific to the computer on which it is installed.
3. Floating (Concurrent): Floating allows a license to be shared between machines at any given point in time. (1 floating license allows QTP to be accessible from an entire lab’s worth of PCs but can only have 1 instance running at any given point in time).
Three types of licenses are available from HP:
1. Demo License : a 14-day demo license
2. Seat license : permanent seat license that is specific to the computer on which it is installed.
3. Floating (Concurrent): Floating allows a license to be shared between machines at any given point in time. (1 floating license allows QTP to be accessible from an entire lab’s worth of PCs but can only have 1 instance running at any given point in time).
Record and Playback
Initial development of automated tests with QTP is usually done by record-and-playback. A user’s actions are captured via Microsoft’s Component Object Model (COM). These are recorded into Actions, a kind of subroutine, as VBScript commands. All manipulated objects that QTP recognizes are also added to the object repository. Once recorded, the scripts are editable in either Keyword View or Expert View.
After clicking on the playback button all these actions will be played back. During playback, QTP attempts to identify and perform operations on the same objects, again using COM.
Initial development of automated tests with QTP is usually done by record-and-playback. A user’s actions are captured via Microsoft’s Component Object Model (COM). These are recorded into Actions, a kind of subroutine, as VBScript commands. All manipulated objects that QTP recognizes are also added to the object repository. Once recorded, the scripts are editable in either Keyword View or Expert View.
After clicking on the playback button all these actions will be played back. During playback, QTP attempts to identify and perform operations on the same objects, again using COM.
Checkpoints
Checkpoints are a feature used for verifying the application under test. One can add a checkpoint to check if a particular object, text or a bitmap is present in the automation run.
In short, checkpoints are used to verify that during the course of test execution, the actual application behavior or state is consistent with the expected application behavior or state.
Checkpoints are a feature used for verifying the application under test. One can add a checkpoint to check if a particular object, text or a bitmap is present in the automation run.
In short, checkpoints are used to verify that during the course of test execution, the actual application behavior or state is consistent with the expected application behavior or state.
There are 10
types of checkpoints available
in QTP:
1. Standard Checkpoint — Checks the properties of an object.
2. Table Checkpoint — A Standard Checkpoint that checks the properties of a table.
3. Image Checkpoint — A Standard Checkpoint that checks the properties of an image.
4. Bitmap Checkpoint — Compares an area of the application under test pixel-for-pixel with the screen as seen at record-time.
5. Database Checkpoint — Used to automate back-end testing.
6. Text Checkpoint — Checks that a section of text is found between two other sections of text.
7. Text Area Checkpoint
8. Page Checkpoint — Checks the properties of a web page.
9. Accessibility Checkpoint — Checks the accessibility of an application.
10. XML Checkpoint
The VBScript Reporter.ReportEvent function also produces output very similar to that of a checkpoint, allowing the creation of custom checkpoints.
1. Standard Checkpoint — Checks the properties of an object.
2. Table Checkpoint — A Standard Checkpoint that checks the properties of a table.
3. Image Checkpoint — A Standard Checkpoint that checks the properties of an image.
4. Bitmap Checkpoint — Compares an area of the application under test pixel-for-pixel with the screen as seen at record-time.
5. Database Checkpoint — Used to automate back-end testing.
6. Text Checkpoint — Checks that a section of text is found between two other sections of text.
7. Text Area Checkpoint
8. Page Checkpoint — Checks the properties of a web page.
9. Accessibility Checkpoint — Checks the accessibility of an application.
10. XML Checkpoint
The VBScript Reporter.ReportEvent function also produces output very similar to that of a checkpoint, allowing the creation of custom checkpoints.
Recovery
Recovery is the name for exception handling in QTP, with the goal of enabling the tests to continue to run if an unexpected failure occurs. For instance if an application crash occurs and a message dialog appears, QTP can be instructed to attempt to restart the application and continue with the rest of the test cases from there
Recovery is the name for exception handling in QTP, with the goal of enabling the tests to continue to run if an unexpected failure occurs. For instance if an application crash occurs and a message dialog appears, QTP can be instructed to attempt to restart the application and continue with the rest of the test cases from there
Output Value
This feature is used to store the run-time values/data that are displayed in the application into the run-time data table, so that we can use these run-time values in the script for further use.
Say we need the value which is dynamically created or processed by application for later use, we can go for output concept. We can follow the following example to understand. If the application produces an id for the person and we need that id, that can be solved using output concept, where we store value ‘id’ of that person in the data table and we can refer to that value later.
This feature is used to store the run-time values/data that are displayed in the application into the run-time data table, so that we can use these run-time values in the script for further use.
Say we need the value which is dynamically created or processed by application for later use, we can go for output concept. We can follow the following example to understand. If the application produces an id for the person and we need that id, that can be solved using output concept, where we store value ‘id’ of that person in the data table and we can refer to that value later.
Data Table
The data table is a table primarily used to implement data-driven testing. It is implemented as a Microsoft Excel workbook that can be accessed from within QTP. There are two types of Data Tables available in QTP: the Global data sheet and the local data sheets. The Global data sheet is a single sheet which is accessible from every Action in a test. By default, each row of this sheet specifies the values to be used in an iteration of the entire test. The data table can be managed by other third party tools such as Grid Tools Datamaker, which offers features such as Data inheritance; substitution variables and version control.
There is also one local data sheet associated with each Action. As the Global data sheet specifies iterations of an entire test, these sheets are often used to set up iterations of a single Action. The data in these sheets can only be accessed from their associated Action. While it is possible to access a different Action’s local data sheet, it cannot be done from the Object Repository or from inside a checkpoint.
The data table is a table primarily used to implement data-driven testing. It is implemented as a Microsoft Excel workbook that can be accessed from within QTP. There are two types of Data Tables available in QTP: the Global data sheet and the local data sheets. The Global data sheet is a single sheet which is accessible from every Action in a test. By default, each row of this sheet specifies the values to be used in an iteration of the entire test. The data table can be managed by other third party tools such as Grid Tools Datamaker, which offers features such as Data inheritance; substitution variables and version control.
There is also one local data sheet associated with each Action. As the Global data sheet specifies iterations of an entire test, these sheets are often used to set up iterations of a single Action. The data in these sheets can only be accessed from their associated Action. While it is possible to access a different Action’s local data sheet, it cannot be done from the Object Repository or from inside a checkpoint.
Virtual Objects
Complex objects may not be recognized properly by QTP. The Virtual Object concept was implemented to enable users to add some degree of support for these objects. If an object is not recorded out-of-the-box, an experienced user may be able to define that object as a personal virtual object and build a virtual object repository. Assuming that the required information can be extracted from the object, this allows the users to successfully record and playback against that object. In practice, this is not always possible.
Complex objects may not be recognized properly by QTP. The Virtual Object concept was implemented to enable users to add some degree of support for these objects. If an object is not recorded out-of-the-box, an experienced user may be able to define that object as a personal virtual object and build a virtual object repository. Assuming that the required information can be extracted from the object, this allows the users to successfully record and playback against that object. In practice, this is not always possible.
Transactions
This feature can be used to calculate the time required to run a particular test or particular steps in the tests. Transactions are most often used in automated software performance testing, so they are infrequently used in QTP(Quick test Professional)
This feature can be used to calculate the time required to run a particular test or particular steps in the tests. Transactions are most often used in automated software performance testing, so they are infrequently used in QTP(Quick test Professional)
Results
QTP generates the result file for the test cases at the end of test in the form of XML tree. The result file provides detail regarding PASS and FAILS counts, error messages, and potentially supporting information that allows users to determine the underlying cause of a failure.
QTP generates the result file for the test cases at the end of test in the form of XML tree. The result file provides detail regarding PASS and FAILS counts, error messages, and potentially supporting information that allows users to determine the underlying cause of a failure.
User Interface
QuickTest provides two main views of a script: Keyword View and Expert View. They are selected from tabs at the bottom of the QuickTest Professional window.
QuickTest provides two main views of a script: Keyword View and Expert View. They are selected from tabs at the bottom of the QuickTest Professional window.
Keyword View
Keyword View is QTP’s default test procedure interface. It displays the automation steps of a test procedure as a descriptive tree of Actions and functions. The tree contains columns listing the Action or function name, any parameters, and comments. This mode is most useful for the beginners in operating with the tool. This view allows the user to select the objects either from the application or from the Object Repository and the user can select the methods to be performed on those objects. The script is automatically generated. Users can also set check points from keyword view.
Keyword View is QTP’s default test procedure interface. It displays the automation steps of a test procedure as a descriptive tree of Actions and functions. The tree contains columns listing the Action or function name, any parameters, and comments. This mode is most useful for the beginners in operating with the tool. This view allows the user to select the objects either from the application or from the Object Repository and the user can select the methods to be performed on those objects. The script is automatically generated. Users can also set check points from keyword view.
Expert View
In Expert View, QTP allows display and editing of the a test’s source code. All test actions can be edited here except for the root Global action. Expert View acts as an IDE for the test. It includes most standard IDE features, such as breakpoints. This view is most suitable for the advanced users, enabling them to customize the test, such as by writing user-defined functions.
In Expert View, QTP allows display and editing of the a test’s source code. All test actions can be edited here except for the root Global action. Expert View acts as an IDE for the test. It includes most standard IDE features, such as breakpoints. This view is most suitable for the advanced users, enabling them to customize the test, such as by writing user-defined functions.
Languages
Supports VB Script. Supports classes but not supports polymorphism and inheritance
Supports VB Script. Supports classes but not supports polymorphism and inheritance
starting
quicktest:
Loading
QTP Add-in When Starting From QC
You can create a Template test with the addins u need and save it
to QC .And then you can associate that Template Test script with ur script,so
next time QTP will load with the addins u need .
-----------
Creating a New Template Test
You create a template test by first creating a blank test in QuickTest with the required test settings. Then, in the Test Plan module of your Quality Center project, you browse to your QuickTest test and save it as a Template Test.
Note: When you save the test in QuickTest, you should apply a descriptive name that clearly indicates its purpose. For example, if the template test is to used to associate the ActiveX and Web Add-ins with a new test, you could call it ActiveX_Web_Addins_Template.
Tip: In the Quality Center test plan tree (Test Plan module), you may want to create a special folder for your template tests. This will enable other users to quickly locate the relevant template test when they create new QuickTest tests in Quality Center.
To create a template test:
In QuickTest:
Open QuickTest with the required add-ins loaded. For more information on loading QuickTest add-ins, see Loading QuickTest Add-ins.
Define the required settings in the Test Settings dialog box (File > Settings). For more information, see Using the Test Settings Dialog Box.
If you want to include comments or steps in all tests based on this template test, add them.
Click the Save button or choose File > Save to save the test. The Save Test to Quality Center dialog box opens. Save the test to your Quality Center project using a descriptive name that clearly indicates its purpose. For more information, see Saving Tests to a Quality Center Project.
In Quality Center:
Open the project in Quality Center, click the Test Plan button on the sidebar to open the Test Plan module, and browse to the test you saved in step 4.
Right-click the test and choose Mark as Template Test. The test is converted to a template test.
Repeat steps 1 to 6 to create additional template tests, as needed.
--------------------
You can refer QTP help file for more info .
-----------
Creating a New Template Test
You create a template test by first creating a blank test in QuickTest with the required test settings. Then, in the Test Plan module of your Quality Center project, you browse to your QuickTest test and save it as a Template Test.
Note: When you save the test in QuickTest, you should apply a descriptive name that clearly indicates its purpose. For example, if the template test is to used to associate the ActiveX and Web Add-ins with a new test, you could call it ActiveX_Web_Addins_Template.
Tip: In the Quality Center test plan tree (Test Plan module), you may want to create a special folder for your template tests. This will enable other users to quickly locate the relevant template test when they create new QuickTest tests in Quality Center.
To create a template test:
In QuickTest:
Open QuickTest with the required add-ins loaded. For more information on loading QuickTest add-ins, see Loading QuickTest Add-ins.
Define the required settings in the Test Settings dialog box (File > Settings). For more information, see Using the Test Settings Dialog Box.
If you want to include comments or steps in all tests based on this template test, add them.
Click the Save button or choose File > Save to save the test. The Save Test to Quality Center dialog box opens. Save the test to your Quality Center project using a descriptive name that clearly indicates its purpose. For more information, see Saving Tests to a Quality Center Project.
In Quality Center:
Open the project in Quality Center, click the Test Plan button on the sidebar to open the Test Plan module, and browse to the test you saved in step 4.
Right-click the test and choose Mark as Template Test. The test is converted to a template test.
Repeat steps 1 to 6 to create additional template tests, as needed.
--------------------
You can refer QTP help file for more info .
What's QuickTest Professional (QTP Window?
Before you begin creating tests, you should familiarize yourself
with the main QuickTest window.
The QuickTest window contains the following key elements:
. Title bar—Displays the name of the currently open test.
. Menu bar—Displays menus of QuickTest commands.
. File toolbar—Contains buttons to assist you in managing your test.
. Testing toolbar—Contains buttons to assist you in the testing process.
. Debug toolbar—Contains buttons to assist you in debugging tests.
. Test pane—Contains the Keyword View and Expert View tabs.
. Active Screen—Provides a snapshot of your application as it appeared when you performed a certain step during the recording session.
. Data Table—Assists you in parameterizing your test.
. Debug Viewer pane—Assists you in debugging your test. The Debug Viewer pane contains the Watch Expressions, Variables, and Command tabs. (The Debug Viewer pane is not displayed when you open QuickTest for the first time. You can display the Debug Viewer by choosing View < Debug Viewer.)
. Status bar—Displays the status of the QuickTest application.
The QuickTest window contains the following key elements:
. Title bar—Displays the name of the currently open test.
. Menu bar—Displays menus of QuickTest commands.
. File toolbar—Contains buttons to assist you in managing your test.
. Testing toolbar—Contains buttons to assist you in the testing process.
. Debug toolbar—Contains buttons to assist you in debugging tests.
. Test pane—Contains the Keyword View and Expert View tabs.
. Active Screen—Provides a snapshot of your application as it appeared when you performed a certain step during the recording session.
. Data Table—Assists you in parameterizing your test.
. Debug Viewer pane—Assists you in debugging your test. The Debug Viewer pane contains the Watch Expressions, Variables, and Command tabs. (The Debug Viewer pane is not displayed when you open QuickTest for the first time. You can display the Debug Viewer by choosing View < Debug Viewer.)
. Status bar—Displays the status of the QuickTest application.
QTP Commands
QTP Commands are available in 3 ways.
1.Menu options
2.Tool Bar options
3.Short cut keys (for Some important operations only)
File menu: Through file menu user can create, save tests, open existing tests, export tests in zip format.
Command
| |
New > Test
| |
New > Business Component
| |
New > Scripted Component
| |
New > Application Area
| |
New > Function Library
| |
Open > Test
| |
Open > Business/Scripted Component
| |
Open > Application Area
| |
Open > Function Library
| |
Close
| |
Close All Function Libraries
| |
Save
| |
Save As
| |
Save Test with Resources
| |
Save All
| |
Enable Editing
| |
Export Test to Zip File
| |
Import Test from Zip File
| |
Convert to Scripted Component
| |
Print
| |
Print Preview
| |
Settings
| |
Process Guidance Management
| |
Associate Library '<Function Library Name>' with '<Document Name>'
| |
Recent Files
| |
Exit
|
Edit Menu: It provides editing options and renaming, deleting and splitting actions.
Command
| |
Undo
| |
Redo
| |
Cut
| |
Copy
| |
Paste
| |
Delete
| |
Copy Documentation to Clipboard
| |
Action >
| |
Action > Rename Action
| |
Action > Delete Action
| |
Action > Action Properties
| |
Action > Action Call Properties
| |
Step Properties > Comment Properties
| |
Step Properties > Object Properties
| |
Step Properties > Checkpoint Properties
| |
Step Properties > Output Value Properties
| |
Step Properties > Report Properties
| |
Find
| |
Replace
| |
Go To
| |
Bookmarks
| |
Advanced > Comment Block
| |
Advanced > Uncomment Block
| |
Advanced > Indent
| |
Advanced > Outdent
| |
Advanced > Go to Function Definition
| |
Advanced > Complete Word
| |
Advanced > Argument Info
| |
Advanced > Apply "With" to Script
| |
Advanced > Remove "With" Statements
| |
Optional Step
|
View menu: Through this menu we can launch and close, active screen, Data Table, Debug viewer, information, missing resources etc.
Insert Menu: Through this menu user can inserting check points, out put values, synchronizing points.
In this menu step generator available, using this user can generate recordable and non-recordable scripts.
Through insert menu user can insert VB Script conditional and loop statements and transaction points (Start and End).
Through insert menu user can create new actions, call existing actions and copy existing actions.
Automation Menu:
This menu provides Record, Run options and Run setting options
Through this menu we can start normal recording, analog recording and Low level recording.
Through this menu we can stop recoding, running and also we run tests.
Command
| |
Record
| |
Run
| |
Stop
| |
Run Current Action
| |
Run from Step
| |
Maintenance Run Mode
| |
Update Run Mode
| |
Analog Recording
| |
Low Level Recording
| |
Record and Run Settings
| |
Process Guidance List
| |
Results
|
Resources Menu:
This menu provides object repository and recovery scenarios options.
Through this menu we can create /modify/delete objects information and we can associate repositories.
Through this menu we can create, modify and delete recovery scenarios.
Command
| |
Object Repository
| |
Object Repository Manager
| |
Associate Repositories
| |
Map Repository Parameters
| |
Recovery Scenario Manager
| |
Associated Function Libraries
|
Debug Menu:
This menu provides debug commands for step by step execution.
Through this menu we can insert/remove/break points.
Tools Menu:
This menu provides Tools settings option, view options and object identification configuration.
Through this menu we can set tool options as well as test pane view options.
In this menu object spy option available, through this we can get object’s information.(Properties and values)
In this menu Virtual object option available; through this option we can create virtual objects.
Command
| |
Options
| |
View Options
| |
Check Syntax
| |
Object Identification
| |
Object Spy
| |
Web Event Recording Configuration
| |
Data Driver
| |
Change Active Screen
| |
Virtual Objects > New Virtual Object
| |
Virtual Objects > Virtual Object Manager
| |
Customize
|
Window Menu:
This menu provides QTP tool window style settings.
Help Menu:
This menu provides QTP help as well as VB Script help.
Through this menu we can contact technical support people and we can send feedback.
Through this menu we can check for updates and download or install directly.
QTP 11: Complete List of New Features
XPath and CSS based object identification
Identify objects not only using normal object identification but withXPath and CSS identifier properties. A much awaited and a killer feature
Good Looking and Enhanced Results Viewer
The new improved results viewer provides an executive summary page with summary data, pie charts and statistics for both the current and previous runs and a quick link to the previous run results.
Easy Regular Expressions
You can now create reg ex with the help of syntax hints. Regular Expression Evaluator is available to test regular expressions that you have created. Good One.
Now identify objects not only in relation to each other but in relation to neighboring objects.
With this feature, QTP 11 has moved beyond the unreliability of ordinal identifiers. Objects identified with ordinal identifiers are good only as long as they maintain their relative positions with respect to each other in the new build of application. In case if this position changes or gets interchanged, ordinal identifiers may go for a toss.
HP has now introduced Visual Relation Identifier.
HP has now introduced Visual Relation Identifier.
A visual relation identifier is a set of definitions that enable you to identify the object in the application according its neighboring objects in the application. You can select neighboring objects that will maintain the same relative location to your object, even if the user interface design changes. You define visual relations in the Visual Relation Identifier dialog box, which is accessible from the local or shared object repository, and from the Object Properties dialog box.
Load Function Libraries at Run Time
With the help of LoadFunctionLibrary statement. You can now load a function library when a step runs instead of at the beginning of a run session.
Test Your GUI and UI-Less Application Functionality in One Test
Since QTP is integrated with Service Test, you can now test your GUI and non-GUI based apps in a single run.
Record Support
For FireFox is now available.
Much Awaited Log Tracking is available now
QTP 11 is capable of receiving Java or .NET log framework messages from your application which can then be embedded in the run results.
Embed/Run Javascript in web pages
You can use the new EmbedScript/EmbedScriptFromFile andRunScript/RunScriptFromFile functions to embed JavaScripts in all loaded browser pages. You can use these scripts to perform operations on, or retrieve data from, the browser pages in your application.
Manage Test Data
Improved test data management when integrated with Quality Center
Web 2.0 Toolkit Applications Support
QTP 11 now supports Web 2.0 Toolkit Applications out-of-the-box similar to any other add-ins.
Automatically Parameterize Steps
You can instruct QTP 11 to automatically parameterize test steps at the end of record session.
Silverlight Add-in
To test objects in Silverlight 2 and Silverlight 3 applications. [After installation, Silverlight Add-in is displayed in the Add-in Manager as a child add-in under the WPF Add-in]
Extend WPF and Silverlight Support
You can use WPF and Silverlight Add-in Extensibility SDK to develop support for testing third-party and custom WPF and Silverlight controls that are not supported out-of-the-box
working with
add-ins and add-in manager
Using the Add-In Manager
you can specify which add-ins to load at startup.
Using the Add-In Manager you can specify which
add-ins to load at startup. You can also unload certain add-ins while in
session. The available add-ins and their load behavior is listed in the dialog
box. Add-ins that are not loaded at startup are listed without a load behavior.
When an add-in is unloaded, its functionality is
not available. However, all translator add-ins (such as DXF, DWF, and DWG)
automatically load when that format is selected when doing a Save Copy As. By
default, the translators are not loaded at startup.
NoteYou cannot unload or load an Autodesk Inventor Professional
add-in session. Restart the application for your selection to take effect.
·
Reduce the memory footprint for the application and increase the
capacity. An increased capacity enables you to work with larger assemblies. If
you experience capacity issues while using Autodesk Inventor Professional,
unload some of the larger add-ins (such as Tube & Pipe, Cable &
Harness) if they are not used in your design. In most cases, we recommend that
you do not unload Autodesk add-ins.
·
Correct problems with the application. If you experience problems
with Autodesk Inventor, start to unload non-Autodesk add-ins
systematically to see if unloading corrects the problems. It is possible for
some non-Autodesk Inventor add-ins to be invalid for a current release,
and unloading them may correct problems. Refer to the following default add-in
lists to determine which add-ins to remove.
There are two ways to use the Add-In Manager.
From within the application or from the Windows Start menu.
2. On the ribbon, click Tools
tab
Options panel Add-Ins.
Options panel Add-Ins.
3. In the Add-In Manager
dialog box, double-click the name in the list to switch between Loaded and
Unloaded or between Startup/Loaded and Startup/Unloaded.
4. Click OK.
1. From the Windows Start
menu, select Programs Autodesk Autodesk Inventor[version] Tools Add-In Manager.
Autodesk Autodesk Inventor[version] Tools Add-In Manager.
2. In the Add-In Manager dialog
box, double-click the name in the list to switch between Loaded and Unloaded or
between Startup/Loaded and Startup/Unloaded.
3. Click OK.
·
Assembly Bonus Tools
·
Autodesk DWF Markup Manager
·
Autodesk iDrop Translator
·
AutoLimits
·
Content Center
·
Content Center Item Translator
·
Design Accelerator
·
Drag & Drop Interoperability
·
ESKD Support
·
Eco Materials Adviser
·
Frame Generator
·
iLogic
·
Inventor Studio
·
Inventor Vault
·
Translator: Alias
·
Translator: CATIA V4 Import
·
Translator: CATIA V5 Import
·
Translator: CATIA V5 Part Export
·
Translator: CATIA V5 Product Export
·
Translator: DWF
·
Translator: DWFx
·
Translator: DWG
·
Translator: DXF
·
Translator: IGES
·
Translator: JT
·
Translator: Parasolid Binary
·
Translator: Parasolid Text
·
Translator: PDF
·
Translator: Pro/ENGINEER
·
Translator: Pro/ENGINEER Granite
·
Translator: Pro/ENGINEER Neutral
·
Translator: SAT
·
Translator: SolidWorks
·
Translator: STEP
·
Translator: STL
·
Translator: UGS NX
·
Assembly Bonus Tools
·
Autodesk DWF Markup Manager
·
Autodesk iDrop Translator
·
Autodesk IDF Translator
·
AutoLimits
·
Content Center
·
Content Center Item Translator
·
Design Accelerator
·
Drag & Drop Interoperability
·
ESKD Support
·
Eco Materials Adviser
·
Frame Generator
·
iLogic
·
Inventor Studio
·
Inventor Vault
·
Routed Systems: Cable & Harness
·
Routed Systems: Tube & Pipe
·
Simulation: Dynamic Simulation
·
Simulation: Stress Analysis
·
Translator: Alias
·
Translator: CATIA V4 Import
·
Translator: CATIA V5 Import
·
Translator: CATIA V5 Part Export
·
Translator: CATIA V5 Product Export
·
Translator: DWF
·
Translator: DWFx
·
Translator: DWG
·
Translator: DXF
·
Translator: IGES
·
Translator: JT
·
Translator: Parasolid Binary
·
Translator: Parasolid Text
·
Translator: PDF
·
Translator: Pro/ENGINEER
·
Translator: Pro/ENGINEER Granite
·
Translator: Pro/ENGINEER Neutral
·
Translator: SAT
·
Translator: SolidWorks
·
Translator: STEP
·
Translator: STL
·
Translator: UGS NX
Sort the list by name or
load behavior by clicking the column header. Press CTRL + click to select
multiple items on the list.
|
Start menu: Programs
Autodesk Autodesk Inventor [version] Tools Add-In Manager. |
No comments:
Post a Comment