Most Powerful Open Source ERP

Nexedi test naming convention

Document describing how we name tests
  • Last Update:2019-12-05
  • Version:001
  • Language:en

Introduction

This document describes the naming convention we use for Tests.

Format

<project>(.<sub_project>)*.<type_of_test>-<revision>

Where

  • "project" - is name of the project and / or product (like ERP5 or Wendelin)
  • "sub_project" - is the name of a sub project or a sub product or component of main one
  • "type_of_test" - is the type of test being run. We support this minimal set of tests
    • UnitTest - an ERP5 based unit tests (it can include instance creation, too)
    • StandaloneDeploymentScriptTest - a test which tests software instalation and instance creating inside a fresh virtual or bare metal machine
    • ScalabilityTest - a test of the scalability of a cluster
    • PerformanceTest - a test which test performance against already set metrics of ERP5 code. It monitors for regressions of the metrics itself
    • ResilienceTest - a test which test the resiliency of the deployed software stack
  • "revision" - the revisions of the tested software. Usually either a branch name or tag and / or in case of deployment tests the operating system version

More information for names of tests used in ERP5 names can be found here.