community 
The purpose of this article is to show how to add and when to edit a library in Studio.
This is an admin function, the user have to have admin right.
it is recommended to only add the library that is provided by QualiSystems.
It is very important to remember, if the Library is already existed in Studio then use edit to update the library version. DO NOT CREATE a new one
Adding a new library
1. choose "Admin" tab
2. choose "Libraries" in the below Ribbon
3. once the Libraries pane is opened
4. right click on "Libraries"
5. choose "New"->"Library"
6. a browser window will open
7. browse to the new library and select it.
The new library will be part of the Tool pane when create new test.
To edit the library.
1. go to "Admin" tab at the top of the Studio application
2. choose "Libraries" in the below ribbon
3. select the library to update
4. on the right pane at the "File:" click on "Edit..."
5. a browser window will open to browse to the new library
The version is provided for each of the DLL, validate the library is updated with the correct version on the pane.
An example of screen capture library https://support.qualisystems.com/entries/22793362-Screen-Capture-DLL-Library
What is the difference between adding a library and using the dll through the assets tab?
Regards,
Brian
Hi Brian,
That's a very good question!
There are several differences between using an imported Library compared to a DLL Asset.
While both methods expose the full functionality of the DLL in question to the test author a Library has some infrastructure around it that also allows the following:
1) Version Control - Libraries are version tracked. An Admin user will 'check out' the current version and can replace it with an updated library to perform some testing locally. Only when the Admin user 'checks in' the new library will it become generally available to the remaining users via an automatic push update.
2) Libraries have a more refined UI - When you drag an Asset to the canvas and enter the step's mini-canvas, all of the DLL's functions are listed in a flat list comprising public and private functions. A Library, on the other hand, supports a folder-organized list of functions and will only expose Public functions to the user. Overall, this allows you to find what you're looking for more quickly and, subjectively, provides a better user experience.
3) Following on with ease-of-use, a DLL will most likely have some sort of Init function where you create a connection or establish some initial parameters. With an Asset you will need to call the Init function explicitly by having it as the first step in the mini-canvas followingthe Set Session step. With a Library the init function is included in the Set Session step which allows you to specify all relevant information and perform the initialization.
4) Finally, a Library will appear in TestShell Studio under the Tools section and is immediately available to the users. An asset is usually kept in a very specific folder under the Assets section and does not benefit from the same visual accessibility.
As you can see, from a functional point of view the two are largely equivalent, however, a library does benefit from certain usability and quality of life advantages.
If you have any further questions feel free to contact us via a Support ticket and we will be happy to assist.
Yaron.
Contributors
