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. Groups and tests states and execution statuses
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

Groups and tests states and execution statuses

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

The test is a set of SQL statements and parameters, which are arranged in a particular way to check if the converted objects work in the same way as the source objects.

The group is a set of logically connected tests, which are executed according to the scenario.

Test Scenario — defines a group of tests and says how tests will be executed:

  • sequentially or in parallel,
  • in one session or in several sessions,
  • in a random or in a strict order.

Execution states

After the execution, each test and each group of tests gets the execution statuses, assigned depending on was the executions successful or not.

Use the Save data set in file option in the pop-up menu to save the result of test execution into a .csv file.

The tests return the result of comparison for the three types of outputs (one of them or a combination of two of them):

  • scalar output values (procedure parameters, function return value, etc.)
  • datasets (sys_refcursor, a result of a SELECT statement, etc.)
  • affected objects (objects, which potentially could be affected during the programmability execution)

Group and test can have the following execution statuses:

  • Passed: means that scalar result(s), dataset(s), or affected object(s) return, and these results are equal in the Source and the Target
  • Failed: means that scalar result(s), dataset(s), or affected object(s) return, and these results are NOT equal in the Source and the Target
  • Error: means that there is an error in the test (table or view does not exist, user-defined exception, arithmetic overflow error, etc.)
  • Not executed: means that the test is new, imported, copied, moved, and not started yet

Test status is cumulative. It’s defined based on the results from the three test components:

  • scalar output values,
  • datasets,
  • affected objects.

The test status defines the most severe result of these three components.

Group status is also cumulative. It’s defined based on the test statuses of both test results and test state. Group status is defined as the most severe test result/state.

The test results from the highest to the lowest severity:

  • Error
  • Failed
  • Passed

Figure 1. Passed tests

Figure 2. Failed tests

Figure 3. Error status

 

Figure 4. Not executed tests

Group and test states

The groups and tests can have the following states:

  • Invalid — the high severity state that indicates that the test is corrupted (deleted from the file system but the record in the project file remains, the object is not in the metadata tree, the affected objects are missing or the name of the test object does not match from the * .js file and project file).
  • Ignore — low severity state that means that the test(s) will not run within the GROUP but it can be started by itself – if you select it and press “Run” (“Ignore test” on the “Run Scenario” tab).

Figure 5. Invalid tests

Figure 6. Ignored tests


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
PreviousGroups and tests execution
Next Tests moving logic

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.