Skip to main content

Concept

What is MANDOS?​

MANDOS is short for MultiversX Account, Network and Data Operation Scenarios. We sometimes call them simply "scenarios".

They were designed to test the VM and the early contracts in a language-agnostic way, hence initially implemented in JSON.

Initially written manually, they were gradually superseded by Rust tests. The format, however, is still very useful, since it can be generated from a backend, and then re-run on another.

Concept​

Let's think for a moment how an interaction with a blockchain might look like.

The only way to change the blockchain state is by sending transactions. We might also need to query some contracts in between sending these transactions. We might also query the blockchain state (balances, for instance) directly. Let's call these actions "steps". In a simulated environment, we need at least an additional step: initializing the sandbox.

Several steps form a scenario.

A scenario is any interaction with a blockchain, composed of one or more steps. These interactions might be:

  • real, completed on a real blockchain, a history of sorts;
  • programmed to be executed in the future;
  • simulated, but using real blockchain data;
  • simulated, using absurd or unrealistic data.

So it doesn't really matter if these steps are real or imagined. All that matters is that they obey the rules of the blockchain.

Because of their generality, it is natural to think of all blockchain interactions and black-box tests as such scenarios.

Scenario formats​

The concept of scenario is not tied to a specific technology, or language.

Historically, they started out as JSON tests. But writing a lot of JSON by hand is very inconvenient and unproductive, so we came up with a very similar syntax in Rust. When we created the interactor framework, we found that the scenario model fits naturally to real interactions too.

important

Nowadays, we think that the JSON scenario format is best used for interoperability and replays, not for writing tests.

There are several ways to generate a scenario JSON file automatically, and we encourage developers to move away from writing them by hand.

The greatest benefit of the JSON format is that it is language-agnostic, and so it can be used with any of our backends.

Scenarios as tests​

Scenarios also have syntax for checking transaction outputs and the blockchain state. This means that each scenario is also a test. Any failing check causes the scenario test to fail.

What kind of tests are they?

They are always black-box tests. They model real blockchain interactions, so there is no way for them to peek inside contracts and access their private functions.

Typed vs. untyped scenarios​

Transaction data on the blockchain is not really typed. Arguments, storage, logs, etc. - they are all untyped at blockchain level. The types are only added by developers when writing contracts, to avoid bugs and make them safer to use.

But this means that scenarios in their most general form are also untyped. This fits JSON well, which is also (mostly) untyped.

It clearly becomes tiring, as a developer, to only be able to work with untyped and un-annotated data. There are two ways to overcome this:

  • Using a typed version of the scenarios. This is what we do when working with scenarios in Rust.
  • Using a specialized language to make values easier to read by developers.

These are the scenario value expressions, and they help us better express numbers, addresses, or even more complex data. Note that this does not add any type checks, it is a purely cosmetic affair. The format is detailed here and here.