On Wed, 2017-03-22 at 09:07 -0400, Kamil Paral wrote:
The problem is that this approach requires to search through most or
all the database before you figure out that you have every unique
result available.
Sorry, I'm really badly glazing over trying to read this mail. But let
me just zero in on the first thing I don't understand, which is this.
Later in the mail, you write this:
"IIUIC, the requirement is:
** We want to be able to retrieve all unique results for a particular
item. ..."
yes, that's the case I've mostly been considering. So where does this
"search through most or all of the database" thing come from? I've been
assuming all along that almost all uses are going to be limiting the
amount of searching that needs to be done quite heavily by specifying
at least an item, or multiple items, or a result group, or a test case
name, or some combination of all of those. I certainly am not expecting
many if any folks/tools to be just searching for "absolutely any
results with scenario X".
So where does this concern about "search[ing] through most or all of
the database" come from? I just don't get that, which I think is making
it harder to understand the rest of the proposal.
Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net