Migrate unit tests to DataRow pattern

[Copilot]

Description

Migrated unit tests to use [DataRow] attributes following the pattern established in PR #186. This eliminates test data classes and foreach loops in favor of parameterized test methods, making tests cleaner and more maintainable.

NFUnitTestSystemLib (9 files) - Migrated Equals() tests for all primitive numeric types:

• Replaced TestData helper classes with [DataRow] attributes
• Split type-mismatch edge cases (null, string, int) into separate test methods
• Applied to: Byte, SByte, Int16, Int32, Int64, UInt16, UInt32, UInt64, Boolean

NFUnitTestBitConverter - Migrated 4 GetBytes* test methods:

• GetBytesBool, GetBytesChar, GetBytesInt16, GetBytesInt32
• Extracted min/max value tests into separate methods where applicable

Motivation and Context

Addressing nanoframework/Home#1159.

Following the pattern established in PR #186 to keep the code clean and allow for easier addition of new test cases in the future.

How Has This Been Tested?

• Code review completed with no issues
• CodeQL security scan passed with no alerts
• All migrations follow the established pattern from PR Migrate Unit Tests to use DataRow #186

Screenshots

N/A - No UI changes

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue with code or algorithm)
• New feature (non-breaking change which adds functionality to code)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)
• Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• My code follows the code style of this project (only if there are changes in source code).
• My changes require an update to the documentation (there are changes that require the docs website to be updated).
• I have updated the documentation accordingly (the changes require an update on the docs in this repo).
• I have read the CONTRIBUTING document.
• I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
• I have added new tests to cover my changes.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Migrate Unit Tests to DataRow</issue_title>
<issue_description>### Details about Problem

nanoFramework area: ( CoreLibrary)

Description

To keep the code clean we should migrate nanoframework/CoreLibrary Unit Tests to use DataRow. In a future it will allow us to add more test cases to each method.
Please check this #186 PR for reference.

</issue_description>

<agent_instructions>Make sure to use PR template on the repo and fill in relevant sections. Only tick check lists, don't delete them.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Migrate Unit Tests to DataRow Home#1159

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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

[josesimoes]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[josesimoes]

@copilot Make sure to use PR template on the repo and fill in relevant sections. Only tick check lists, don't delete them.

[Copilot]

@copilot Make sure to use PR template on the repo and fill in relevant sections. Only tick check lists, don't delete them.

Updated the PR description to follow the template format with all required sections and checklists.

[josesimoes]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[josesimoes]

LGTM

[nfbot]

Hi @Copilot,

😯 I'm afraid you'll have to use the PR template like the rest of us...
Make sure you've used the template and have include all the required information and fill in the appropriate details. After doing that feel free to reopen the PR. If you have questions we are here to help..

[josesimoes]

@copilot some of the new tests are not correctly implemented. Follow my fixes in commit d41914b and reproduce on the other ones you've added.

[Copilot]

@copilot some of the new tests are not correctly implemented. Follow my fixes in commit d41914b and reproduce on the other ones you've added.

Applied the same assertion pattern from commit d41914b to all numeric type tests (SByte, Int16, Int32, Int64, UInt16, UInt32, UInt64) in commit 880b0ce. Changes include:

• Using Assert.AreEqual/Assert.AreNotEqual instead of Assert.AreEqual(expected, ...)
• Using Assert.IsTrue/Assert.IsFalse for hash code comparisons
• Removing error messages from assertions
• Adding blank lines for formatting

[josesimoes]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[josesimoes]

LGTM

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud