Wikia

Delphi Programming

Nexus Quality Suite

2,918pages on
this wiki
Talk0

The Nexus Quality Suite (NQS) is a set of tools that enables you to finetune your applications to the highest possible performance and quality standards. The current collection of tools include two profilers (one working at Method level and one working at Line level), and a unit test coverage analyzer. More modules will be added as NQS evolves.

The Quality Suite tools officially work with 32 bit windows executables created in all Delphi versions from Delphi 5 and up, and all C++ Builder versions from BCB 5 and up. They may also work on earlier Delphi applications compiled with versions 2 to 4.

The Quality Suite was formerly known as TurboPower Sleuth QA.


MethodTimerEdit

The MethodTimer tool is a performance analyzer. It measures and reports activity in your code with the purpose of identifying performance bottlenecks. Specifically, MethodTimer records routine calls and reports time spent in each routine. It also shows you a list of routines that are called from a particular routine and how much was spent in a routine on behalf of a calling routine. In addition, MethodTimer contains a disassembler that reports the clock counts and pairing issues that affect the efficiency of your code.

The MethodTimer identifies where your program spends the majority of execution time. With a Quality Suite MethodTimer profile in front of you, you can make code transformations in specific areas to improve the performance of your code.

LineTimerEdit

The LineTimer tool is an execution time profiler that lets you enhance your application and even drill down to individual lines in your program. With the LineTimer, you can see actual times spent on any (or all) lines of code in your project. With this tool you can pinpoint exactly which lines cost you the most execution time!

CoverageAnalystEdit

The CoverageAnalyst tool helps you visually identify the portions of your code that are not fully exercised. With Quality Suite CoverageAnalyst you can build better, more effective test cases.

The most important use of a coverage analyzer is to ensure that all parts of a module (application, DLL, COM object, etc.) have been executed during testing. Far too many programs are released with bugs that escape detection during the quality assurance phase simply because the offending code is never executed. Qality Suite CoverageAnalyst helps to ensure that all parts of the program have been executed.

Around Wikia's network

Random Wiki