Merge official 2026 5 to master

[ravirk91]

Description

Type of Change

• Bug fix - [ ] New feature - [ ] Breaking change - [ ] Plugin update

Checklist

• PR description clearly describes the changes
• Target branch is correct (master for features, Releases/* for fixes)
• Latest code from target branch merged
• No commented/junk code included
• No new build warnings or errors
• All existing unit tests pass
• New unit tests added for new functionality
• Cross-platform compatibility verified (Windows/Linux/macOS)
• CI/CD pipeline passes
• Code follows project conventions (Act{Platform}{Type}, {Platform}Driver)
• Repository objects use [IsSerializedForLocalRepository] where needed
• Error handling uses Reporter.ToLog() pattern
• Documentation updated for user-facing changes
• Self-review completed and code review comments addressed

Summary by CodeRabbit

Release Notes

• New Features

  • Added a "Full Page Screenshot" checkbox option to the visual testing interface for more granular control over baseline and checkpoint comparisons.

• Behavior Changes

  • Full-page screenshot feature now defaults to disabled for visual testing actions.

• Chores

  • Updated version to 26.5.0.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: cca2bc4b-9b5b-4cfc-9c14-6d981dc6c637

📥 Commits

Reviewing files that changed from the base of the PR and between 049b738 and 4cddb35.

📒 Files selected for processing (5)

• Ginger/Ginger/Actions/ActionEditPages/VisualTesting/VRTComparePage.xaml
• Ginger/Ginger/Actions/ActionEditPages/VisualTesting/VRTComparePage.xaml.cs
• Ginger/Ginger/Drivers/DriversConfigsEditPages/UFTCredentialsDialog.xaml
• Ginger/GingerCoreCommon/GingerCoreCommon.csproj
• Ginger/GingerCoreNET/ActionsLib/UI/VisualTesting/ActVisualTesting.cs

---

Walkthrough

This PR adds a full-page screenshot feature to the Visual Testing page with conditional visibility rules, updates the default property value for IsFullPageScreenshot from true to false, and includes routine version maintenance and minor formatting fixes.

Changes

Full-Page Screenshot Feature

Layer / File(s)	Summary
XAML layout and checkbox binding Ginger/Ginger/Actions/ActionEditPages/VisualTesting/VRTComparePage.xaml, VRTComparePage.xaml.cs	Grid row structure expands with new RowDefinition; full-page screenshot label and checkbox inserted; preview and note sections repositioned. Checkbox binds to mAct.IsFullPageScreenshot.
Visibility rules by VRT action type VRTComparePage.xaml.cs	Full-page screenshot controls hidden for Start and Stop actions. For Track action: when baseline creation is checked, controls show only with ActiveWindow baseline and Window action scope; when baseline creation unchecked, controls show only with Window action scope.
IsFullPageScreenshot default value Ginger/GingerCoreNET/ActionsLib/UI/VisualTesting/ActVisualTesting.cs	Property default fallback changes from true to false when bool.TryParse fails or parameter is absent.

Maintenance Updates

Layer / File(s)	Summary
Version bump and XAML formatting Ginger/GingerCoreCommon/GingerCoreCommon.csproj, Ginger/Ginger/Drivers/DriversConfigsEditPages/UFTCredentialsDialog.xaml	Project version incremented from 26.4.0.0 to 26.5.0.0 (AssemblyVersion, FileVersion, NuGet Version). UFTCredentialsDialog XAML indentation adjusted for closing tags in Apps tab (no functional change).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Ginger-Automation/Ginger#4492: Directly overlaps with full-page screenshot checkbox binding/visibility logic and IsFullPageScreenshot property default changes.

Suggested reviewers

• Maheshkale447

Poem

🐰 A screenshot springs up, full and wide,
With checkboxes dancing, visibility guide.
Windows and baselines in sweet accord,
While versions tick upward, a release restored! 📸✨

🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (2 warnings, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is incomplete—it contains only the template with empty sections and no actual description of changes, though the PR objectives reveal substantial changes across multiple areas.	Fill in the Description section with a clear summary of major changes (Android TV support, .NET 10 upgrade, security fixes, etc.) and check appropriate Type of Change boxes.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The PR title 'Merge official 2026 5 to master' is vague and lacks specificity about what 'official 2026 5' represents or what changes are included.	Consider using a more descriptive title that clarifies the scope, such as 'Release 2026.5: Add Android TV support and upgrade to .NET 10' or similar.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch Merge-official-2026-5-to-master

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}