test(Scss): fix variable check test

[ArgoZhang]

Link issues

fixes #6814

Summary By Copilot

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Fix SCSS variable unit test by aligning file paths, simplifying test helper injection, and correcting regex match conditions

Tests:

• Remove manual ITestOutputHelper field and constructor in VariableTest in favor of constructor parameter injection
• Update the SCSS variables file path to "wwwroot/scss/variables.scss"
• Replace matches.Any() with matches.Count != 0 to accurately detect regex matches

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR refactors the SCSS variable check unit test by updating the test class constructor for xUnit output injection, correcting the target SCSS file path, and standardizing regex match conditions.

File-Level Changes

Change	Details	Files
Refactor test class to use xUnit primary constructor injection	Removed private _outputHelper field and manual constructor Added ITestOutputHelper parameter in class signature	test/UniTest.Sass/VariableTest.cs
Fix SCSS variables file path	Updated variableFile path from bootstrapblazor.scss to variables.scss	test/UniTest.Sass/VariableTest.cs
Standardize regex match condition checks	Replaced matches.Any() with matches.Count != 0 in variable validation Replaced matches.Any() with matches.Count != 0 in mixin validation	test/UniTest.Sass/VariableTest.cs

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#6814	Fix the unit test for variable checking in the Scss-related test class.	✅
#6814	Improve code coverage for the Scss variable check functionality.	✅

Possibly linked issues

• #UserProvidedIssue: The PR directly fixes the SCSS variable check test by refactoring code, updating the variable file path, and improving checks, aligning with the issue's title.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[Copilot]

Pull Request Overview

This PR fixes a test file for Sass variable checking by modernizing the constructor pattern and correcting the file path reference used in the test.

• Updates constructor to use primary constructor syntax
• Corrects the variable file path from bootstrapblazor.scss to variables.scss
• Replaces .Any() calls with .Count != 0 for performance optimization

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The primary constructor parameter testOutputHelper is captured but never used in the class. Consider storing it in a field or property if it's needed for test output, or remove it if it's not required.

Suggested change

	public partial class VariableTest(ITestOutputHelper testOutputHelper)
	public partial class VariableTest

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (b2b7191) to head (05931b4).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #6815   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          739       739           
  Lines        31751     31751           
  Branches      4465      4465           
=========================================
  Hits         31751     31751           

Flag	Coverage Δ
BB	100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.