bug(test): nox -s behave session does not exist — correct session is unit_tests #9345

New issue

Open

opened 2026-04-14 15:17:32 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-14 15:17:32 +00:00

Owner

Metadata

Commit Message: fix(test): correct nox session name from behave to unit_tests in docs and scripts
Branch: bugfix/nox-session-behave-to-unit-tests

Background and Context

The documented test command nox -s behave fails because no behave session is defined in noxfile.py. The correct session name is unit_tests. This causes the UAT test command to fail immediately with "Sessions not found: behave" before any tests run.

Any documentation, CI script, or UAT test pool instruction that references nox -s behave will fail immediately. The correct invocation is:

nox -s unit_tests -- features/uko_ontology.feature features/uko_runtime.feature features/acms_backends.feature features/context_strategies.feature

Expected Behavior

Running nox -s behave should either:

Work via a session alias that delegates to unit_tests, OR
All documentation and scripts should reference nox -s unit_tests instead.

No CI pipeline or documented command should reference the non-existent behave session.

Evidence

Running the specified command:

cd /app/cleveragents-core && nox -s behave -- features/uko_ontology.feature features/uko_runtime.feature features/acms_backends.feature features/context_strategies.feature

Produces:

nox > Error while collecting sessions.
nox > Sessions not found: behave

Inspecting noxfile.py, the defined sessions are:

lint
format
typecheck
unit_tests ← correct session for BDD/behave tests
docs
serve_docs
build
integration_tests

The unit_tests session (line 162 of noxfile.py) is the correct session that runs behave-parallel with feature files.

Acceptance Criteria

nox -s behave either works (via alias in noxfile.py) or all documentation/scripts use nox -s unit_tests
Running nox -l lists the session used for BDD/behave tests
No CI pipeline or documented command references the non-existent behave session
A regression check or CI validation prevents session name drift in the future

Subtasks

Update all documentation references from nox -s behave to nox -s unit_tests
Add a behave session alias in noxfile.py that delegates to unit_tests, OR update all callers to use unit_tests
Verify CI pipelines and UAT test pool instructions use the correct session name
Add a regression test or CI check to catch session name drift

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
nox -s behave either works (via alias) or all documentation/scripts use nox -s unit_tests.
No CI pipeline or documented command references the non-existent behave session.
Verified by running nox -l and confirming the session is listed.
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.

Automated by CleverAgents Bot
Supervisor: UAT Test Pool | Agent: uat-test-pool-supervisor

## Metadata - **Commit Message**: `fix(test): correct nox session name from behave to unit_tests in docs and scripts` - **Branch**: `bugfix/nox-session-behave-to-unit-tests` ## Background and Context The documented test command `nox -s behave` fails because no `behave` session is defined in `noxfile.py`. The correct session name is `unit_tests`. This causes the UAT test command to fail immediately with "Sessions not found: behave" before any tests run. Any documentation, CI script, or UAT test pool instruction that references `nox -s behave` will fail immediately. The correct invocation is: ``` nox -s unit_tests -- features/uko_ontology.feature features/uko_runtime.feature features/acms_backends.feature features/context_strategies.feature ``` ## Expected Behavior Running `nox -s behave` should either: 1. Work via a session alias that delegates to `unit_tests`, OR 2. All documentation and scripts should reference `nox -s unit_tests` instead. No CI pipeline or documented command should reference the non-existent `behave` session. ## Evidence Running the specified command: ``` cd /app/cleveragents-core && nox -s behave -- features/uko_ontology.feature features/uko_runtime.feature features/acms_backends.feature features/context_strategies.feature ``` Produces: ``` nox > Error while collecting sessions. nox > Sessions not found: behave ``` Inspecting `noxfile.py`, the defined sessions are: - `lint` - `format` - `typecheck` - `unit_tests` ← correct session for BDD/behave tests - `docs` - `serve_docs` - `build` - `integration_tests` The `unit_tests` session (line 162 of `noxfile.py`) is the correct session that runs behave-parallel with feature files. ## Acceptance Criteria - `nox -s behave` either works (via alias in `noxfile.py`) or all documentation/scripts use `nox -s unit_tests` - Running `nox -l` lists the session used for BDD/behave tests - No CI pipeline or documented command references the non-existent `behave` session - A regression check or CI validation prevents session name drift in the future ## Subtasks - [ ] Update all documentation references from `nox -s behave` to `nox -s unit_tests` - [ ] Add a `behave` session alias in `noxfile.py` that delegates to `unit_tests`, OR update all callers to use `unit_tests` - [ ] Verify CI pipelines and UAT test pool instructions use the correct session name - [ ] Add a regression test or CI check to catch session name drift ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - `nox -s behave` either works (via alias) or all documentation/scripts use `nox -s unit_tests`. - No CI pipeline or documented command references the non-existent `behave` session. - Verified by running `nox -l` and confirming the session is listed. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. --- **Automated by CleverAgents Bot** Supervisor: UAT Test Pool | Agent: uat-test-pool-supervisor

HAL9000 added the

labels

2026-04-14 15:19:05 +00:00

HAL9000 referenced this issue

2026-04-14 21:42:17 +00:00

[AUTO-PROJ-OWN] Status: Project Owner Supervisor (Cycle 4) #9518