cleveragents/cleveragents-core
cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.1k Pull requests 489 Projects Releases Packages Wiki Activity Actions

refactor(test): remove all unittest.mock usage from Robot Framework integration tests #703

Closed
freemo wants to merge 5 commits from refactor/m3-remove-unittest-mock-integration into master
pull from: refactor/m3-remove-unittest-mock-integration
merge into: cleveragents:master
Conversation 5 Commits 5 Files changed 43 +2919 -2526
freemo commented 2026-03-12 00:23:17 +00:00
Owner
Copy link

Summary

Removes all unittest.mock usage (MagicMock, patch, create_autospec, PropertyMock) from 41 Robot Framework integration test files, replacing them with real dependency instantiation via a new shared stub library.

Closes #699

Changes

Created robot/_testing_stubs.py (383 lines) providing lightweight, Pyright-clean test doubles for integration tests:

  • Stub — generic attribute-bag replacing MagicMock (returns Stub() for any missing attribute)
  • SpyStub — records calls for assertion without mocking behavior
  • patch_attr — context manager replacing unittest.mock.patch for temporary attribute overrides
  • fake_settings — builds a real Settings instance with test defaults, replacing MagicMock(spec=Settings)

Updated 41 files across three categories:

Category Files Change
Helper files using MagicMock and/or patch 31 Replaced with Stub, SpyStub, patch_attr, fake_settings from _testing_stubs
Helper files using only patch 7 Replaced unittest.mock.patch with patch_attr from _testing_stubs
Robot files with inline unittest.mock 3 (binding_resolution.robot, google_provider.robot, openai_provider.robot) Replaced inline MagicMock with Stub via helper keywords

No Behave unit tests were modified — they continue using unittest.mock as permitted by CONTRIBUTING.md.

Quality Checks

  • nox -e typecheck — 0 Pyright errors
  • nox -e lint — all checks passed
  • nox -e format — all files unchanged
  • nox -e integration_tests — all affected Robot suites pass
  • No unittest.mock imports remain in any robot/ file
## Summary Removes all `unittest.mock` usage (`MagicMock`, `patch`, `create_autospec`, `PropertyMock`) from 41 Robot Framework integration test files, replacing them with real dependency instantiation via a new shared stub library. Closes #699 ## Changes Created `robot/_testing_stubs.py` (383 lines) providing lightweight, Pyright-clean test doubles for integration tests: - **`Stub`** — generic attribute-bag replacing `MagicMock` (returns `Stub()` for any missing attribute) - **`SpyStub`** — records calls for assertion without mocking behavior - **`patch_attr`** — context manager replacing `unittest.mock.patch` for temporary attribute overrides - **`fake_settings`** — builds a real `Settings` instance with test defaults, replacing `MagicMock(spec=Settings)` Updated 41 files across three categories: | Category | Files | Change | |----------|-------|--------| | Helper files using MagicMock and/or patch | 31 | Replaced with `Stub`, `SpyStub`, `patch_attr`, `fake_settings` from `_testing_stubs` | | Helper files using only patch | 7 | Replaced `unittest.mock.patch` with `patch_attr` from `_testing_stubs` | | Robot files with inline unittest.mock | 3 (`binding_resolution.robot`, `google_provider.robot`, `openai_provider.robot`) | Replaced inline `MagicMock` with `Stub` via helper keywords | No Behave unit tests were modified — they continue using `unittest.mock` as permitted by CONTRIBUTING.md. ## Quality Checks - `nox -e typecheck` — 0 Pyright errors - `nox -e lint` — all checks passed - `nox -e format` — all files unchanged - `nox -e integration_tests` — all affected Robot suites pass - No `unittest.mock` imports remain in any `robot/` file
refactor(test): remove all unittest.mock usage from Robot Framework integration tests
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 15s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 17s
Details
CI / security (pull_request) Successful in 38s
Details
CI / typecheck (pull_request) Successful in 39s
Details
CI / unit_tests (pull_request) Successful in 3m5s
Details
CI / integration_tests (pull_request) Successful in 3m42s
Details
CI / docker (pull_request) Successful in 59s
Details
CI / coverage (pull_request) Successful in 7m15s
Details
CI / benchmark-regression (pull_request) Successful in 36m40s
Details
1067ed5e40 
Replace MagicMock, patch, create_autospec, and PropertyMock with custom
lightweight test doubles in robot/_testing_stubs.py:

- Stub: drop-in for MagicMock with call tracking, return_value,
  side_effect, context-manager and iteration protocol support
- SpyStub: wraps a real object while tracking calls
- patch_attr(): replaces unittest.mock.patch/patch.object with
  context-manager and start/stop API support
- fake_settings(): replaces create_autospec(Settings, instance=True)
- _CallRecord: lightweight replacement for unittest.mock.call

All 42 files in robot/ directory updated. No file in robot/ imports
from unittest.mock. Features/mocks directory left untouched.

Passes: nox -e lint, nox -e typecheck (0 errors), nox -e unit_tests
(372 features, 10553 scenarios, 0 failed).

Closes #699
freemo added this to the v3.2.0 milestone 2026-03-12 00:23:53 +00:00
refactor: replace all unittest.mock patterns with real dependencies in robot integration tests
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / quality (pull_request) Successful in 18s
Details
CI / build (pull_request) Successful in 18s
Details
CI / security (pull_request) Successful in 35s
Details
CI / typecheck (pull_request) Successful in 41s
Details
CI / unit_tests (pull_request) Successful in 3m5s
Details
CI / integration_tests (pull_request) Failing after 3m27s
Details
CI / docker (pull_request) Successful in 53s
Details
CI / coverage (pull_request) Successful in 5m31s
Details
CI / benchmark-regression (pull_request) Successful in 35m29s
Details
30b6bfc810 
- Delete _testing_stubs.py (382 lines of Stub/SpyStub/patch_attr/fake_settings)
- Create _test_container.py with real service factories backed by in-memory SQLite
- Replace all .return_value/.assert_called/.call_args patterns across 41 helper files
- Use real PlanLifecycleService, CorrectionService, DecisionService, InvariantService
- Use real ResourceRegistryService, NamespacedProjectRepository, ProjectResourceLinkRepository
- Use real ActorService + ActorRegistry for TDD actor validation tests
- Use types.SimpleNamespace for lightweight structural interfaces (DI container resolve)
- Use InMemoryChangeSetStore (production class) for changeset tests
- Tag LLM-dependent tests with [Tags] llm-required for CI skip
- All modified files pass ruff check, ruff format, and pyright with zero errors

Implements CONTRIBUTING.md line 568: no mocking in integration tests.
- Add create_test_decision_service() and create_plan_for_decisions() to
  _test_container.py so DecisionService shares the same in-memory SQLite
  DB as PlanLifecycleService (fixes FK constraint on decisions.plan_id)
- Fix helper_plan_correct_tree_wiring.py: use shared DB for decisions
- Fix helper_event_bus.py: use shared DB for decision_service_emits_event
- Fix helper_m4_e2e_verification.py: use shared DB for cli-plan-tree,
  add regex-based JSON extraction to handle interleaved log lines
- Fix helper_resource_handlers.py: use real temp dirs with
  SandboxStrategy.NONE for git-resolve and fs-resolve tests
- Fix helper_m1_sourcecode_smoke.py: plan_diff() now creates a real
  PlanApplyService with InMemoryChangeSetStore and changeset_id
- Fix helper_actor_cli_show.py: upsert() instead of save(), flexible
  list assertion for built-in actors
- Fix helper_apply_pipeline.py: set terminal APPLIED state for
  already-applied test
- Fix helper_cli_extensions.py: set inputs_schema on action object
  (not via create_action kwarg)
- Fix helper_m3_decision_validation_smoke.py: dict access for
  attach_validation() return value
- Fix helper_plan_cli_spec.py: project_links with ProjectLink objects
- Add prepare_plan_for_execute/apply calls across lifecycle helpers

All 110 targeted robot tests pass. Quality gates: typecheck (0 errors),
lint (all passed), format (1415 files formatted).
fix(test): use model_id instead of model in provider attribute checks
Some checks failed
CI / lint (pull_request) Successful in 15s
Details
CI / typecheck (pull_request) Successful in 40s
Details
CI / security (pull_request) Successful in 38s
Details
CI / quality (pull_request) Successful in 34s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 19s
Details
CI / unit_tests (pull_request) Successful in 5m12s
Details
CI / integration_tests (pull_request) Successful in 6m7s
Details
CI / docker (pull_request) Successful in 4m12s
Details
CI / coverage (pull_request) Successful in 6m54s
Details
CI / benchmark-regression (pull_request) Has been cancelled
Details
72ddf83fdf 
GoogleChatProvider and OpenAIChatProvider store the model name as
model_id (inherited from LangChainChatProvider), not model. The
attribute check tests were asserting the wrong attribute name.
fix(test): fix IndentationError in provider env-gating inside Robot Catenate blocks
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 17s
Details
CI / typecheck (pull_request) Successful in 38s
Details
CI / security (pull_request) Successful in 40s
Details
CI / integration_tests (pull_request) Successful in 3m28s
Details
CI / unit_tests (pull_request) Successful in 5m17s
Details
CI / docker (pull_request) Successful in 22s
Details
CI / coverage (pull_request) Successful in 5m35s
Details
CI / benchmark-regression (pull_request) Successful in 35m54s
Details
1a584563a7 
Robot Framework's Catenate with SEPARATOR=\n strips leading whitespace
from continuation lines, so a multi-line if/body block:

    ...    if not api_key:
    ...        print('SKIP: ...'); sys.exit(0)

becomes invalid Python (print at column 0 after the if). Collapse the
if and its body onto a single line so indentation is not needed.
freemo self-assigned this 2026-03-12 20:33:27 +00:00
freemo commented 2026-03-12 20:46:21 +00:00
Author
Owner
Copy link

PM Status — Day 32

Status: CONFLICTED — needs rebase. Part of the mock removal initiative.

PR: Remove all unittest.mock from Robot Framework integration tests (41 files). M3 (v3.2.0), overdue. Author: @freemo. 0 comments, 0 reviews.

Context: This is part of the mock removal epic (#699). Issues #698 and #700 were already completed via direct commits to master. #724 was also completed on master. This PR covers the remaining 41-file integration test cleanup.

Action Required:

  1. @freemo: Rebase onto current master. Since you've been pushing mock removal commits directly to master, some of this PR's changes may already be on master — verify after rebase.
  2. Labels: Has Type/Task. Missing Priority (High), MoSCoW (Must have), Points (13), State (In Progress).
  3. Needs peer review after rebase — suggest @brent.edwards since mock removal affects test infrastructure.
## PM Status — Day 32 **Status**: CONFLICTED — needs rebase. Part of the mock removal initiative. **PR**: Remove all `unittest.mock` from Robot Framework integration tests (41 files). M3 (v3.2.0), overdue. Author: @freemo. 0 comments, 0 reviews. **Context**: This is part of the mock removal epic (#699). Issues #698 and #700 were already completed via direct commits to master. #724 was also completed on master. This PR covers the remaining 41-file integration test cleanup. **Action Required**: 1. **@freemo**: Rebase onto current master. Since you've been pushing mock removal commits directly to master, some of this PR's changes may already be on master — verify after rebase. 2. Labels: Has Type/Task. Missing Priority (High), MoSCoW (Must have), Points (13), State (In Progress). 3. Needs peer review after rebase — suggest @brent.edwards since mock removal affects test infrastructure.
freemo commented 2026-03-13 22:06:02 +00:00
Author
Owner
Copy link

Rebase Required

@freemo — This PR has merge conflicts with master. Please rebase onto the latest master and force-push. See also: #668, #669, #708, #713, #720, #722 (all need rebase).

## Rebase Required @freemo — This PR has merge conflicts with `master`. Please rebase onto the latest `master` and force-push. See also: #668, #669, #708, #713, #720, #722 (all need rebase).
freemo commented 2026-03-14 04:40:26 +00:00
Author
Owner
Copy link

PM Review — Day 34

Status: NOT mergeable (conflicts), 0 reviews, M3 (v3.2.0), Priority/High, 21 points
Closes: #699 | Author: @freemo

Review Summary

Architecturally sound refactor that replaces all unittest.mock usage in Robot Framework integration tests with real service dependencies backed by in-memory SQLite. This is the correct direction per CONTRIBUTING.md §568 (integration tests must exercise real services).

42 files changed across robot/ — the largest scope PR currently open.

Key Findings

The refactor exposed and fixed real bugs hidden by mocks:

  • FK constraint violations on decisions.plan_id (masked by MagicMock)
  • Actor CLI calling .save() (doesn't exist — real method is .upsert())
  • Provider tests checking .model (real attribute is .model_id)
  • Plan lifecycle missing required state transitions
  • project_links expecting raw dicts instead of ProjectLink objects

This validates the entire approach — mocks were silently accepting wrong attribute names, wrong method calls, and wrong data structures.

Issues

[BLOCKING] Merge conflicts — mergeable: false. Several overlapping mock-removal issues (#698, #700, #724) were landed via direct master commits, causing conflicts. Rebase required.

[STALE] PR description misleading — The body describes the Phase 1 _testing_stubs.py approach (Stub, SpyStub, patch_attr), which was deleted in commit 2. The actual implementation uses _test_container.py with real services. Description must be updated after rebase.

[MINOR] Messy commit history — Commit 1 creates _testing_stubs.py, commit 2 deletes it entirely. Consider squashing during rebase.

[MINOR] Points discrepancy — PR is labeled Points/21 but parent issue #699 is Points/5. The scope justifies 21.

Action Items

Who Action Deadline
@freemo Rebase onto current master, resolve conflicts, update PR description Day 36
@freemo Verify all 110 robot tests pass post-rebase Day 36
@brent.edwards Peer review after rebase (QA lead, test infrastructure domain) Day 37

This PR is high-value — it eliminates an entire class of false-positive test results across the integration suite. Priority to unblock after rebase.

## PM Review — Day 34 **Status**: NOT mergeable (conflicts), 0 reviews, M3 (v3.2.0), Priority/High, 21 points **Closes**: #699 | **Author**: @freemo ### Review Summary Architecturally sound refactor that replaces all `unittest.mock` usage in Robot Framework integration tests with real service dependencies backed by in-memory SQLite. This is the correct direction per CONTRIBUTING.md §568 (integration tests must exercise real services). **42 files changed** across `robot/` — the largest scope PR currently open. ### Key Findings **The refactor exposed and fixed real bugs hidden by mocks:** - FK constraint violations on `decisions.plan_id` (masked by MagicMock) - Actor CLI calling `.save()` (doesn't exist — real method is `.upsert()`) - Provider tests checking `.model` (real attribute is `.model_id`) - Plan lifecycle missing required state transitions - `project_links` expecting raw dicts instead of `ProjectLink` objects This validates the entire approach — mocks were silently accepting wrong attribute names, wrong method calls, and wrong data structures. ### Issues **[BLOCKING] Merge conflicts** — `mergeable: false`. Several overlapping mock-removal issues (#698, #700, #724) were landed via direct master commits, causing conflicts. Rebase required. **[STALE] PR description misleading** — The body describes the Phase 1 `_testing_stubs.py` approach (Stub, SpyStub, patch_attr), which was **deleted** in commit 2. The actual implementation uses `_test_container.py` with real services. Description must be updated after rebase. **[MINOR] Messy commit history** — Commit 1 creates `_testing_stubs.py`, commit 2 deletes it entirely. Consider squashing during rebase. **[MINOR] Points discrepancy** — PR is labeled Points/21 but parent issue #699 is Points/5. The scope justifies 21. ### Action Items | Who | Action | Deadline | |-----|--------|----------| | @freemo | **Rebase** onto current master, resolve conflicts, update PR description | Day 36 | | @freemo | Verify all 110 robot tests pass post-rebase | Day 36 | | @brent.edwards | **Peer review** after rebase (QA lead, test infrastructure domain) | Day 37 | This PR is high-value — it eliminates an entire class of false-positive test results across the integration suite. Priority to unblock after rebase.
freemo reviewed 2026-03-14 22:07:39 +00:00
freemo left a comment
Copy link

PM Status — Day 34

@freemo — unittest.mock removal from 41 Robot files (#699). Has merge conflicts. Must Have / Priority High.

Status: Conflicted. This is the largest remaining mock removal item. Depends on PR #710 (CI LLM keys) being configured first.

Dependency chain: PR #710 (CI keys) → PR #703 (mock removal) → M3 mock removal 100% complete.

Priority: Critical for M3 closure. Please rebase after #710 is ready.

PM status — Day 34

## PM Status — Day 34 @freemo — unittest.mock removal from 41 Robot files (#699). Has merge conflicts. **Must Have / Priority High**. **Status**: Conflicted. This is the largest remaining mock removal item. Depends on PR #710 (CI LLM keys) being configured first. **Dependency chain**: PR #710 (CI keys) → PR #703 (mock removal) → M3 mock removal 100% complete. **Priority**: Critical for M3 closure. Please rebase after #710 is ready. --- *PM status — Day 34*
freemo commented 2026-03-14 22:21:24 +00:00
Author
Owner
Copy link

wont do, did E2E tests instead

wont do, did E2E tests instead
freemo closed this pull request 2026-03-14 22:21:24 +00:00
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 16s
Required
Details
CI / build (pull_request) Successful in 16s
Required
Details
CI / quality (pull_request) Successful in 17s
Required
Details
CI / typecheck (pull_request) Successful in 38s
Required
Details
CI / security (pull_request) Successful in 40s
Required
Details
CI / integration_tests (pull_request) Successful in 3m28s
Required
Details
CI / unit_tests (pull_request) Successful in 5m17s
Required
Details
CI / docker (pull_request) Successful in 22s
Required
Details
CI / coverage (pull_request) Successful in 5m35s
Required
Details
CI / benchmark-regression (pull_request) Successful in 35m54s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  
controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
v3.2.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
freemo
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#699 refactor(test): Remove all unittest.mock usage from Robot Framework integration tests
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core!703
No description provided.