QA check log improvement

Hi,

for a long time Studio QA check log does not provide fundamental data and actually cannot be used as a proof of QA. End customers but also we as LSPs require more details for making sure relevant checks were performed and present issues are only false positives.

Therefore I would like to see at least following improvements:

- list of checks performed in every saved QA log

- report segment source with every hit (if possible highlight the issue)

- report segment target with every hit (if possible highlight the issue)

Thanks

Ladislav

Ladislav Hlavatý

Evzen Polenka over 6 years ago

Add one more option - ability to DISPLAY ONLY ISSUES... or some sort of report filtering, various views, or so...

If project has 1000+ files, it's HORRIBLE to scroll through gazzillions of "No Errors Reported" items (moreover, each item differently indented from left edge :-O), looking for the dozen of errors... :-(
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel
Miriam Santos Freire over 7 years ago

Good suggestion! If you want a good example of a useful QA log, please check APSIC XBench. It is very effective in the type of checks provided and the information reported. We could learn quite a few things from them.
- Cancel
- Vote Up 0 Vote Down
- More
- Cancel

Trados Portfolio Ideas > Trados Studio Ideas

QA check log improvement