[docs] Update glossary - daily scan

[Amaury Levé (Evangelink)]

AwesomeAssertions was bumped from 9.3.0 to 9.4.0 (PR #8008) and is the
mandated assertion library for this project's test suites. Adding a
glossary entry to explain its purpose and relationship to FluentAssertions.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[Copilot]

Pull request overview

Adds documentation to the glossary clarifying what AwesomeAssertions is and why it’s used in this repository’s test code, in response to the recent dependency bump.

Changes:

• Add a new glossary entry for AwesomeAssertions, including a brief description and a NuGet link.

Show a summary per file

File	Description
docs/glossary.md	Adds an “AwesomeAssertions” glossary entry explaining its role in the repo’s test assertions.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Summary

Workflow: PR Nitpick Reviewer
Date: 2026-05-11
Repository: microsoft/testfx

Key Findings

1. Important – Alphabetical ordering (docs/glossary.md, line 7): AwesomeAssertions is inserted before ArgumentArity, but alphabetically it belongs between ArgumentArity and AzureDevOpsReport.
2. Minor – Inconsistent backtick formatting (docs/glossary.md, line 9): FluentAssertions is backtick-formatted on its first mention but plain text on the second mention in the same sentence.

Positive Highlights

The entry itself is well-written and informative — it covers what the library is, its API style, its provenance as a FluentAssertions fork, and how its use is enforced via BannedSymbols.txt. Good addition to the glossary.

Recommendations

• Move the new ### AwesomeAssertions block to sit between ### ArgumentArity and ### AzureDevOpsReport in the ## A section.
• Make FluentAssertions consistently formatted (either always backtick-code or always plain) within the description paragraph.

---

Generated by PR Nitpick Reviewer

🔍 Meticulously inspected by PR Nitpick Reviewer 🔍

[Amaury Levé (Evangelink)]

AwesomeAssertions was bumped from 9.3.0 to 9.4.0 (PR #8008) and is the
mandated assertion library for this project's test suites. Adding a
glossary entry to explain its purpose and relationship to FluentAssertions.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[Copilot]

Pull request overview

Adds documentation to the glossary clarifying what AwesomeAssertions is and why it’s used in this repository’s test code, in response to the recent dependency bump.

Changes:

• Add a new glossary entry for AwesomeAssertions, including a brief description and a NuGet link.

Show a summary per file

File	Description
docs/glossary.md	Adds an “AwesomeAssertions” glossary entry explaining its role in the repo’s test assertions.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Summary

Workflow: PR Nitpick Reviewer
Date: 2026-05-11
Repository: microsoft/testfx

Key Findings

1. Important – Alphabetical ordering (docs/glossary.md, line 7): AwesomeAssertions is inserted before ArgumentArity, but alphabetically it belongs between ArgumentArity and AzureDevOpsReport.
2. Minor – Inconsistent backtick formatting (docs/glossary.md, line 9): FluentAssertions is backtick-formatted on its first mention but plain text on the second mention in the same sentence.

Positive Highlights

The entry itself is well-written and informative — it covers what the library is, its API style, its provenance as a FluentAssertions fork, and how its use is enforced via BannedSymbols.txt. Good addition to the glossary.

Recommendations

• Move the new ### AwesomeAssertions block to sit between ### ArgumentArity and ### AzureDevOpsReport in the ## A section.
• Make FluentAssertions consistently formatted (either always backtick-code or always plain) within the description paragraph.

---

Generated by PR Nitpick Reviewer

🔍 Meticulously inspected by PR Nitpick Reviewer 🔍

[Amaury Levé (Evangelink)]

AwesomeAssertions was bumped from 9.3.0 to 9.4.0 (PR #8008) and is the
mandated assertion library for this project's test suites. Adding a
glossary entry to explain its purpose and relationship to FluentAssertions.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[Copilot]

Pull request overview

Adds documentation to the glossary clarifying what AwesomeAssertions is and why it’s used in this repository’s test code, in response to the recent dependency bump.

Changes:

• Add a new glossary entry for AwesomeAssertions, including a brief description and a NuGet link.

Show a summary per file

File	Description
docs/glossary.md	Adds an “AwesomeAssertions” glossary entry explaining its role in the repo’s test assertions.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Summary

Workflow: PR Nitpick Reviewer
Date: 2026-05-11
Repository: microsoft/testfx

Key Findings

1. Important – Alphabetical ordering (docs/glossary.md, line 7): AwesomeAssertions is inserted before ArgumentArity, but alphabetically it belongs between ArgumentArity and AzureDevOpsReport.
2. Minor – Inconsistent backtick formatting (docs/glossary.md, line 9): FluentAssertions is backtick-formatted on its first mention but plain text on the second mention in the same sentence.

Positive Highlights

The entry itself is well-written and informative — it covers what the library is, its API style, its provenance as a FluentAssertions fork, and how its use is enforced via BannedSymbols.txt. Good addition to the glossary.

Recommendations

• Move the new ### AwesomeAssertions block to sit between ### ArgumentArity and ### AzureDevOpsReport in the ## A section.
• Make FluentAssertions consistently formatted (either always backtick-code or always plain) within the description paragraph.

---

Generated by PR Nitpick Reviewer

🔍 Meticulously inspected by PR Nitpick Reviewer 🔍

[Amaury Levé (Evangelink)]

AwesomeAssertions was bumped from 9.3.0 to 9.4.0 (PR #8008) and is the
mandated assertion library for this project's test suites. Adding a
glossary entry to explain its purpose and relationship to FluentAssertions.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[Copilot]

Pull request overview

Adds documentation to the glossary clarifying what AwesomeAssertions is and why it’s used in this repository’s test code, in response to the recent dependency bump.

Changes:

• Add a new glossary entry for AwesomeAssertions, including a brief description and a NuGet link.

Show a summary per file

File	Description
docs/glossary.md	Adds an “AwesomeAssertions” glossary entry explaining its role in the repo’s test assertions.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Summary

Workflow: PR Nitpick Reviewer
Date: 2026-05-11
Repository: microsoft/testfx

Key Findings

1. Important – Alphabetical ordering (docs/glossary.md, line 7): AwesomeAssertions is inserted before ArgumentArity, but alphabetically it belongs between ArgumentArity and AzureDevOpsReport.
2. Minor – Inconsistent backtick formatting (docs/glossary.md, line 9): FluentAssertions is backtick-formatted on its first mention but plain text on the second mention in the same sentence.

Positive Highlights

The entry itself is well-written and informative — it covers what the library is, its API style, its provenance as a FluentAssertions fork, and how its use is enforced via BannedSymbols.txt. Good addition to the glossary.

Recommendations

• Move the new ### AwesomeAssertions block to sit between ### ArgumentArity and ### AzureDevOpsReport in the ## A section.
• Make FluentAssertions consistently formatted (either always backtick-code or always plain) within the description paragraph.

---

Generated by PR Nitpick Reviewer

🔍 Meticulously inspected by PR Nitpick Reviewer 🔍

[Amaury Levé (Evangelink)]

AwesomeAssertions was bumped from 9.3.0 to 9.4.0 (PR #8008) and is the
mandated assertion library for this project's test suites. Adding a
glossary entry to explain its purpose and relationship to FluentAssertions.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[Copilot]

Pull request overview

Adds documentation to the glossary clarifying what AwesomeAssertions is and why it’s used in this repository’s test code, in response to the recent dependency bump.

Changes:

• Add a new glossary entry for AwesomeAssertions, including a brief description and a NuGet link.

Show a summary per file

File	Description
docs/glossary.md	Adds an “AwesomeAssertions” glossary entry explaining its role in the repo’s test assertions.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Summary

Workflow: PR Nitpick Reviewer
Date: 2026-05-11
Repository: microsoft/testfx

Key Findings

1. Important – Alphabetical ordering (docs/glossary.md, line 7): AwesomeAssertions is inserted before ArgumentArity, but alphabetically it belongs between ArgumentArity and AzureDevOpsReport.
2. Minor – Inconsistent backtick formatting (docs/glossary.md, line 9): FluentAssertions is backtick-formatted on its first mention but plain text on the second mention in the same sentence.

Positive Highlights

The entry itself is well-written and informative — it covers what the library is, its API style, its provenance as a FluentAssertions fork, and how its use is enforced via BannedSymbols.txt. Good addition to the glossary.

Recommendations

• Move the new ### AwesomeAssertions block to sit between ### ArgumentArity and ### AzureDevOpsReport in the ## A section.
• Make FluentAssertions consistently formatted (either always backtick-code or always plain) within the description paragraph.

---

Generated by PR Nitpick Reviewer

🔍 Meticulously inspected by PR Nitpick Reviewer 🔍

[Amaury Levé (Evangelink)]

AwesomeAssertions was bumped from 9.3.0 to 9.4.0 (PR #8008) and is the
mandated assertion library for this project's test suites. Adding a
glossary entry to explain its purpose and relationship to FluentAssertions.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[Copilot]

Pull request overview

Adds documentation to the glossary clarifying what AwesomeAssertions is and why it’s used in this repository’s test code, in response to the recent dependency bump.

Changes:

• Add a new glossary entry for AwesomeAssertions, including a brief description and a NuGet link.

Show a summary per file

File	Description
docs/glossary.md	Adds an “AwesomeAssertions” glossary entry explaining its role in the repo’s test assertions.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Summary

Workflow: PR Nitpick Reviewer
Date: 2026-05-11
Repository: microsoft/testfx

Key Findings

1. Important – Alphabetical ordering (docs/glossary.md, line 7): AwesomeAssertions is inserted before ArgumentArity, but alphabetically it belongs between ArgumentArity and AzureDevOpsReport.
2. Minor – Inconsistent backtick formatting (docs/glossary.md, line 9): FluentAssertions is backtick-formatted on its first mention but plain text on the second mention in the same sentence.

Positive Highlights

The entry itself is well-written and informative — it covers what the library is, its API style, its provenance as a FluentAssertions fork, and how its use is enforced via BannedSymbols.txt. Good addition to the glossary.

Recommendations

• Move the new ### AwesomeAssertions block to sit between ### ArgumentArity and ### AzureDevOpsReport in the ## A section.
• Make FluentAssertions consistently formatted (either always backtick-code or always plain) within the description paragraph.

---

Generated by PR Nitpick Reviewer

🔍 Meticulously inspected by PR Nitpick Reviewer 🔍

[Amaury Levé (Evangelink)]

AwesomeAssertions was bumped from 9.3.0 to 9.4.0 (PR #8008) and is the
mandated assertion library for this project's test suites. Adding a
glossary entry to explain its purpose and relationship to FluentAssertions.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[Copilot]

Pull request overview

Adds documentation to the glossary clarifying what AwesomeAssertions is and why it’s used in this repository’s test code, in response to the recent dependency bump.

Changes:

• Add a new glossary entry for AwesomeAssertions, including a brief description and a NuGet link.

Show a summary per file

File	Description
docs/glossary.md	Adds an “AwesomeAssertions” glossary entry explaining its role in the repo’s test assertions.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Summary

Workflow: PR Nitpick Reviewer
Date: 2026-05-11
Repository: microsoft/testfx

Key Findings

1. Important – Alphabetical ordering (docs/glossary.md, line 7): AwesomeAssertions is inserted before ArgumentArity, but alphabetically it belongs between ArgumentArity and AzureDevOpsReport.
2. Minor – Inconsistent backtick formatting (docs/glossary.md, line 9): FluentAssertions is backtick-formatted on its first mention but plain text on the second mention in the same sentence.

Positive Highlights

The entry itself is well-written and informative — it covers what the library is, its API style, its provenance as a FluentAssertions fork, and how its use is enforced via BannedSymbols.txt. Good addition to the glossary.

Recommendations

• Move the new ### AwesomeAssertions block to sit between ### ArgumentArity and ### AzureDevOpsReport in the ## A section.
• Make FluentAssertions consistently formatted (either always backtick-code or always plain) within the description paragraph.

---

Generated by PR Nitpick Reviewer

🔍 Meticulously inspected by PR Nitpick Reviewer 🔍

[Amaury Levé (Evangelink)]

AwesomeAssertions was bumped from 9.3.0 to 9.4.0 (PR #8008) and is the
mandated assertion library for this project's test suites. Adding a
glossary entry to explain its purpose and relationship to FluentAssertions.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[Copilot]

Pull request overview

Adds documentation to the glossary clarifying what AwesomeAssertions is and why it’s used in this repository’s test code, in response to the recent dependency bump.

Changes:

• Add a new glossary entry for AwesomeAssertions, including a brief description and a NuGet link.

Show a summary per file

File	Description
docs/glossary.md	Adds an “AwesomeAssertions” glossary entry explaining its role in the repo’s test assertions.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1

[Amaury Levé (Evangelink)]

Summary

Workflow: PR Nitpick Reviewer
Date: 2026-05-11
Repository: microsoft/testfx

Key Findings

1. Important – Alphabetical ordering (docs/glossary.md, line 7): AwesomeAssertions is inserted before ArgumentArity, but alphabetically it belongs between ArgumentArity and AzureDevOpsReport.
2. Minor – Inconsistent backtick formatting (docs/glossary.md, line 9): FluentAssertions is backtick-formatted on its first mention but plain text on the second mention in the same sentence.

Positive Highlights

The entry itself is well-written and informative — it covers what the library is, its API style, its provenance as a FluentAssertions fork, and how its use is enforced via BannedSymbols.txt. Good addition to the glossary.

Recommendations

• Move the new ### AwesomeAssertions block to sit between ### ArgumentArity and ### AzureDevOpsReport in the ## A section.
• Make FluentAssertions consistently formatted (either always backtick-code or always plain) within the description paragraph.

---

Generated by PR Nitpick Reviewer

🔍 Meticulously inspected by PR Nitpick Reviewer 🔍