EXPERTISE

Model-Based Testing (MBT) & Automated Test Methodology

Model-Based Testing (MBT) is an innovative approach that optimizes software and system testing by automating test case generation.

With MBT, we model the expected behavior of the System Under Test (SUT) to:
✔ Accelerate validation while reducing manual errors.
✔ Ensure complete test coverage and full traceability.
✔ Synchronize test scripts across different tools and versions.
✔ Simplify long-term maintenance, making testing more scalable.

MBT streamlines test cycles and ensures precise regulatory compliance.

Why Choose Model-Based Testing Over Traditional Methods?

Challenges of Traditional Testing
  • Manual test creation – Prone to human errors and inconsistencies.
  • Coverage gaps – Subjective interpretation of requirements.
  • Complex maintenance – Increasing costs and delays in certification.
  • Automated test generation – Eliminates manual errors and ensures full coverage.
  • Synchronized test scripts – Consistent execution across all test tools.
  • Instant updates – Automatically adapts to specification changes.
  • Lower maintenance costs – Reduced effort and long-term scalability

With MBT, businesses achieve higher accuracy, efficiency, and long-term test reliability.

Diagram comparing traditional testing and model-based testing framework, illustrating Mellonne's advanced approach to secure and efficient test automation

Ensure Consistent Testing Results

Many organization use multiple test tools for the same specifications, leading to discrepancies. MBT solves this by:

  • Standardizing test execution – Every tool follow the same API and methodology.
  • Eliminating interpretation errors – Results are dictated by the model, not the test tool vendor.
  • Ensuring repeatable and reliable results – No variations across different tools or test environments.

Achieve uniform, vendor-independant test execution with model-based testing.

Diagram illustrating consistent testing results through Mellonne's model-based testing methodology

Automated Return to Initial State

Model-based testing ensures that the System Under Test (SUT) always starts from a defined, correct state, preventing test pollution and inconsistencies.

  • Automatic reset to initial state after each test execution.
  • No manual intervention needed, ensuring clean, error-free test runs.
  • Test sequences remain valid no matter the execution order.

Run tests in any order with full confidence that the system resets correctly.

Diagram showcasing automated return to the initial state after testing, highlighting Mellonne's secure test automation

What You See Is What You Test

Traditional testing relies on vendor-specific test scripts, leading to inconsistencies. With MBT:

  • Test scripts are auto-generated – Fully aligned with specifications.
  • Execution remains consistent – Standardized results across tools.
  • Automatic updates – Any specification change is instantly reflected.

Gain full control and transparency over your testing process.

Icon illustrating test plan and code equivalence in model-based testing, symbolizing Mellonne's accuracy in testing

Maximize Coverage & Accuracy

Mellonne’s model-based testing framework provides continuous control over test coverage through automation and real-time validation.

  • End-to-end test automation – Enhances efficiency and test repeatability.
  • Automated compliance validation – Ensures ongoing regulatory alignment.
  • Structured test scenarios – Enables systematic, transparent validation.
  • Detailed reporting – ull traceability between test cases and specifications.

Achieve precise, and consistency with model-based testing

Checked box representing Mellonne's commitment to improving coverage accuracy in model-based testing

Automated Test Synchronization & Version Control

With model-based testing, all updates are automatically synchronized, ensuring:

  • Centralized version control – All test scripts align with the latest updates.
  • Consistent execution across tools – Eliminates discrepancies.
  • Full ownership of test plans – Readable test scripts remain under your control.
  • Instant updates – Automatically adjusts to regulatory changes.

Eliminate inconsistencies and streamline compliance validation.

Person analyzing multiple data screens, representing Mellonne's automated testing solutions and effective test control.

Enhance test execution & Efficiency

With traditional test plans
  • Manual updates delay certification.
  • Test coverage drifts over time
  • Higher maintenance costs slow down adaptation
  • Seamless updates – No need for manual reconfiguration.
  • Faster test execution – Reduce certification delays.
  • Lower maintenance costs – Automated processes minimize overhead.

Simplify test management and accelerate compliance validation.

Diagram representing speed and flexibility in Mellonne's model-based testing approach

How We Work with You

1. Define the test strategy

We start by understanding your testing expectations to ensure that the test plan will be executable and deliver meaningful results. We help you define a test strategy that automates execution. We also develop the appropriate test tool to synchronize seamlessly with the model-based testing approach. If you use third-party test tools, we can also synchronize with them. In this step, we agree on a test architecture, specify the interface, specify data in and data out and how to stimulate the SUT, and receive feedback.​

2. Define the test coverage

Next, we begin creating the test plan. We take your specifications as the input document and extract the requirements. These requirements populate a spreadsheet, providing requirement name, documentation references, sub-cases to cover and additional data. The output document becomes the cornerstone of the test plan and the reference against which the test coverage is computed. We work with you to check and confirm that the coverage matches your expectations. Spreadsheets can be updated or amended any time to change the test coverage required.

3. Develop the model

Once coverage is defined, Mellonne develops a model of the SUT. This ‘model’ is a formal high-level implementation of the specifications. It describes all commands, answers, and behaviors. We add traceability tags within the model to match against the coverage spreadsheet.

4. Write tests

Tests can be either written by humans or automatically generated. Either way, traceability tags ensure that the coverage is met. The model enforces specifications and ensures that all testing is relevant. It also dynamically computes each command's return. Unlike test plans written in Word where expectations are mentally calculated, the model contains a perfect representation of all internal data and mechanisms. This ensures that every bit of SUT output can be checked systematically at each step of each test.

5. Produce the test plan

The last step of test planning is producing the deliverables. Our publishing software takes the model + tests as inputs and delivers development specification + tests for execution. All of these assets are generated from the same source, so everything is consistent.

6. Implement test tools

With the deliverables in hand, test tool(s) can start being developed. Since the development spec is provided, test tool vendors implement the same methods. Because the test tool vendors also receive the test sequences, you can expect the same behaviors from different test tools.

7. Validate test tools

We often begin work during test plan production to define the specification. This allows us to know how to develop the most appropriate test tool—or third-party test tool developers—to save time and ultimately accelerate successful testing.

Frequently Asked Questions About Model-Based Testing

Model-based testing (MBT) is a software testing methodology where test cases are automatically generated from a formal model describing the expected behavior of the System Under Test (SUT).

Instead of manually writing individual test scripts, engineers create a model representing system logic, states, and specifications. Test scenarios are then automatically generated from this model.

 

This approach ensures consistent test execution, traceability between requirements and tests, and significantly improved test coverage.

Model-based testing improves test coverage by generating test scenarios directly from system specifications and behavioral models.

Because the model represents all expected behaviors and transitions, MBT systematically generates tests that cover:

  • functional requirements

  • edge cases

  • unexpected state transitions

  • specification constraints

 

This reduces the risk of missing scenarios that are often overlooked with manually written test scripts.

Compared to traditional manual testing approaches, model-based testing provides several key advantages:

  • automated test generation from system models

  • significantly improved test coverage

  • reduced risk of human errors in test design

  • easier maintenance when specifications evolve

  • faster adaptation to new requirements

 

These benefits make MBT particularly valuable for complex systems requiring strict validation and compliance.

Model-based testing is especially effective for complex systems with evolving specifications or strict certification requirements.

It is commonly used in industries such as:

  • payment systems

  • embedded systems

  • telecom infrastructures

  • security-critical applications

 

MBT helps organizations maintain consistent validation processes while reducing long-term test maintenance costs.

Mellonne applies model-based testing by creating formal models of the System Under Test and automatically generating test cases from those models.

This approach ensures full traceability between:

  • system requirements

  • generated test scenarios

  • execution results

 

It allows teams to maintain consistent and scalable testing processes across different validation environments and certification workflows, including ecosystems aligned with standards such as EMVCo and GlobalPlatform.

Related Testing Tools

Model-based testing is most effective when combined with automated test execution platforms capable of running large sets of generated test scenarios.

Mellonne provides specialized tools designed to execute, validate, and analyze model-generated test cases while maintaining full traceability across validation environments.

These platforms support automated workflows and help teams maintain consistent testing processes across complex systems.

Juice – Web-Based Test Execution Platform

Configure, execute, and validate automated test sessions through a web-based platform designed for scalable test execution.

Juice allows teams to manage test campaigns, analyze results, and maintain full traceability between generated test scenarios and execution outcomes.

It is particularly suited for environments requiring repeatable testing processes and certification workflows.


Learn more about Juice

Terminal Simulator – EMV Testing Tool

Terminal Simulator enables engineers to simulate payment terminal behavior and validate EMV transaction flows in controlled testing environments.

It supports the validation of:
- chip transactions
- contactless payment scenarios
- mobile payment interactions

This allows teams to analyze communication between the terminal, card, and host systems while validating payment specifications aligned with EMVCo.
Discover the Terminal Simulator

Automate, Validate, and Optimize Your Testing with MBT

Automate, validate, and optimize complex testing environments using Mellonne’s model-based testing methodology.

Contact Mellonne to learn how MBT can improve your testing efficiency and compliance validation.

Discuss Your Testing Strategy