Contributions
- 14 years agoPlace QAComplete QuestionsQAComplete Questions1.3KViews0likes0Comments
Rename the defects tab?
Not all items raised as defects actually are defects. we prefer to use the term only for those that are code or documentation defects and use other terms for items that - for instance - end up as new feature requests, etc. As per my other thread, is there any way that the Defects tab could be renamed? Either via our end or as a feature request on a new versino of SoftwarePlanner? regards, Martin14 years agoPlace QAComplete QuestionsQAComplete Questions8.9KViews0likes3CommentsRe: Change Requests - Not Defects
Hi Barbara, We did think of that but the problem is that we have quite rigid policies in place for evolution of requirements and so there are numerous fields that must be populated for a requirement to get to certain states. To enact the idea of using the Requirements sectino to maintain the Change Requests, we would need to create an "extra" set of states that don't have such restrictions, but these would be visible for Requirements. I'll have a think about it and discuss with the team. cheers, Martin14 years agoPlace QAComplete QuestionsQAComplete Questions1.7KViews0likes0CommentsRe: Change Requests - Not Defects
Thanks for the response! It partially answers the question really because what we would really like to see in SoftwarePlanner is the Defects section be renamed to something like "Issues" since in most software development a large proportion of items raised as defects actually aren't. The above suggestions are great but they don't really help with managing whether to make the change to the requirement or not in the first instance. We'd like to see a Change control section implemented or failing that, be able to classify "Issues" as either a "Defect" or a "CR". (It would be a bit onscure to manage a CR as a checkbox inside a defect that appears on all reports as a defect. If there were an Issue type of "CR" then you could resolve and close the initial Issue report (currently a defect) by noting the number of the CR that was raised and then manage the CR in the change control system. cheers, Martin14 years agoPlace QAComplete QuestionsQAComplete Questions1.7KViews0likes0CommentsChange Requests - Not Defects
Hi, We have been using SoftwarePlanner for over a year and are interested in what is considered the best practise for managing Change Requests within SoftwarePlanner. Currently, they enter our system as Defects and get maintained as such but the reality is that up to half of all incoming defects are actually Change Requests and as much as 60% of those CRs are actually requests for amendments to requirements in various stages of implementation. regards, Martin14 years agoPlace QAComplete QuestionsQAComplete Questions9.4KViews0likes6CommentsTestComplete 8 and Visual Studio 2010
What does "Visual Studio 2010 support" actually mean? Does it mean we can use the VS2010 IDE to create tests or is it just referring to being able to talk to the VS2010 Team Foundation Server to schedule and execute tests? (I have to admit I find it very weird that I am getting email updates about the upcoming TestComplete 8 that link back to the AutomatedQA website where I can't seem to find any detail about TestComplete beyon 7.52) regards, Martin16KViews0likes1Comment