Manage tests
Create, manage and run automated tests
Our IDE
An IDE made for testing
CLI & CI
CLI & continuous integration support

Reporting
Integrated reporting and issue tracking

Manage tests
Create, manage and run automated tests
Our IDE
An IDE made for testing
CLI & CI
CLI & continuous integration support

Reporting
Integrated reporting and issue tracking
Verify tests
Verify complex test data

Access all QiTASC manuals & tutorials

Verify hundreds of parameters and metadata within seconds during a test or after data has been collected. With the click of a button,
intaQt Verification
checks device, subscriber and event details, internal infrastructure, legal requirements, financial characteristics and more.
Verify hundreds of parameters and metadata within seconds during a test or after data has been collected. With the click of a button,
intaQt Verification
checks device, subscriber and event details, internal infrastructure, legal requirements, financial characteristics and more.
Platform and Language Support
intaQt Verification
is fully compatible with Windows, Linux and Mac OS. Its `Rules` files are compatible with
intaQt
's Vocable Expression Language and UI Steps Language, meaning that Verification test cases, their steps, and configurations can be integrated into larger intaQt projects.
Verification Rules
intaQt Verification
automates the comparison of call detail records (CDRs) or event detail records (EDRs) and XML files against a configured set of Verification Rules. Rules define the type of check that
intaQt Verification
will perform against the selected records, as well as which properties to compare. Examples of Verification Rules include:
  • Test case structure Rules - Concern the structure of test cases or their tickets
  • Comparison Rules - Compare ticket properties relative to specified criteria
  • Format Rules - Check values, which must have a specific format
Verification Selectors
intaQt Verification
simplifies defining the criteria to be checked via its Selectors. These Selectors tell
intaQt
which records to check against Verification Rules and which to exclude. Because only certain records or Tickets should be chosen, Selectors are a critical part of eliminating unnecessary data from the Verification process, which helps to keep these tests running smoothly and quickly.
Online and Offline Verification
intaQt Verification
is available for both online and offline testing. Online Verification involves live
intaQt
test cases, which execute Verification while the test case is in process.

Offline Verification happens after a test case execution is no longer in process. For example, if CDRs/EDRs are only generated once per day, Online Verification may not be possible. While it is possible to set-up a project to use Online Verification in this case, the process is intricate and requires a lot of know-how. Therefore, we have implemented a Verification UI specifically for such offline use cases.
Verification Rules
intaQt Verification Rules check parameters including:
Test Case Structure Rules
These Verification Rules concern the structure of test cases or their tickets.

  • Test case structure - Checks how many ticket types are present
  • Record IDs - Checks that record IDs match the required content and format
Test Case Structure Rules
These Verification Rules concern the structure of test cases or their tickets.

  • Test case structure - Checks how many ticket types are present
  • Record IDs - Checks that record IDs match the required content and format
Comparison Rules
These Verification Rules compare ticket properties with relative to specified criteria.

  • Equals/Not Equals - Checks that a value either equals or does not equal a defined criteria
  • Before/After - Checks that a value is before or after (or not before or after) defined criteria
  • Possible/Impossible - Checks that a ticket's value is or is not in the list of possible values
  • Difference - Checks that the difference between two ticket properties equals an expected value
  • Is Empty - Checks that the property has an empty value
Comparison Rules
These Verification Rules compare ticket properties with relative to specified criteria.

  • Equals/Not Equals - Checks that a value either equals or does not equal a defined criteria
  • Before/After - Checks that a value is before or after (or not before or after) defined criteria
  • Possible/Impossible - Checks that a ticket's value is or is not in the list of possible values
  • Difference - Checks that the difference between two ticket properties equals an expected value
  • Is Empty - Checks that the property has an empty value
Format Rules
These Verification Rules check values, which must have a specific format.

  • All/Not All - Checks that a property contains all or not all of a repetition of the specified chunk
  • ASCII - Checks that the ticket's property value consists of ASCII characters
  • Begins With/Ends With - Checks that a property begins or ends with a certain value
  • Bit Matcher - Checks single bits of a property value
  • Date Comparison - Checks the date from a ticket against another date
  • Matches/Not Matches - Checks that the ticket property's values match or do not match a Regex pattern
  • Phone Number Match - Checks that phone numbers match an expected format
  • Ranges - Checks that a value's property falls between two specified values
  • Values are Equal - Checks that specified values and types are equal
Format Rules
These Verification Rules check values, which must have a specific format.

  • All/Not All - Checks that a property contains all or not all of a repetition of the specified chunk
  • ASCII - Checks that the ticket's property value consists of ASCII characters
  • Begins With/Ends With - Checks that a property begins or ends with a certain value
  • Bit Matcher - Checks single bits of a property value
  • Date Comparison - Checks the date from a ticket against another date
  • Matches/Not Matches - Checks that the ticket property's values match or do not match a Regex pattern
  • Phone Number Match - Checks that phone numbers match an expected format
  • Ranges - Checks that a value's property falls between two specified values
  • Values are Equal - Checks that specified values and types are equal
Verification Built-ins
Verification Built-ins provide additional flexibility and specificity in defining Rules. These Built-ins contain functions that filter for important criteria.
  • Number Matching - Checks that two phone numbers match in a certain format
  • Time Matching - Checks that a time occurs before or after a specified time
  • Bit Matching - Checks that a bits' position corresponds to the bits of a given value converted to a binary
  • Rounding - Rounds values up or down in multiple ways including to full numbers, half numbers, to ceiling or to floor
  • Date creation - Create dates, with an optional date format specification
Verification Configurations
intaQt Verification
allows you to configure your project both in terms of tickets, and in terms of your preferences and needs for additional information and functionality such as:
  • Ticket formats
  • Finding and saving a project's tickets
  • Specifying which Selectors and Rules should be used
  • Verification report content, format and archiving
  • Defining templates for Rules files