Add Allure reports to Garnet Github

[darrenge]

Full test reporting using Allure (https://github.com/allure-framework).

See website here: http://10.159.0.74:8080/ Local to DarrenGe machine so expected to be slower than when released.

• Update Nightly GH action to use Allure for all tests
• Create base class for tests to use so Allure can categorize
• Make it so each test combination (Net8/Win22/Rel etc) counts as 1 test and not a series of retries
• Update easy tests to use base class (where quick and easy addition of base class)
• Save history to another branch so it can be kept to keep a test history (branch allure_data_history; folder:test/Allure/history).
• Set it up so allure_report is copied to web site (website/static/allure)
• Update readme on the front of Garnet Github site so it is a link next to BDN link
• Update tsav tests to Allure
• Update Garnet tests to Allure
• Update Cluster tests to Allure
• Clean up debug parts (history data, code etc)
• Remove all duplication - only show categorized (Allure web site "Suites" view shows duplicate results for custom grouping. One correct custom grouping and same test in default mode allure-framework/allure-csharp#638)
• Document Allure process in Teams Channel
• Document Allure on GH page so devs know how to have tests for Allure (update CI message with proper URL)
• Implement a pre CI that checks that all tests are Allure enabled
• History grows by 2-3 MB for each run. Look into truncation methods (will be in separate PR)

[Copilot]

Pull request overview

This pull request adds comprehensive Allure test reporting infrastructure to the Garnet project. Allure is a test reporting framework that provides visual test execution reports with history tracking and detailed categorization.

Key Changes:

• Integration of Allure reporting framework across all test projects
• Creation of AllureTestBase class for test categorization and environment labeling
• Updated CI/CD workflows to generate and publish Allure reports
• Documentation updates for developers on Allure test requirements

Reviewed changes

Copilot reviewed 163 out of 164 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
test/Garnet.test/AllureUtils.cs	New base class for Allure test infrastructure with environment labeling
Directory.Packages.props	Added Allure.Net.Commons and Allure.NUnit package dependencies
test/Garnet.test/*.cs	Updated 60+ test classes to inherit from AllureTestBase and add [AllureNUnit] attribute
.github/workflows/nightly.yml	Major refactoring to support Allure report generation, history tracking, and publishing
.github/workflows/ci.yml	Added Allure wiring verification to ensure all tests are properly configured
test/Allure/*.ps1	New PowerShell scripts for Allure data collection and report generation
website/docs/dev/onboarding.md	Added documentation requiring Allure-enabled tests for new features
README.md	Added badge linking to Allure test report

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[TalZaccai]

Added some minor comments. Please see why Tsavorite tests are failing...

[darrenge]

Added some minor comments. Please see why Tsavorite tests are failing...

Fixed

[Copilot]

Pull request overview

Copilot reviewed 162 out of 163 changed files in this pull request and generated 7 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.