Generic selectors
Exact matches only
Search in title
Search in content
Search in posts
Search in pages
  1. DB Best Documentation
  2. Migration Platform
  3. Development project
Migration Platform
  • Overview
  • Product features
    • Release notes
    • Source and target platforms
    • Third-party applications
  • Getting started
    • Creating a new project
    • Ora2Pg installation
    • Tree view filtering
    • Compatible ODAC versions
    • Opening an existing project
    • Connecting to servers
      • Connecting to an Azure SQL Database
      • Connecting to an Oracle database
      • Connecting to a PostgreSQL database
      • Connecting to a Microsoft SQL Server database
    • Command timeout
  • Mapping
    • Object mapping
    • Error mapping rules
    • Data types mapping
  • Schema conversion
  • Schema comparison
  • Data comparison
  • Data migration
    • Migration task
      • Creating migration tasks
      • Templates
      • Migration options
      • Task actions
      • Task statuses
      • Errors or non-standard situations
    • Installing migration agent
      • Installing and uninstalling the data migration agent
      • Registering the migration agents
    • Project settings
  • Test organizer
    • Creating tests
    • Auto-generating tests
    • Groups and tests execution
    • Groups and tests states and execution statuses
    • Tests moving logic
    • Importing and exporting tests
    • Advanced comparison options
    • Creating reports
    • Error handling
  • Data store
  • Development project
  • System requirements
  • Hot keys
  • Known issues
  • Support

Development project

  • Share
    • Share via Facebook
    • Share via Twitter
    • Share via Linkedin

Development project is a special environment for in-depth database testing, code improvements, and emulating close-to-production database scenarios in a separate project. The derived database improvements can be later applied to production databases for increasing the performance level.

Currently, Development project supports the following databases as the operating platforms:

  • Oracle
  • PostgreSQL
  • Microsoft SQL Server
  • Azure SQL Database

The major difference with a regular Migration project is the lack of a target database plus the addition of features for comprehensive database testing.

The additional functionality includes:

  • Expected errors.

Manual setup of expected results

Available in the Test organizer module, the Expected Result tab is the last step of the test creation. The feature shows how database objects’ are supposed to perform. It compares these results with the Test suite results to identify how the database will perform in the production environment.

To generate expected results, do the following steps:

  1. Go through the regular test creation process.
  2. At the Expected Result tab, press the Generate button. It will automatically generate tests for the affected data objects.

Figure 1. Expected result creation

  1. Then press Save, and see the test appearing in the Test suite section with the Expected Result tab available for inspection.

Figure 2. A new test in Test suite

Note: if the Generate button hasn’t been pressed before pressing Save, the test will appear with a small yellow mark in the Test suite section. Hovering the mouse over the test will display the “Missing expected result” message.

Figure 3. Missing expected result

  1. Now run the test and see the Results tab showing comparison result for affected objects and the exact number of matching database objects from a dataset.

Figure 4. Test results

  1. To see more details about dataset objects test results, users need to proceed to Advanced compare options > check Override parent options > check Equal rows and press Save.

Figure 5. Equal rows setup

  1. Run the test once again. Now the Result tab contains detailed information about each matching row from a dataset.

Figure 6. Equal rows in the Results tab

Automatic expected results

Users can automatically generate expected errors for groups and categories of database objects in a tree view.

To do that, complete the following steps:

  1. Navigate to a tree view and select a category of database objects, including tables, views, procedures, functions, and materialized views.
  2. Right-click on the selected category and click on Auto generate tests.

Figure 7. Test auto-generation

  1. The selected category will appear in the Test suite section with a yellow mark, indicating that every object in the selected category doesn’t have expected results and displaying the “Missing expected result” message.

Figure 8. Missing expected result for subcategories

  1. Right-click on the selected object category and choose the Generate expected result option.

Figure 9. Generating expected results for a category

  1. Once generated, expected results will be applied to every available database object in a category and users can run the test by using the Run option. After finishing the test, users will see test results in the right section of the screen.

Figure 10. Running a test with expected results

  1. To see rows that match between expected results and the actual test results, users need to expand the Test suite tree view and select an object to inspect. The Results tab will the matching rows after users proceed to Advanced compare options > check Override parent options > check Equal rows, press Save, and run the test once again (as shown in Figure 4).

Figure 11. Inspecting results for a selected object

  1. Both the tests and expected results function based on pre-selected settings. To modify them, users should navigate to the “triple horizontal line” Main Menu > Project Settings > Test Organizer > Auto-generation settings and check the necessary options for Data objects and Programmability objects behavior.

Figure 12. Auto-generation settings


Didn’t find the answer?

You can report problems, ask questions or share ideas for improvements on our email [email protected].

Did this page help you?

Provide Feedback
Next Overview

Did this page help you? Yes

Thanks for letting us know that we did a great job.

Did this page help you? No

Thanks for letting us know that there is a problem on this page.

Send Feedback

Feel free to share your ideas or occurred issues with us. The DB Best team will be happy to make our documentation better.

Please, specify your email address so that we can reach out to you to clarify your question. Also, we will use this email address to notify you about solving the issue.

* marks the mandatory fields

Dark theme Light theme

© 2002–2021 DB Best Technologies, LLC. All rights reserved.