Testing in Mavkit

Testing is important to ensure the quality of the Mavkit codebase by detecting bugs and avoiding regressions. Mavkit and its components use a variety of tools and frameworks for testing.

This page groups the documentation helping developers to design, write, and execute tests on the Mavkit codebase. It covers different kinds of tests (Unit, Integration, etc.) and the associated tools and frameworks. It also includes tutorials for testing more specific parts such as protocol code.

• Overview of Testing in Mavkit
  • Testing frameworks
  • Executing tests locally
  • Executing tests through the GitLab CI
  • Conventions

• Ppx_expect
  • How to run tests
  • How to add tests
  • Where to put the tests
  • Integration with Lwt

• Tezt: OCaml Mavryk Test Framework
  • How to Run Tests
  • How to Write New Integration Tests
  • How to Write New Unit Tests
  • Regression Tests

• Tezt: Long Tests and Performance Regression Test Framework
  • Adding a Long Test
  • Performance Regression Test framework: Time Series, Alerts and Graphs
  • Example
  • Providing Large Data
  • Testing Your Benchmarks Locally

• Alcotezt: An Alcotest Compatibility Wrapper for Tezt
  • Running Alcotezts
  • Notable Differences Between Alcotest and Alcotezt

• Making legacy code unit-testable
  • Solutions

• How to Test a Protocol Proposal
  • The master Branch
  • Unit Tests and Sandboxed Mode
  • Testing Migration Code
  • Migration Testing
  • Wrap up the Migration Procedure
  • Tips and Tricks
  • Anatomy of Migration Code