lei.chen/myxce
1
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

test(xce-test-rc-file): task 3.2 end-to-end rc-file failure handling

Browse source 
Extends test_rcfile_integration.sh with 2 scenarios proving Requirements
3.1-3.4: a failing rc-file command in piped/scripted mode aborts before
any of the piped script's own commands run, exiting nonzero; the same
failing command in an interactive session still reports the failure,
continues executing the rc file's remaining lines, and reaches the normal
prompt -- while still carrying the session's sticky nonzero exit-code
verdict (g_session_failed is never cleared, matching how any other
failing-command-then-quit interactive session already behaves).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AgYRU3zDTqNGV5Jk8aiKLg
This commit is contained in:
Rongsong Shen 2026-08-26 16:57:09 +00:00
parent d258aa3d91
commit 19bc819204
No known key found for this signature in database
GPG key ID: 5BCDAAE0123E9FE2
2 changed files with 97 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.kiro/specs/xce-test-rc-file/tasks.md
View file

@ -40,7 +40,7 @@
- _Requirements: 1.1, 1.2, 1.4, 1.5, 2.1, 2.3_
- _Depends: 2.2_
- [ ] 3.2 Verify rc-file failure handling matches the session's existing abort/continue behavior end-to-end
- [x] 3.2 Verify rc-file failure handling matches the session's existing abort/continue behavior end-to-end
- Scenario: a failing rc-file command in scripted/piped mode aborts before any of the piped script's own commands run, and the process exits with a failure status
- Scenario: the same failing rc-file command in an interactive session still reaches the normal prompt afterward
- Observable: an integration test run demonstrates both scenarios pass against the real built binary