TMXst™ Frequently Asked Questions

Will adding TMXst affect my budget?

Yes! Typical installation adds the power and functionality of keyword-based testing and reduces your current budget. Think about that for a moment—by adding the flexibility and functionality offered by TMXst, your costs for licenses and maintenance will decrease, in addition to saving on training. And these are just the hard dollar costs. There’s additional savings realized by improved efficiency and effectiveness of your QA process as well as meeting tighter deadlines and schedules.

What kind of applications can TMXst test?

Since TMXst relies on the power and functionality of the underlying automation tool or “engine,” the general rule is that anything SilkTest™ can test, TMXst can test. However, the use of TMXst can actually simplify the testing of complicated third party controls, tables, and frames more than just SilkTest™ alone.

What is the ratio of TMXst to SilkTest licenses?

Typical installs show ratios of 5 to 10 TMXst licenses for each SilkTest™ license. There are some groups that actually approach a 20 to 1 ratio depending on the experience of the automation engineer and where the project is in terms of maturity. Typically, the newer the project the lower the ratio.

What reporting is available with TMXst?

TMXst relies on the underlying tools for the reporting. If you’re using SilkTest™ along with SilkCentral™, you have access to state-of-the art reporting tools quickly and efficiently, using their reporting and management functions.

How is TMXst licensed?

The TMXst license is a concurrent instance, meaning the license can be shared among your work group or project. This makes it a very economical approach to testing.

Does TMXst interface with SilkCentral?

We’re currently working with the technical resources at Borland on a comprehensive interface with SilkCentral™. This should be available shortly, as it is a priority development project.

We outsource most of our code development. How will this help me?

You don’t need to wait for the code to be delivered to start building your test cases or maintaining your existing test library. Work directly from the requirements and begin building your test library as soon as the requirements are known. When your outsourced developers deliver the completed code, your test library is already built and ready to go.