The following sections describe the database tables that each test run stores the result in. Whether the test used SQLite or SQL Server for test result storage, the tables are pretty similar. The only difference is SQL Server shares a database between many test results, while SQLite only has one test result per database file (.sqlite file).
ResultCatalog table in SQL Server
Since the SQL Server database can store data for multiple test results, the SQL server has a test result catalog table called ResultCatalog.
| Field | Type | Description |
|---|---|---|
| TestId (PK) | uniqueidentifier | The test run GUID. Every subsequent database table has a TestId field that tells which test run the record belongs to. SQLite TestId: If a test used SQLite for test result storage, then the TestId value will be 00000000-0000-0000-0000-000000000000 |
| Name | varchar(128) | A unique name for a test. |
| DisplayName | varchar(128) | The display name of a test. By default, it is the same as Name |
| RunDate | datetime | The data and time of when the test started |
| Consolidated | bit | Always 1 |
| ConfigId | uniqueidentifier | The GUID of the test script configuration file. 2 tests that originated from the same .ssconfig file will have the same id. |
Overview
Content Tools
