User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20060728 Firefox/184.108.40.206 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/20060728 Firefox/18.104.22.168 Adding a subgroup into Litmus states that it works, but the subgroup is not available for adding to a testgroup. I have left the Build Identifier as the firefox ID, since that's the version of firefox I'm using, in case that matters. Reproducible: Always Steps to Reproduce: 1. Go to manage subgroups 2. Add a subgroup to Project Calendar Testgroup: Sunbird FFT 3. Type in a subgroup name and click add 4. Go to Manage TestGroups, select Project Calendar 5. Check the list of "all subgroups" on the left side. Actual Results: Subgroup is not available. It doesn't show up at all. Expected Results: The subgroup would be available to add to the testgroup. Or, in a perfect world, the add after step 3 would have added it to the selected Test Group. This used to work as recently as August 18th, 2006. I don't know what happened to this. Zach and I discussed this in #calendar, and he tried rebuilding the Litmus cache but the bug persisted. He directed me to file this one. I'm going to make this a "Major" feature, because this is clearly a regression in functionality, and it is hampering some of our test case development work in Calendar. We will use the workaround of adding "ungrouped" testcases to a certain existing subgroup for now.
This should be fixed now. Go into 'Manage Testgroups,' select the testgroup you wish to manage (Sunbird FFT), and then select the '-Branch' option in the "Branch(es)" dropdown. This will allow you see subgroups that belong to the same product (Calendar) but have not yet been assigned to a testgroup, and hence have no associated branch information. Not necessarily intuitive, but it should get the job done. Clint: can I also ask you to remove some of the testing/bogus subgroups that I noticed in the db from when you were probably trying to get this working before? Thanks.
(In reply to comment #1) > This should be fixed now. > > Clint: can I also ask you to remove some of the testing/bogus subgroups that I > noticed in the db from when you were probably trying to get this working > before? Thanks. > Yes, I'll do that.