I'm currently creating a new project from scratch, which gives me a lot of freedom when it comes to organising the environment.
We use Risked Based Testing and therefore I want to make the testitems leading in Quality Centre. To get something descent out of the RBT Sessions, I need some testitems to be split up into smaller bits. To make a long story short: I have a number of objects, and each object has a number of functions. Each object though, have the same functions. Like:
At first glance, I thought that using a list with subitems was the way to go, but I'm having some problems.
My problem is that if I now want to filter the requirements (Each requirement has this value filled in) And select for instance Object2.Func2 out of the dropdown list that appears, it will return ALL Func2's, including those of object1!
Although in some cases, this might actually be quite nice to do, it's not what I would expect or wanted to see. I only wanted to see the Object2.Func2 related requirements.
My question is: Does QC have a function that filters and keeps the hiearchy of the testitems in mind? I'd like to be able to :
- Select Object2.Func2 and only see the requirements that have exactly that item.
- Select Object2 and see all requirements that have Object2 as testitem, or any subitem of Object2
If QC does not have such a function, how can I create a function that does and how does QC respond to this hierachy when for instance I'd like to generate reports using the OTA API?
Re: Filtering a list when having identical subitems
What you're dealing with here is a many to many relationship Objectx<>Funcx. In this scenario, using a subitem list is not the best option - as you've clearly discovered. Better to have independent lists for Object and Function.
Re: Filtering a list when having identical subitem
Sorry for the late reply, but I just wanted to let you know that I adopted the method Tony has suggested. I was playing with the concept of bkoenig but went the other way because, although not completely failsafe, it is better since the nr of sublevels might vary for each project and I want a method that is as uniform as possible.