f9f6bc01fd
CI / test (push) Canceled after 0s
## Summary epic r04 - begin refactor ## Change Type - [x] Cowork feature - [ ] Bug fix - [ ] Core AI contribution - [ ] Test / hardening - [ ] Performance - [ ] Documentation ## Related Work Cowork Task: Core Repo: http://34.143.229.138/gitea-admin/fsg-ai-core-assets Core AI Issue: Core Task: Related PR: ## Scope What is intentionally included? What is intentionally NOT included? ## Validation - [ ] Unit tests - [ ] Integration tests - [ ] Manual verification - [ ] Regression check Commands / evidence: ## Security Impact Permission / credential / network / customer data impact: ## Compatibility - [ ] No breaking change - [ ] Breaking change documented ## Reviewer Notes Anything Cowork reviewers should pay attention to. --------- Co-authored-by: Anh Tran Nguyen Minh <anhtnm1@fpt.com> Co-authored-by: Huong Le Thi Thien <huongltt35@fpt.com> Co-authored-by: Nam Pham Dinh Thanh <nampdt@fpt.com> Co-authored-by: Vu Dam Tuan <vudt15@fpt.com> Co-authored-by: Hiep Ha Van <hiephv3@fpt.com> Co-authored-by: Lam Hoang Van <lamhv7@fpt.com> Reviewed-on: #7 Co-authored-by: Duy Le Huu <duylh19@fpt.com>
12 lines
593 B
Python
12 lines
593 B
Python
"""Characterization tests: pin the CURRENT behaviour of legacy code (R01-T04).
|
|
|
|
These are not specifications of what the code *should* do - they are a snapshot
|
|
of what it *does* today, written before the refactor so that any behavioural
|
|
drift introduced while moving logic into ``application/`` shows up as a failing
|
|
test rather than as a bug report from a user.
|
|
|
|
Rule for this folder: when a test here fails during the refactor, do not "fix"
|
|
the test first. Decide deliberately whether the behaviour change is intended,
|
|
and only then update the snapshot in the same commit as the change.
|
|
"""
|