I want to extract data for test instances in a large number of test set folders, starting from a point in the test set folder hierarchy.
I know how to filter for test instances based on the id of the test set using the cycle-id. But in my case there is a vast number of test sets, and I really want to extract based on all test sets in test set folders below a certain point in the folder heirarchy.
I believe I can select the folders using .../test-set-folders?query={hierarchical-path[AAANAAB*]}. That gives me a list of test set folders, and then I can get a list of the test sets in those with .../test-sets?query={parent-id[<list of ids>]}. Then to get all the test instances I need ... /test-instances?query={cycle-id[<very long list of test set ids>]}.
But that would require a long list of test set ids, and three different API requests. I think I would hit a uri length limit; I haven't tested for that, but I'm not confident going over around 2080 characters.
So I'd like to use a cross-filter. The API documentation says that is possible, citing an example tests?query={status[Ready]; bug.owner[SallyQA]}. But nowhere can I find the rules and table names to use to construct the cross filter. I have looked at the database model documents and tried using the table names like cycl-fold, but these don't work.
My request is to understand:
- the syntax of the cross filter as used in the REST API
- the table names to use for test set folders and test sets in the REST API
- can chain the cross filter to get test instances in test sets in a hierarchy of test set folders.
- the length limit on the url for the GET request
- can I use the POST method for a longer list of test set id's?
Many thanks if you can help.