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

Integrated reporting and issue tracking
Verify tests
Verify complex test data

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

Integrated reporting and issue tracking
Verify tests
Verify complex test data

Access all QiTASC manuals & tutorials

Use Cases / Tariff and Charging Verification

Tariff and Charging Verification

Tariff verification and charging conformity tests are critical for ensuring that convergent charging systems (CCS), online charging systems (OCS) and customer accounts are behaving correctly.

img src
Tariff verification and charging conformity tests are critical for ensuring that convergent charging systems (CCS), online charging systems (OCS) and customer accounts are behaving correctly. These tests require accessing large amounts of metadata created by events such as phone calls or SMS transfers that affect charging, and involve verifying:

  • Phone & subscriber details, such as phone type, phone number and service provider
  • Call & event details, such as calling parties, lengths of time and passed/failed steps
  • Internal infrastructure
  • Legal requirements
  • Financial characteristics
  • Tariff configurations

QiTASC Products for Tariff Verification and Charging Conformity

intaQt Verification

intaQt Verification checks subscriber details to assess how their accounts are treated in different environments. Metadata collected from call detail records (CDRs), event data records (EDRs) and logs created from test executions is instantly compared against a matrix of requirements called “Verification Rules” to check that charging conforms to a projects’s requirements. When verification fails, a report provides details about which parameters didn’t match to determine where the source of the problem is.

To date, intaQt Verification has automated more than 800 basic charging use cases according the Verification Rules developed at QiTASC, which highlights its precision as a testing tool. The most complex scenarios contain up to 20 different CDRs with more than 3000 parameters. Within a matter of minutes, intaQt Verification checks the number of CDRs/EDRs, the correlation between values within and across the CDRs as well as every single parameter according to expected content and format.

intaQt Verification Product Page

intaQt Verification

intaQt Verification may be executed online, as an intaQt test case is being executed, or offline, for example, if CDRs are only collected at the end of each day. In both cases, the following functionality is included with intaQt Verification:

  • Selectors - These tell intaQt Verification which records to choose. For example, if only voice call tickets should be used.
  • Verification Rules - Rules define the type of “checks” that will be performed against the selected records. For example, checking the difference between two properties like amounts of data used, the length of a phone call, or the difference in a customer’s account balance.
  • Special functions for calculating properties and values such as dates, times and numbers within a test case.

Rules Example

CHECK_Service {
      verify any of {
          check "sequenceId" equals 1;

          check "accountClosingBalance" all "198";
          check "accountClosingBalance" not all "1984";
          check "accountClosingBalance" not all "19";

          check "bearerType" begins with "Voi";

          check "chargeAmount" between 30000 and 40000;
          check "answerTimestamp" between property "sessionCreationTimestamp" and property "ticketCreationTimestamp";
          check "transactionId" equals "1";
          check "sequenceId" equals 1;

          check "success" equals ${true};

          check "chargedDuration" within 100 from 60050;
          check "chargedDuration" within 5 from 60 scaled by 1000;
          check "callDuration" within 60000 from property "chargedDuration";


intaQt provides features that help create, maintain and check tariffs and charging conformity within intaQt test cases. This includes:

  • The intaQt Rater, which creates, edits and update tariffs according to project needs. Tariffs can be created for voice calls, SMS and data usage based on criteria such as call length, the amount of SMS sent or volume of data used.
    • After creating tariffs, intaQt calculates, converts and checks the tariffs from test scenarios and immediately provide results concerning charging accuracy.
  • intaQt Telephony Steps: Combine intaQt’s Telephony steps with the Rater to fully automate the customer’s experience in a live network and check that tariffs are applied correctly. Whether placing a call, sending an SMS or downloading data, intaQt supports the creation of test cases that reflect real-life behaviors.
  • Switch between virtual phones and real phones as you integrate components into your test environment. In both cases, tariffs are calculated as though a real phone was being used in the network.
  • Access intaQt’s suite of Built-ins, which provide out-of-the-box functionality for database connections, utility functions, protocol testing as well as accessing and manipulating different file types.

intaQt Product Page

intaQt Test Case with Online Verification Steps

When performed online, Verification occurs within a regular intaQt test case, such as a voice call or an SMS. The example below shows an intaQt test case, where lines 14-16 contain three Verification steps that collect CDRs, extract metadata and then run the check against the project’s Rules.


Feature: callCompoundStep
  Scenario: callCompoundStepScenario
    Given a phone as A:
      * of type Android
      * where operator == "3 AT"
      * with profile Vienna

    Given a phone as B:
      * of type Android
      * where IMEI: "351554019631511"

    And A starts a call to B as MYCALL:
      * detect incoming call within 10 seconds
    And copy cdrs matching variables "MMOVariables" from "cdrLocation" as "myCdrs"
    And extract Account_ID from cdr myCdrs matching mom as accountIDValue
    And run verification with cdrs "result" and rules "voice".oneCall

When using Online Verification, all intaQt functionality is available to integrate into your tests.

QiTASC User Interfaces for Verification

intaQt Studio (Online Verification)

QiTASC’s integrated development environment provides features that improve your productivity and the quality of your tests:

  • Auto-completion, go-to declarations and rename refactoring help you write, find and edit your tests with ease.
  • Error inspections, line markers and notifications help you identify problems with your code as you write it.
  • the intaQt Phone Plug-in, which shows a project’s phones in real time and enables interacting with remote phones from within intaQt Studio.
  • Create templates, in-code documentation, and more!

intaQt Studio Product Page

intaQt Verifier (Offline Verification)

The Verifier UI is a graphical user interface (GUI) specifically developed for executing Offline Verification tests. All Rules files, Selectors and configurations for Offline Verification are created in the Verifier UI. Additionally, short test cases that tell the UI to execute Verification steps are created and run within the application.

intaQt Verification Product Page

QiTASC Product Add-ons

intaQt Client

intaQt Client is used to execute entire intaQt test projects from the command line, and can be integrated into continuous integration (CI) environments like Jenkins and TeamCity. Combined with intaQt’s parallel execution functionality, test suites can be run and re-run between very short development cycles.

intaQt Client also provides configurable features that allow users to:

  • Specify how often to retry failed tests.
  • Pass parameters to specify ports, configurations or hosts for different projects.
  • Upload local project changes to the server before execution.
  • Create XML configuration files to create complex test suites with tags.

intaQt Client Product Page

ConQlude Reporting Service

Collect, manage and export intaQt test case project data manage defects, which can be accessed by all members of your project’s team. ConQlude automatically uploads all test reports, logs, media attachments and metadata to a centrally-accessible, secure web interface. conQlude provides approval workflow features and can be integrated into most test management systems and defect tracking systems. Our reporting interface ensures that users can remain confident that all test execution details are 100% correct, up-to-date and conform to formats recognized by external project management systems.

conQlude Product Page