Menu
Introduction
Getting Started
Developer guide
Release
Architecture
CLI
Technical documentations
Version
Publication date

Mar 9, 2022

Confidentiality
Public
Reactions
1
Share

Brick test runner

TASK
Typing name :  TASK.gws_core.BrickTestRunner Brick :  gws_core

Run pytest suites of bricks inside a fresh glab container and collect JUnit results.

Run brick test suites inside a fresh glab test container.

This task installs a configurable set of bricks inside a sub-compose, runs gws server test-all for the bricks marked "Run tests", and reports the JUnit XML output. The task always finishes in success so the structured summary is available downstream — inspect summary.is_success to learn whether the underlying tests actually passed.

Inputs / Outputs

  • results (Folder): folder containing the per-brick *.xml JUnit reports at the top level, plus a <brick>/log file per brick with the JSON log output of that brick's test run.
  • summary (JSONDict): aggregated counts (totals + per-brick breakdown) and the list of test failures.

Parameters

  • bricks (ParamSet): one row per brick to install. Each row carries name, version and a run_tests toggle. gws_core must be present.
  • parallel: pass --parallel to gws server test-all.
  • compose_timeout_seconds: cap how long the test container can run.

Output

JUnit XML folder
Raw per-brick JUnit XML files.
Test summary
Aggregated counts and failures.

Configuration

bricks

gws_core is mandatory.

Type : ListMaximum occurrences number : -1

name

Brick to install (e.g. gws_core).

Type : string

version

Version tag, e.g. 0.22.0-beta.5.

Type : string

run_tests

Optional

Run this brick's pytest suite.

Type : boolDefault value : true

parallel

Optional

Pass --parallel to gws server test-all.

Type : bool

compose_timeout_seconds

Optional

Maximum wait for the test container to finish.

Type : intDefault value : 3600
Shine Logo
Technical bricks to reuse or customize

Have you developed a brick?

Share it to accelerate projects for the entire community.