starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[PR #13316] Extend test coverage of TestDbcsWriteRead #29473

New Issue
Open
opened 2026-01-31 09:35:08 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:35:08 +00:00
Owner
Copy Link

Original Pull Request: https://github.com/microsoft/terminal/pull/13316

State: closed
Merged: Yes

TestDbcsWriteRead failed to properly test all text input scenarios.
In order to write wide characters with CHAR_INFO structs using the W APIs
one must still repeat the CHAR_INFO twice, once with COMMON_LVB_LEADING_BYTE
and once with COMMON_LVB_TRAILING_BYTE set in the attributes. This is because
CHAR_INFO APIs are column oriented. TestDbcsWriteRead on the other hand
only tested the scenario of sending wide characters without those flags.

This commit fixes the problem by introducing a UnicodeDoubled mode and
increases the number of test patterns from 14 to 17. Due to the existing
code having been written with the false assumption in mind, a simpler
modification resulted in +1100 LOC. As such I opted to rewrite the code instead
and replaced the potentially buggy output generators with static arrays.

Code page 437 tests were removed, as it contains no DBCS characters anyways.

This is preliminary work for #8000.

**Original Pull Request:** https://github.com/microsoft/terminal/pull/13316 **State:** closed **Merged:** Yes --- `TestDbcsWriteRead` failed to properly test all text input scenarios. In order to write wide characters with `CHAR_INFO` structs using the `W` APIs one must still repeat the `CHAR_INFO` twice, once with `COMMON_LVB_LEADING_BYTE` and once with `COMMON_LVB_TRAILING_BYTE` set in the attributes. This is because `CHAR_INFO` APIs are column oriented. `TestDbcsWriteRead` on the other hand only tested the scenario of sending wide characters without those flags. This commit fixes the problem by introducing a `UnicodeDoubled` mode and increases the number of test patterns from 14 to 17. Due to the existing code having been written with the false assumption in mind, a simpler modification resulted in +1100 LOC. As such I opted to rewrite the code instead and replaced the potentially buggy output generators with static arrays. Code page 437 tests were removed, as it contains no DBCS characters anyways. This is preliminary work for #8000.
claunia added the pull-request label 2026-01-31 09:35:08 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#29473
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?