Skip to content

Commit 5d06794

Browse files
committed
adds two new posts, links to new tools
1 parent 803583a commit 5d06794

3 files changed

Lines changed: 71 additions & 0 deletions

File tree

_data/navigation.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@
1616
link: /AdoPipelineView/
1717
- name : Azure Policy Conditions Viewer
1818
link: /ArmJsonOsTargetingConditionParser/
19+
- name : nUnit Test Viewer
20+
link: /NUnitTestViewer/
1921
- name: Series
2022
dropdown:
2123
- name: Learn PowerShell

_posts/2025-10-27-ado-tip---performing-quality-checks-only-on-changed-files! renamed to _posts/2025-10-27-ado-tip performing-quality-checks-only-on-changed-files.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,14 @@ It was very easy to get the list of files I cared about, the interesting thing w
6262

6363
This will give you a list, in linux file format, of all files that changed in your commits/pr versus master.
6464

65+
This actually failed aggresively, as it turns out that ADO pipelines will by default only include the dev branch and won't mirror master as well. I added this to fix that particular issue.
66+
67+
```
68+
git fetch origin master
69+
$changedFiles = git diff --name-only master
70+
```
71+
72+
6573
From here, it was simple enough to compare `$allJsonFiles` against the list back from `$allChangedFiles` and filter things down. I then ended the `BeforeDiscovery` block of my test by publishing `$myChangedJsonFiles`.
6674

6775
Next up, it's very easy to hand a list of resources off to a `Describe` block and iterate over them, using this syntax:
Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
title: "New Tool – nUnit Test Results Viewer"
3+
date: "2025-10-27"
4+
redirect_from: /new-tools-nunit-test-viewer
5+
coverImage: \assets\images\2025\pipelineViewHeader.png
6+
categories:
7+
- "programming"
8+
- "tools"
9+
- "testing"
10+
tags:
11+
- "nUnit"
12+
- "Testing"
13+
- "XML"
14+
- "SPA"
15+
- "DevOps"
16+
excerpt: "Tired of trying to parse nUnit XML test results by hand? This new single-page application renders your test results in a clean, pipeline-style view that makes it easy to understand your test outcomes at a glance."
17+
fileName: '2025-10-27-new-tool-released-nUnit-viewer.md'
18+
---
19+
20+
![](../assets/images/2025/pipelineViewHeader.png)
21+
Ever find yourself staring at a massive nUnit XML test results file, trying to figure out which tests passed, failed, or were skipped? Ever wish you could see your test results in the same clean, organized view you get when running tests in an Azure DevOps pipeline?
22+
23+
If you're like me, you've probably opened those XML files in a text editor more times than you'd care to admit, scrolling through endless `<test-case>` elements, trying to make sense of the results. There has to be a better way!
24+
25+
Well, now there is.
26+
27+
## Introducing: **nUnit Test Results Viewer** 🎉
28+
29+
This single-page application takes your nUnit XML test results and renders them in a beautiful, pipeline-style view that makes it easy to understand your test outcomes at a glance.
30+
31+
![nUnit Test Results in a clean, organized view](<../assets/images/2025/pipelineView.png>)
32+
33+
No more squinting at raw XML trying to count passed vs failed tests, or hunting through massive files to find that one test that's been causing issues.
34+
35+
Think of it as "Azure DevOps Test Results tab," except it works with any nUnit XML file and runs entirely in your browser.
36+
37+
### Features
38+
- **Pipeline-style test visualization** - See your test results organized just like in Azure DevOps
39+
- **Test summary dashboard** - Get an instant overview of passed, failed, and skipped tests
40+
- **Expandable test details** - Click into individual tests to see failure messages and stack traces
41+
- **Search and filter** - Quickly find specific tests or filter by status
42+
- **Runs entirely in your browser** - No installs, no servers, no hassle
43+
- **Complete privacy** - Your test results never leave your browser
44+
45+
46+
### How to Use It
47+
Simply upload your nUnit XML results file or paste the XML content directly into the viewer. The app will parse your test results and display them in an organized, easy-to-read format that mimics the test results view you're familiar with from Azure DevOps pipelines.
48+
49+
### It's Completely Private!
50+
There's no telemetry, monitoring, or data collection of any kind. Your test results stay completely within your browser tab - nothing is ever sent to a server or stored anywhere.
51+
52+
### Perfect for:
53+
- **Local development** - Quickly review test results from your local test runs
54+
- **CI/CD troubleshooting** - Download XML results from failed builds and analyze them locally
55+
- **Test result archiving** - Keep historical test results viewable in a user-friendly format
56+
- **Team collaboration** - Share test results in a format that's actually readable
57+
58+
If you've ever spent way too long trying to parse XML test results by hand, this tool will save your sanity (and probably some time too).
59+
60+
Give it a try here: **[nUnit Test Results Viewer](https://www.foxdeploy.com/NUnitTestViewer/)**
61+
And if you find any bugs, well... at least now you'll have a nice way to view the test results when you fix them! 😉

0 commit comments

Comments
 (0)