Database structure

Store Perfdata

At the end of a test case, if you call the Store Perfdata system keyword, you can store the test case data in a database setting the folder path and the file name of each database (e.g. C:\Python27\Lib\site-packages\ alyvix\robotproxy\ alyvix_testcases\). The test case databases are made of 4 tables: runs, sorting, thresholds, timestamp. The SQL databases can be explored with a regular database browser (e.g. DB Browser for SQLite).

../_images/output_database_01.png

runs table

The runs table contains one row for every script execution. In the first column there is the absolute timestamp (epoch in seconds) of the beginning of the script execution. In the other columns the transaction performances are written (milliseconds). In case that a transaction breaks (Alyvix reaches the timeout threshold for that transaction) there will write a NULL for it and the subsequent ones.

../_images/output_database_02.png

sorting table

The sorting table contains one row for every script execution, but just in case that the transaction order or state is changed from the last entry. In the first column there is the absolute timestamp (epoch in seconds) at the beginning of the script execution. In the other columns the execution order for each transaction is written (serial number from 0). In case that a transaction breaks there will write a -1 for it and the subsequent ones.

../_images/output_database_03.png

thresholds table

The thresholds table contains one row for every script execution, but just in case the transaction state is changed from the last entry. In the first column there is the absolute timestamp (epoch in seconds) of the beginning of the script execution. In the other columns the transaction thresholds (warning, critical and timeout) are written (milliseconds). In case that a transaction breaks there will write a NULL for it and the subsequent ones.

../_images/output_database_04.png

timestamp table

The timestamp table contains one row for every script execution. In the first column there is the absolute timestamp (epoch in seconds) of the beginning of the script execution. In the other columns the absolute timestamps (epoch in milliseconds) of the beginning of each transaction are written (milliseconds). In case a transaction breaks (Alyvix reaches the timeout threshold for that transaction) there will write a ‘NULL’ for it and the subsequent ones.

../_images/output_database_05.png

Store Scrapdata

At the end of a test case, if you call the Store Scrapdata system keyword, you can store the scraped text in a database setting the folder path and the file name of the database. The test case databases are made of tables, one for each scraper. The SQL databases can be explored with a regular database browser (e.g. DB Browser for SQLite).

<scraper_name> table

The <scraper_name> table contains one row for every script execution. In the first column transaction_timestamp there is the absolute timestamp (epoch in seconds) of the beginning of the scraper transaction. In the second column scraped_text there is the raw scraped text from the scraper.

../_images/output_scrapdatabase_01.png