Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: QA Audits



Permlink Replies: 4 - Last Post: Feb 19, 2016 2:04 AM Last Post By: G. Smith
G. Smith

Posts: 44
Registered: 5/3/03
QA Audits
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 17, 2016 5:51 AM
I'm trying to use QA Audit in Delphi/XE8.

It seems buggy. Is it worth it?

1. Choosing Project>QA Audit and following the instructions gives me a list of problems. So far so good.

2. Clicking on of the listed problems opens the source file (good), but DOESN'T bring the offending line into view (bad).

3. Ammending code (fixing the problem) and running QA Audit again gives me an empty audit results page. Looks that my 20 previous problems have all gone away. (bad)

4. Restoring the code to it's previous state and running QA Audit again gives me (again) a blank page. To me, that meens it doesn't work.

5. Now, closing down and reloading XE8, and running QA Audit once more produces the oringinal list of problems.

Is this supposed to be the technique?
a. Run QA Audit.
b. Correct the bug/prblem.
c. close down/shut XE8.
d. Open the project again in XE8
e. go to a..
Per Larsen, Nex...

Posts: 28
Registered: 3/19/00
Re: QA Audits
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 17, 2016 12:24 PM   in response to: G. Smith in response to: G. Smith
G. Smith wrote:

I'm trying to use QA Audit in Delphi/XE8.

It seems buggy. Is it worth it?

1. Choosing Project>QA Audit and following the instructions gives me
a list of problems. So far so good.

2. Clicking on of the listed problems opens the source file (good),
but DOESN'T bring the offending line into view (bad).

3. Ammending code (fixing the problem) and running QA Audit again
gives me an empty audit results page. Looks that my 20 previous
problems have all gone away. (bad)

4. Restoring the code to it's previous state and running QA Audit
again gives me (again) a blank page. To me, that meens it doesn't
work.

5. Now, closing down and reloading XE8, and running QA Audit once
more produces the oringinal list of problems.

Is this supposed to be the technique?
a. Run QA Audit.
b. Correct the bug/prblem.
c. close down/shut XE8.
d. Open the project again in XE8
e. go to a..

Never noticed that before. Seems to be inspired by Microsoft's FxCop
utility and friends (integrated in VS in later years). Good idea in
principle, but...

I can confirm most of your observations using XE10 Seattle.

"Refresh" clears the list even with no changes applied.

Also, I've yet to find a single one of the - apparently - hundreds of
errors and warnings for this single source file that I happen to be
working on that's valid.

This feature appears to be pretty useless in its current form.

Per
G. Smith

Posts: 44
Registered: 5/3/03
Re: QA Audits
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 18, 2016 3:22 AM   in response to: Per Larsen, Nex... in response to: Per Larsen, Nex...
//original text snipped//


Never noticed that before. Seems to be inspired by Microsoft's FxCop
utility and friends (integrated in VS in later years). Good idea in
principle, but...

I can confirm most of your observations using XE10 Seattle.

"Refresh" clears the list even with no changes applied.

Also, I've yet to find a single one of the - apparently - hundreds of
errors and warnings for this single source file that I happen to be
working on that's valid.

This feature appears to be pretty useless in its current form.

Per

Thanks for spending the time to look.
It's as I feared - useless.

I'll just pretend Audits don't exist (and tell my boss that the time waisted wasn't waisted, but a valuable learning experience :-).

Graham

PS - Is the UML feature of similar quality?

Per Larsen, Nex...

Posts: 28
Registered: 3/19/00
Re: QA Audits
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 18, 2016 11:45 AM   in response to: G. Smith in response to: G. Smith
G. Smith wrote:

Is the UML feature of similar quality?

No idea.

For me, the U in UML always stood for Unwanted :)

Per
G. Smith

Posts: 44
Registered: 5/3/03
Re: QA Audits
Click to report abuse...   Click to reply to this thread Reply
  Posted: Feb 19, 2016 2:04 AM   in response to: Per Larsen, Nex... in response to: Per Larsen, Nex...
Per Larsen, NexusDB Larsen wrote:
G. Smith wrote:

Is the UML feature of similar quality?

No idea.

For me, the U in UML always stood for Unwanted :)

Per

Yep.

Useless. Unfinished. These also come to mind.

For me I think Unused will do for me.

Graham
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02