Generating Unit Tests

If there are many persistent classes, it can be difficult to test them all to prove that:

The mappings are correctly defined
The CRUD (Create, Read, Update, Delete) options work
The find methods work
The navigations work

Usually, developers have to develop unit tests or user-interfaces in order to test these objects. PowerDesigner can automate this time-consuming process by using the NUnit or Visual Studio Test System (VSTS) to generate the unit test classes.

Some conditions must be met to unit test for a class:

Mapping of the class should be defined.
The class can be instantiated. Unit test classes cannot be generated for abstract classes.
The class is not a value type.
The Mutable property is set to true. If Mutable is set to false, the class can not be updated or deleted.
The class has no unfulfilled foreign key constraints. If any foreign key is mandatory, the parent class should be reachable (navigable on the parent class side) for testing.

You can run the tests using NUnit or Visual Studio Test System.

Add Unit Test Support
PowerDesigner provides a UnitTest.NET extended model definition to generate unit test files.
Generating Code for Unit Testing
You generate Code for Unit Testing as follows:
Differences Between NUnit and Visual Studio Team Test (VSTS)
Most code generated for these two UnitTest frameworks is very similar. The main differences are:
Running NUnit Unit Tests
After generating your test code, you can run it in one of three ways:
Running Visual Studio Test System Unit Tests
The Visual Studio Team System Team Test tools offer a number of ways to run tests, both from the Visual Studio integrated development environment (IDE) and from a command prompt.

Parent topic: Generating .NET 2.0 Persistent Objects and Windows Applications