Files
AgentLab/backend/tests/test_datasource.py
ThearchyHelios 03c18c4d78 界面文案整改:口语改书面、术语统一、不再露出实现细节;修掉几处说错的提示;新增文案检查防回潮
一、文案(前端约 1600 处,后端传到界面的约 880 处)
- 术语统一:工作流层面用「运行」(继续运行、重新运行、试运行),节点和工具层面用「执行」,不再用「跑」;
  总时长 / 执行时长 / 等待审批;服务端;助手;Agent;token;工作流;固定版本;模型接入;系统提示;批准 / 驳回;受管级别
- 口语改书面:取不到、没取回来、读不懂、连不上、多半、照样、兜底、揉成这类说法改成「无法 / 未能 / 失败 / 请」;去掉拟人写法
- 不再露出实现细节:界面上不写 checkpoint、同一拍、哈希(凭证处除外),不写改版历史(「以前…」「老数据」);
  报错、校验、门禁、自动修复里裸写的配置键名和枚举值换成界面上的中文标签,由新的 backend/app/engine/labels.py 统一提供;
  发布弹窗里结论句的选项不再是 off / require_citation
- 同一件事只留一种说法:生成阶段文案、出具档位说明、画布锁定提示各合成一份
- 去掉界面上的工业场景示例(MES、ERP、「张工」「王工」)和真实产品名,换成通用示例

二、说错的提示(都有测试证明)
- 数据库测连接失败时的专用提示以前从不出现(按报错文字全等比较,永远比不上):改为按错误类型判断,不再拼出重复的前缀
- 「设置 → 供应商」改指「设置 → 模型接入」;「在设置里建数据源」改指「数据」页
- 缺少 API Key、模型接入已停用的报错不再夹英文,写明去哪里填
- 两处原因说错(「这种引用在后续版本支持」「这一版还不支持」)改成真实原因
- 节点说明里不准确的说法改正:代码节点在 microVM 或系统沙箱中执行;报告撰写、口径卡的说明不再说过头
- 导出的证据 CSV 里两列同名,第三列改为「片段编号」

三、前后端对齐
- 前端按后端原文识别日志、报错的地方,新旧两种写法都认得(历史运行里存的是旧文字),逐条补了新旧原文的核对
- 后端交回模型的原指令放进单独的 for_model 字段,前端在解析响应时去掉,不会显示到界面上

四、检查
- 检查脚本里按原文匹配的断言改成新文案;改完会变成永远成立的反向断言逐条修正,并做了变异验证
- 新增 check-copy(静态扫描前端界面字符串和后端上界面的文案):再出现「跑」「后端」「多半」「令牌」、
  界面上的 Copilot、裸写的配置键名、半角标点等就报错;确需保留的写进 scripts/copy-allow.json 并注明理由
2026-09-30 08:05:15 +08:00

254 lines
9.7 KiB
Python
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
"""数据源连接层与工具层。
用真实的 SQLite 库跑——SQLAlchemy 统一了方言,SQLite 走的是和 MySQL/Oracle
同一套代码路径,所以这里验证的不只是 SQLite。各驱动特有的差异(Oracle 的
service_name、MySQL 的 charset)在 URL 构造那组用例里覆盖。
"""
from __future__ import annotations
import json
import sqlite3
from types import SimpleNamespace
import pytest
from app.data.engine import build_url, run_query, test_connection
from app.data.guard import QueryLimits, SqlRejected
from app.data.introspect import describe_table, introspect, summary, table_names
from app.main import app as _fastapi_app
from httpx import ASGITransport, AsyncClient
@pytest.fixture
async def client():
transport = ASGITransport(app=_fastapi_app)
async with AsyncClient(transport=transport, base_url="http://test") as c:
yield c
@pytest.fixture
def shop_db(tmp_path):
"""一个最小但真实的业务库:地区 / 商品 / 订单。"""
path = tmp_path / "shop.db"
db = sqlite3.connect(path)
db.executescript("""
CREATE TABLE regions (id INTEGER PRIMARY KEY, name TEXT NOT NULL);
CREATE TABLE orders (
id INTEGER PRIMARY KEY, region_id INTEGER NOT NULL,
qty INTEGER NOT NULL, amount REAL NOT NULL, ordered_at TEXT NOT NULL
);
""")
db.executemany("INSERT INTO regions(id,name) VALUES(?,?)",
[(1, "华东"), (2, "华北")])
db.executemany(
"INSERT INTO orders(id,region_id,qty,amount,ordered_at) VALUES(?,?,?,?,?)",
[(i, 1 + i % 2, i, i * 10.5, "2026-06-15") for i in range(1, 101)],
)
db.commit()
db.close()
return str(path)
@pytest.fixture
def source(shop_db):
return SimpleNamespace(
id="test-src", name="sales", kind="sqlite", database=shop_db,
host=None, port=None, username=None, password=None, options={},
readonly=True, description="测试销售库", schema_cache={},
)
async def test_connection_and_introspect(source):
assert (await test_connection(source))["ok"]
source.schema_cache = await introspect(source)
assert set(table_names(source)) == {"regions", "orders"}
orders = source.schema_cache["tables"]["orders"]
assert [c["name"] for c in orders["columns"]] == [
"id", "region_id", "qty", "amount", "ordered_at"
]
assert orders["primary_key"] == ["id"]
async def test_summary_is_compact_enough_for_a_prompt(source):
source.schema_cache = await introspect(source)
text = summary(source)
assert "orders" in text and "amount" in text
# 摘要要能塞进 system prompt——超出这个量级就该改成按需探查
assert len(text) < 2000
async def test_summary_says_so_when_never_introspected(source):
"""没探查过就明说,别让 Copilot 对着空气编表名。"""
assert "尚未探查结构" in summary(source)
async def test_describe_table_accepts_qualified_name(source):
"""模型可能传 SCHEMA.TABLE 全名,也可能只传表名,两种都要认。"""
source.schema_cache = await introspect(source)
assert "amount" in describe_table(source, "orders")
assert "amount" in describe_table(source, "main.orders")
assert "amount" in describe_table(source, "ORDERS") # Oracle 惯用大写
async def test_describe_table_lists_unknown_table_options(source):
source.schema_cache = await introspect(source)
out = describe_table(source, "没有这张表")
assert "现有的对象" in out and "orders" in out
async def test_query_returns_rows(source):
result = await run_query(source, "SELECT COUNT(*) AS c FROM orders")
assert result.rows[0][0] == 100
assert result.columns == ["c"]
async def test_readonly_guard_applies_on_real_connection(source):
"""守卫不能只在单测里生效——真实连接路径上也必须拦住。"""
for sql in ("UPDATE orders SET qty=0", "DROP TABLE orders", "SELECT 1; DROP TABLE orders"):
with pytest.raises(SqlRejected):
await run_query(source, sql)
# 数据确实没被动过
assert (await run_query(source, "SELECT COUNT(*) FROM orders")).rows[0][0] == 100
async def test_result_set_is_capped(source):
"""一条 SELECT * 不该把内存和模型上下文一起打爆。"""
result = await run_query(source, "SELECT * FROM orders", limits=QueryLimits(max_rows=10))
assert result.row_count == 10
assert result.truncated is True
async def test_rows_are_json_serializable(source):
"""Decimal / date / bytes 在真实业务数据里遍地都是,不处理等于不可用。"""
result = await run_query(source, "SELECT amount, ordered_at FROM orders LIMIT 3")
json.dumps(result.to_payload()) # 不抛就算过
# --------------------------------------------------------------------------
# URL 构造:各驱动的方言差异
# --------------------------------------------------------------------------
def _src(kind, **kw):
base = dict(id="x", name="n", readonly=True, host="db", port=None,
database=None, username="u", password="p", options={})
base.update(kw)
return SimpleNamespace(kind=kind, **base)
@pytest.mark.parametrize("kind,expect", [
("mysql", "mysql+aiomysql://"),
("postgres", "postgresql+asyncpg://"),
("oracle", "oracle+oracledb://"),
])
def test_url_uses_async_drivers(kind, expect):
opts = {"service_name": "ORCL"} if kind == "oracle" else {}
assert build_url(_src(kind, database="d", options=opts)).startswith(expect)
def test_password_is_masked_by_default():
"""密码不该出现在日志、事件流或任何返回给前端的地方。"""
url = build_url(_src("mysql", database="d"))
assert "***" in url and ":p@" not in url
def test_oracle_requires_service_name_or_sid():
"""Oracle 最常见的配错点,要给明确提示而不是让驱动报晦涩的 ORA 错误。"""
with pytest.raises(ValueError, match="service_name"):
build_url(_src("oracle"))
def test_oracle_accepts_database_as_service_name():
assert "service_name=ORCLPDB1" in build_url(_src("oracle", database="ORCLPDB1"))
def test_unknown_kind_is_rejected():
with pytest.raises(ValueError, match="不支持"):
build_url(_src("mongodb"))
# --------------------------------------------------------------------------
# schema 发现:各家的 "schema" 根本不是同一个东西
# MySQL schema == database(SHOW schemas)
# Oracle schema == user(all_users)
# PG database > schema(pg_namespace)
# SQLite 只有 main + attached
# 所以这组用例守的是"不管哪一家,探不到东西时都要给出可走的下一步"。
# --------------------------------------------------------------------------
async def test_sqlite_degrades_without_information_schema(source):
"""SQLite 没有 information_schema,统计路径要安静地降级而不是报错。"""
from app.data.introspect import list_schemas, schema_stats
assert await schema_stats(source) == []
assert isinstance(await list_schemas(source), list)
async def test_qualified_name_omits_schema_when_absent(source):
"""没有 schema 概念时不要硬拼前缀,否则生成的 SQL 反而错。"""
source.schema_cache = await introspect(source)
assert source.schema_cache["tables"]["orders"]["qualified"] == "orders"
async def test_qualified_name_includes_schema_when_given(source):
"""有 schema 时必须带前缀——Oracle 上少了它就是 ORA-00942。"""
cache = await introspect(source, schema="main")
assert cache["tables"]["orders"]["qualified"] == "main.orders"
def test_schema_stats_sql_covers_every_supported_kind():
"""新增数据库类型时别忘了这里——漏了就退化成黑名单猜测。"""
from app.data.engine import SUPPORTED_KINDS
from app.data.introspect import _SCHEMA_STATS_SQL
# sqlite 显式短路,其余要么有专用 SQL,要么落到 information_schema 标准路径
assert "oracle" in _SCHEMA_STATS_SQL
assert "_standard" in _SCHEMA_STATS_SQL
for kind in SUPPORTED_KINDS:
assert kind in _SCHEMA_STATS_SQL or kind in ("sqlite", "mysql", "mariadb",
"postgres", "postgresql")
# --------------------------------------------------------------------------
# 探查失败 ≠ 还没探查
# --------------------------------------------------------------------------
#
# run 554a0f92:shop 的探查因为 "Lost connection to MySQL server during query"
# 失败了,但失败被存成了一个"成功但没表"的缓存,schema_synced_at 照常盖戳。
# 于是 db_schema 工具对 agent 说"还没有探查过结构,请在设置页里执行一次"——
# 一句错话,配一个 agent 根本做不到的动作。它只好自己摸:猜 7 个表名、发一条
# SELECT 1 试连通性、再用三条 information_schema 把 schema 重建一遍。
# 9 次工具调用花掉 6 次,前 29 秒没碰到一点真数据。
#
# 而 available_schemas 那 10 个候选一直躺在缓存里,没人交给它。
class _FailedCache:
"""探查失败之后 schema_cache 的样子。"""
name = "shop"
kind = "mysql"
database = "prod_shop"
description = ""
readonly = True
schema_cache = {
"tables": {}, "total": 0, "failed": True,
"error": "OperationalError: (2013, 'Lost connection to MySQL server during query')",
"available_schemas": ["prod_shop", "shop_dev", "toolsdb"],
}
class _NeverRun(_FailedCache):
"""从来没探查过的样子。和上面必须说不一样的话。"""
schema_cache: dict = {}
def test_why_empty_tells_the_two_cases_apart():
from app.data.introspect import why_empty
assert "失败" in why_empty(_FailedCache.schema_cache)
assert "Lost connection" in why_empty(_FailedCache.schema_cache)
assert why_empty({}) == "尚未探查结构"