Share via


Microsoft.Data.Schema.UnitTesting.Conditions Namespace

The Microsoft.Data.Schema.UnitTesting.Conditions namespace provides classes that you can use to create and manage test conditions. By defining a custom test condition, you can verify the behavior of a database object in ways that the built-in conditions do not support.

Classes

  Class Description
Public class ChecksumCondition Defines a test condition that verifies the checksum of the result set in a database unit test.
Public class DataSetTestCondition The base class for test conditions that operate on a DataSet and are configured by the user during test "design time". These conditions are configured by querying the database for the expected results of the test.
Public class EmptyResultSetCondition Represents a condition where the ExecutionResult.DataSet property must be empty.
Public class ExecutionTimeCondition Represents a test condition that specifies the maximum amount of time that the test's Transact-SQL statements can take to execute before the test fails.
Public class ExpectedSchemaCondition Specifies that the result set of a database unit test must match a specific schema.
Public class InconclusiveCondition Represents a default condition where nothing is required or expected of a test result.
Public class NotEmptyResultSetCondition Represents a condition where the ExecutionResult.DataSet property must not be empty.
Public class ResultSetCondition Represents the base class for all test conditions that operate on one ResultSet.
Public class RowCountCondition Defines a test condition that verifies the number of rows in the ResultSet that is returned by a database unit test.
Public class ScalarValueCondition Verifies that a particular value in a specific row and column was expected.
Public class TestCondition The base class for all test conditions that are used by generated code.

See Also

Reference

Other Resources

Define Custom Conditions for Database Unit Tests

How to: Create Test Conditions for the Database Unit Test Designer