npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@testcomplete/testcompletelibrarysetup

v0.1.1

Published

How To guide to add script to your project

Downloads

2

Readme

TestComplete - Library Setup

The purpose of this package is standing only for documentation.

When the library is available on npmjs, you can easily get it with the following command if nodejs is installed on your computer.

I advise to install nodejs, because it will greatly help for getting the dependencies. Without nodejs, you will have to pull sources from the repository by yourself.

You have to open a command line interface to type the following command. If you have Bash (Git BASH) installed on your system, prefers it. Else use the Windows Command Line cmd.exe :

Depending of the architecture of your whole NRT project, I advise you to create in your TestComplete project, a separate & dedicated folder which will receive libraries scripts.

I you envisage to create many TestComplete projects (standalone), maybe you have to consider to create a shared network folder where path will be absolute.

Once the folder is created, open the command line and browse into it. Then type the following command.

npm install @testcomplete/<packageName>

Where <packageName> is the package of scope @testcomplete. If the package has not a scope, remove @testcomplete/ (or replace for another scope).

npm installs the package with it dependencies locally in the folder where you type the command.

NPM Install Library

In TestComplete, you will have to add all files (Library & Dependencies) to your project to be able require them in your scripts.

For package of scope @testcomplete, file are specified in the library documentation.

Example for ExcelHandler :

  • [Dependency] : ./node_modules/@neooblaster/tablejs/Bin/Table.js
  • [Package] : ./node_modules/@testcomplete/excelhandler/ExcelHandler.js

Add existing script in TestComplete

Add existing script in TestComplete

Add existing script in TestComplete

Once files (Library and its dependencies) are added in TestComplete, now you are able to required the library in any scripts.

Note : You can see a little black arrow on each script indicating the script is in reference of and so not owned by the project.

Important : In date of 10/05/2022 (TC 14 & 15), adding scripts in your script folder WILL NOT BE appended to your TestComplete project. So you will have to manually add scripts (for each project).

Requiring ExcelHandler

You do have to require dependencies, because the library does itself. This rule is true for all libraries and their dependencies.