|
| |
AutomatedQA Inc. Announces QTime - A Comprehensive Application Testing,
Profiling and Debugging System
Los Angeles, CA - Automated QA Inc is proud to announce the immediate release of
QTime, its complete testing, debugging, profiling and coverage analysis tool for
Delphi(tm), C++Builder(tm), and Microsoft's(r) Visual C++.
QTime is specifically designed for software developers and their organizations
to help deliver robust, bug-free, and bulletproof code; while simultaneously
reducing the amount of time spent testing and managing the application delivery
process.
"We are excited about the coming release of QTime, the first tool in our TotalQA
Family of Products. We created AutomatedQA Inc. to build and engineer end-to-end
solutions for software developers to assist in the timely delivery of software
applications." Thomas P. Ciccarelli, President Automated QA Inc.
QTime is a Comprehensive Performance and Testing Platform
Because application testing is a tuning process that matures over time, you need
a structured and organized system to effortlessly focus your energies on key
tasks and application areas. Once you create an application, QTime can help
guarantee that your code will perform at lightening speeds with stability and
overall application efficiency.
QTime's wide-array of profilers will help you identify:
* Poorly performing application algorithms (Timing Profiler).
* Global (Sampling Profiler) and Low Level (Hierarchical Profiler) application
performance issues.
* Unnecessary function calls or overly used functions calls (Hit Count
Profiler).
* Untested sections of application code and functionality (Coverage Profiler).
* The trace and flow of your code...What is called, when, and how (Trace
Profiler).
* Class usage and its impact on the long-term viability of your code (Class
Review).
* COM reference leaks (Reference Count Profiler).
* And so much more...
QTime can give you the answers to these common development questions...
* What is the slowest area of my program?
* What is the most used and/or executed procedure?
* Which piece of code never gets executed during a given test sequence?
* What is the slowest procedure in my program?
* What is the execution flow of my program?
* Have code changes improved application performance?
* Which units and or files are used by my program?
* Am I linking to my program units and or files that are not really used?
* Which procedures are linked to my program?
* How many procedures are used by my program?
* How many files and or units are used by my program?
* Where in the memory address space are my procedures loaded?
* What is the longest procedure (in procedure source code lines)?
* What is the biggest procedure (in bytes)?
* What is the biggest unit and or file in compiled bytes?
* Which unit contains the greatest and or lowest number of procedures?
* What is the most used class in my program?
* Do I free all classes allocated in my program?
* What is the binary output produced by the compiler for my source code?
QTime offers you and your team a no-compromise project-testing platform. It is
the world's first debugging system with a totally open plug-in architecture so
that others within the software development community can participate in
enhancing its already robust feature set.
"Among the many strengths of QTime is the fact that it will allow others to
integrate new and unique tools to the Debugging Environment. This is an
extremely powerful feature and helps insure that this toolset will continually
evolve and improve as others begin to master its flexibility."
The merits and strengths of QTime's open and extensible architecture cannot be
overstated. For instance, within a few weeks of this announcement, AutomatedQA
will release 3 new plug-ins to further extend the already powerful QTime
feature-set.
These new plug-ins will include:
* Application Testing Macro Recorder - Automated testing "Macro Recorder" for
multiple test runs of your application.
* Real-Time Resource Monitor - To graph and view, in real-time, resources used
in your application.
* ATL Profiler - To view class usage for MSVC++ developers.
A Structured, "Pin-Point Specific" Approach to Testing - That's the QTime Model!
| |
|
