This testmethod monitors the schema (metadata) of a datasource and makes the testcase fail if there were changes.
The following changes get monitored:
- Creating or Deletion of Tables, Views, and Columns.
- Renaming of Tables, Views and Columns.
- Changes on Columns:
- Ordering of Columns in Tables and Views.
When run, the testmethod reads the database-schema of a datasource and compares it against the schema extracted in the previous run. So the baseline is always the schema of the previous run. That’s why the testmethod only works starting with the second run.
When analyzing the testresults, you can download the schema of the datasource as an attachment of the testresult. There you also find the differences detected.
Open the attachment as following:
- Open the details of the testresult.
- Open the contextmenu of the testresult by clicking on the arrow of the “Details”-button.
- Click on “Download Attachment”.
- The testmethod only works with a OLE DB datasource. You cannot choose another datasource-type.
|Datasource||Select the OLE DB datasource whose schema should be monitored.|
|Includes||Enter a semicolon-separated list of database-object-names that should be included into the monitoring. Use the syntax described below.|
|Excludes||Enter a semicolon-separated list of database-object-names that should be execluted from the monitoring. Use the syntax described below.|
|Success||There are no differences between the current schema and the schema extracted in the previous testcase-execution.|
|Failed||There are at least one difference between the current schema and the schema extracted in the previous testcase-execution.|
Syntax of Includes and Excludes
Every database-object has a unique name that is composed by different elements like following:
|Column of Table||Database.Schema.Table.Column||AW2014.dbo.Products.Name|
|Column of View||Database.Schema.View.Column||AW2014.dbo.vAccounts.Name|
Enter a semicolon-separated list of Includes or Excludes into the parameter-fields of the testmethod and use the object-names as defined above.
You can even use placeholders (wildcards) in these names:
|*.dbo.*||All objects within the database-schema “dbo”.|
|*Product*||All objects that have the string “Product” anywhere within their name.|
|*Account||All objects whose name ends with “Account”.|
|Category*||All objects whose database-name starts with “Category”.|
|*dbo.Category*||All objects whose table- or view-name starts with “Category” and that are within any database-schema that ends with “dbo”.|
|*Product*;*Account*||All objects whose name either contains “Product” or “Account”. Note that there is a semicolon in between.|