How we can download the items that belong to a collection?
The "Collections" table in the database is a very simple table, by itself it does not give us information about which items (Keywords, Test Cases or Test Suites belong to it).
To see it more simply, this is an example of the Collections table.
As it can be seen, we do not have a clue of how to consult the items that belong to this collection, but thanks to the DBeaver application (which offers us an option to see the ER diagram of a table), it was possible to discover how we can know which items belong to a specific collection.
We can realize that there are three other tables, each one for each item that can belong to a collection (keywords, test cases and test suites).
Looking at the tables, we can see that they are designed in the same way.
And that in each one we have the primary key of the element that belongs to a specific collection.
With this primary key we can consult the tables and obtain the information of the elements that belong to a certain collection by means of an SQL query.
But now we are faced with another problem, in these examples, we have few items, but what if we had tens or hundreds of items?
A solution to this could be to implement a script or task that is responsible for creating the files and putting them all in a compressed folder. This would prevent the user from choosing the download location for each file.
How we can download the items that belong to a collection?
The "Collections" table in the database is a very simple table, by itself it does not give us information about which items (Keywords, Test Cases or Test Suites belong to it).
To see it more simply, this is an example of the Collections table.
As it can be seen, we do not have a clue of how to consult the items that belong to this collection, but thanks to the DBeaver application (which offers us an option to see the ER diagram of a table), it was possible to discover how we can know which items belong to a specific collection.
We can realize that there are three other tables, each one for each item that can belong to a collection (keywords, test cases and test suites).
Looking at the tables, we can see that they are designed in the same way.
And that in each one we have the primary key of the element that belongs to a specific collection. With this primary key we can consult the tables and obtain the information of the elements that belong to a certain collection by means of an SQL query.
But now we are faced with another problem, in these examples, we have few items, but what if we had tens or hundreds of items?
A solution to this could be to implement a script or task that is responsible for creating the files and putting them all in a compressed folder. This would prevent the user from choosing the download location for each file.