- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
iTestRT, External ITAR Projects, and Project Dependenci
[ Edited ]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-09-2009
02:11 PM
- last edited on
06-03-2009
11:21 AM
by
BethanyW
In iTest 3.4, we are adding support for a new command-line tool called “itestrt” (which is short for iTest RunTime). If you’re familiar with itestcli, you’ll be interested in itestrt as well. The original itestcli tool was designed for running tests from the command line. You point it to an iTest workspace and it will open that workspace and execute tests in that workspace. But many users have told us that having to carry around the whole workspace is awkward. The new itestrt is similar to itestcli, but is lighter weight. (You can continue to use itestcli as usual – and that is valuable when you want to run things in regression from inside a workspace.) itestrt runs tests but does not require a workspace. It takes advantage of the fact that iTest 3.4 now has the ability to export all of the contents of a project into a single file. We call this an “itar” file (short for “iTest Archive”). If you want to use itestrt to run a test, you just need to make sure that all of the prerequisite files are available somewhere in accessible itar files.
If you want to share some of your iTest files with someone else, you can now export the corresponding projects into itar files and send them to them (or put them on a shared network drive, for example). The recipients using iTest can now use all of your files as if they were inside their own workspace – all while leaving them inside the itar files. For example, if you have someone creating and managing some of your response map libraries, they can deploy itar files onto a network share that everyone uses. If there are updates, everyone gets them as soon as the itar files are updated.
Each itar file appears to iTest like another “project” (i.e., top-level folder in your workspace). Large teams will soon have dozens or hundreds of projects and/or itar files. So the next challenge is managing dependencies among these projects. So, again, good news in iTest 3.4. You can now explicitly declare the other projects (or itar files) that any given project is dependent on. (iTest will even generate these for you automatically if you like.) And once these are declared, iTest will know exactly which projects you need when you want to share a set of tests or a library.
So if you’re starting to scale your iTest deployment, you’ll probably be interested in learning more about itar files and the new itestrt command-line tool.
iTestRT
Click the play button on the video to see this feature in action.
Intro to iTAR
Want to learn more? Click the play button on the video to see this feature in action.
Creating an iTar
Want to learn more? Click the play button on the video to see this feature in action.
Using iTars with iTest
Want to learn more? Click the play button on the video to see this feature in action.
Using iTars with iTestRT
Want to learn more? Click the play button on the video to see this feature in action.
Does this post answer your question? Click the "Accept as solution" button.
Was this post helpful? Click the yellow "Kudos!" button.
