forked from ExtendDB/extenddb
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathexternal-suites.sample.toml
More file actions
executable file
·32 lines (29 loc) · 1.26 KB
/
external-suites.sample.toml
File metadata and controls
executable file
·32 lines (29 loc) · 1.26 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
# Copyright 2026 ExtendDB contributors
# SPDX-License-Identifier: Apache-2.0
# ExtendDB external test suite registry - sample template
#
# Copy this file to external-suites.toml and edit as needed to add additional,
# project- or organization-specific test suites. To execute a configured test
# suite, run:
# devtools/run-tests --extenddb --external
#
# Each [[suite]] entry describes an external test suite that can be run against extenddb.
# Suites are referenced by path — never copied into the repo.
#
# Fields:
# name — Human-readable name (used in reports)
# path — Absolute path or ~ path to the suite root directory
# runner — Build/test tool: "maven", "gradle", "pytest", "cargo"
# env — Environment variables passed to the test runner
# args — Extra arguments passed to the test command
# prereqs — Commands that must succeed for the suite to be runnable
# enabled — Set to false to skip without removing the entry
# Configure a test suite.
# [[suite]]
# name = "My Additional Function Tests"
# path = "~/source/tests/functional/FunctionalTests"
# runner = "maven"
# enabled = true
# Configure environment variables needed by your test suites.
# [suite.env]
# DDB_ENDPOINT = "${EXTENDDB_ENDPOINT}"