Nuramon
Occasional Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
AQtime Pro 7.4 on Windows Server 2008 R2 (x64)
Hello everyone, We've been using AQtime for creating coverage reports on our build server for a while (Coverage Profiler, by Lines). Last week we moved to a new server running Windows Server 2008 R2 (x64). The version of AQtime is 7.4.800.64. Further details can be found in the image attached (Version.jpg). On the new server we're facing a serious problem: every time the profiled code throws an exception, the running application crashes. Further analysis shows, that the exception is somehow no longer handled by the program (see EventLog.jpg). I also figured out, that the problem only occurs when profiling "by Lines". Working with "by Routines" or "by Classes" seems to be fine, but we need info on line level. The problem seems to be connected with the operating system of the server, because on various other machines (Win 7 32bit/64bit, Win Vista 32bit/64bit and Win Xp 32bit) it works as expected. Any ideas or known bugs? Kind regards Thomas9.9KViews0likes2CommentsIncomplete Results when using Coverage Profiler
I'm profiling a delphi-package with the coverage profiler, full check by lines is activated. My AQtime-project is rather simple: one "package" with source code one "executable", containing unit tests for the package In the "Setup"-register, I'm able to see all the units / sourcefiles the package is containing. Same is true for the executable. After running the executable (profiling), a coverage report is generated in the "Results"-register. Everything looks good so far, but a detailled look at the result shows that half of the sourcefiles within the package are missing / not listed. The code within the package is definitly covered by the executable. Results of the source files contained in the report are correct. What could I possibly do wrong? Version: AQtime 7.30 IDE: Delphi XE Thanks in advance Thomas9.6KViews0likes2CommentsRe: Coverage Profiler: Data loss in "Auto Merge"
Hello everyone, I can support you with some additional information. First of all: I was able to fix the problem. After doing some further investigation, I figured out that the data loss has to do with a function containing "unsafe code". As explained in the help-file, the "unsafe" method has not been profiled by AQtime. But as soon as I changed the "unsafe" method to a "safe" method (i. e. the method could be profiled), the data loss after doing a merge of two files is gone. So it looks like the "unsafe" method somehow affected the coverage results of another method at the end of the file when merging two reports. Maybe this is a bug in AQtime? Or can somebody at least explain to me, why this happened? Thanks a lot and best regards Thomas1.5KViews0likes0CommentsCoverage Profiler: Data loss in "Auto Merge"
Hello everyone, First of all some background information: for a smaller subproject in my company, I've created an AQtime-project including all packages and executables for creating coverage reports. The projectfile contains 6 executables, which are started one after another, each creating a single report ("result"). Thanks to the "auto merge"-function, after running all 6 executables, I have a report in which all reports are merged together ("Merged Results" > "All Merged"). This works really well, but there is one file that is not working properly. When I take a look at the report from the executable which is covering this file, I get the following coverage: Hitcount = 1034, Coverage = 91.62%. But in the "All Merged" report, I get the following values: Hitcount = 1034, Coverage = 82.74%. When I opened the file in the "Editor"-view (coverage on line level), I figured out, that after merging some rows are marked als "uncovered" (red bullet), which were marked as "covered" (green bullet) before. It looks like this coverage-information has been lost during automerge. I have no idea what's the problem here. For all other files (~100 in the whole project) auto merge works fine. Only this file creates troubles. I would be thankful for every hint helping me to solve this problem. I'm using AQtime in Version 6.50.498.64. The project is being programmed in Delphi. Thanks in advance Thomas10KViews0likes2CommentsRe: Coverage Profiling - Delphi 2010 - Problems with Generics
Hello Alex, Thanks for your response. When writing the post above I was using AQtime 6.40 already (to be more precise: I used AQtime 6.40.485.64 on Windows 7 64bit). I'm quite sure my compiler-settings are right (choosen according to the manual), because coverage reports for classes without generics work fine for me. Please let me know if you need further information from me. Best regards Thomas2.1KViews0likes0CommentsCoverage Profiling - Delphi 2010 - Problems with Generics
Hello everyone, We have encountered some problems with coverage profiling for Delphi 2010 in units which use Generics. I was able to reproduce the unexpected (wrong?) results it in the Delphi-Project attached to this posting. The problems are: The constructor of generic classes is not covered correctly in the "Editor"-view (in the example attached: constructor of class TBag). It seems that the green dots for the constructor are moved down some rows (see screenshot "Error_1.gif"). In the "Report"-Table the method is listed as fully covered (100%), which is the right result. So maybe it is just a display error. If I remove the generic-parameter from the class everything works correctly. Methods with generic parameters are not listed as covered code at all (in the example attached: method Exchange() of class TGenericMethod, respectively see screenshot "Error_2.gif"). The code is definitly called by the executable. Are we doing anything wrong? Or are there known issues in AQtime with Delphi & Generics? Thanks for help. Best regards Thomas13KViews0likes6Comments