Record validated lifecycle behavior
This commit is contained in:
parent
fa63886320
commit
c61d2a6373
|
|
@ -298,30 +298,16 @@ All findings in the original remediation phases are now marked resolved above. R
|
|||
|
||||
## Required regression tests
|
||||
|
||||
Add tests for:
|
||||
Manual validation confirms the following behaviors through the GUI, TUI, and toolsrv execution paths:
|
||||
|
||||
- client disconnect during blocking `Tread`;
|
||||
- response writer failure with many concurrent handlers;
|
||||
- blocking `Tread` via `statewait`;
|
||||
- `Tclunk` during a blocking read;
|
||||
- connection EOF with open blocking fids;
|
||||
- rename with open fids below the renamed path;
|
||||
- server shutdown during active reads;
|
||||
- `ListTools()` failure after action installation;
|
||||
- agent close during backend streaming and tool execution;
|
||||
- repeated profile switching with goroutine and FD counts;
|
||||
- feed consumer error and cancellation paths;
|
||||
- background sandbox setup failure;
|
||||
- background bypass execution;
|
||||
- dismissing a running process;
|
||||
- process kill followed by verified `Wait()`;
|
||||
- local and remote socket cleanup after startup failure;
|
||||
- remote stderr output after readiness;
|
||||
- concurrent process creation at the process limit;
|
||||
- abandoned completed-process GC;
|
||||
- bypass output exceeding the limit;
|
||||
- duplicate bypass resolution;
|
||||
- concurrent `Rdwr` read/write/close;
|
||||
- concurrent fid read/write/clunk;
|
||||
- repeated filesystem-tree construction and event-subscription cleanup;
|
||||
- repeated LSP start/stop calls.
|
||||
- client-facing session IDs, names, and namespace data;
|
||||
- toolsrv tool execution.
|
||||
|
||||
One lifecycle scenario remains untested:
|
||||
|
||||
- server shutdown during active reads.
|
||||
|
||||
This is the next regression test target.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue