fheerwegh
Regular Visitor
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: Last run status on the test set listing should be appropriate for the release selected.
This feature idea has been logged a few years ago. I also noticed another topic requesting the same improvement: https://community.smartbear.com/t5/QAComplete-Feature-Requests/New-Improved-Testing-Results-Report-based-on-a-Release/idi-p/153933 Also cases have been created (e.g. Case #00235269 and Case #00344837 of which I'm aware) indicating that this is more perceived as an issue by customers than an improvement. Can it please be considered to become part of the QAC feature roadmap? That would be greatly appreciated! many thanks, Filip1.9KViews0likes0CommentsRe: Handling De-scoped requirements in QAComplete
You probably know already, but you can add extra requirement statuses in the Requirements module via Actions/Manage Choice Lists. At least that's how I do it (I'm still running QAC 11.0), not sure if this has changed in later versions of QAC. There's a choice list with the status codes which you can extend with for instance "Descoped". You can then put the requirement's status to "Descoped" if that's what you want. What I typically do is make a comment in the requirement, e.g. "removed as part of V1.1 update" as the rationale of having it changed to Descoped. This could be your trace. You just keep the requirement linked to version 1.0 and you don't link it to version 1.1 regards, Filip1.1KViews0likes0CommentsRe: New/Improved Testing Results Report based on a Release
This post perfectly covers the problem we have. We've also bought the tool for its requirements traceability feature and related reporting. I strongly support the statement made that "QAComplete supports this functionality but from our perspective falls short in acccurately reporting it". Since we are workng in a highly regulated software environment having improved reporting capabilities is a must when you consider audits, FDA submissions etc. Having such a report (amongst others) would take away a huge burden of administrative effort, which we're now forced to do manually with every new release in order to preserve the requirement tracing record belonging to that release. A desperate customer looking forward to a major overhaul of the QAComplete reporting feature.2.7KViews0likes0Comments