You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document explains the enhanced test reporting capabilities that have been added to the GitHub Actions workflow.
4
+
5
+
## Overview
6
+
7
+
The GitHub Actions workflow has been enhanced to provide detailed, individual test results for all test suites in the Workflow Core project. This addresses the requirement to see detailed, individual test results from tests run by GitHub workflows.
8
+
9
+
## Key Enhancements
10
+
11
+
### 1. Detailed Test Output
12
+
-**Enhanced Verbosity**: Changed from `--verbosity normal` to `--verbosity detailed`
13
+
-**Detailed Console Logging**: Added `--logger "console;verbosity=detailed"` for comprehensive console output
14
+
-**Individual Test Results**: Each test case now shows its execution status, duration, and any error details
15
+
16
+
### 2. TRX Test Result Files
17
+
-**TRX Format**: Added `--logger "trx;LogFileName={TestSuite}.trx"` to generate XML test result files
18
+
-**Structured Data**: TRX files contain structured test data including:
19
+
- Test names and fully qualified names
20
+
- Test outcomes (Passed, Failed, Skipped)
21
+
- Execution times and durations
22
+
- Error messages and stack traces for failed tests
23
+
- Test categories and traits
24
+
25
+
### 3. GitHub Actions Test Reporting
26
+
-**Test Reporter Integration**: Added `dorny/test-reporter@v1` action to display test results in the GitHub UI
27
+
-**PR Integration**: Test results are automatically displayed in pull request checks
28
+
-**Visual Test Summary**: Failed tests are highlighted with detailed error information
29
+
-**Test Status Annotations**: Test results appear as GitHub Actions annotations
30
+
31
+
### 4. Test Result Artifacts
32
+
-**Downloadable Results**: Test result files are uploaded as artifacts for each job
33
+
-**Persistent Storage**: Test results are available for download even after workflow completion
34
+
-**Individual Job Results**: Each test suite (Unit, Integration, MongoDB, etc.) has separate artifacts
35
+
36
+
## What You'll See
37
+
38
+
### In GitHub Actions Logs
39
+
Before (old format):
40
+
```
41
+
Starting test execution, please wait...
42
+
A total of 1 test files matched the specified pattern.
at WorkflowCore.UnitTests.Services.SomeTest.example_failing_test() in /path/to/test.cs:line 42
60
+
61
+
Test Run Summary:
62
+
Total tests: 25
63
+
Passed: 24
64
+
Failed: 1
65
+
Skipped: 0
66
+
```
67
+
68
+
### In GitHub Pull Requests
69
+
- ✅ **Test Status Checks**: Clear pass/fail status for each test suite
70
+
- 📊 **Test Summary**: Number of passed, failed, and skipped tests
71
+
- 🔍 **Detailed Failure Information**: Click-through to see specific test failures
72
+
- 📁 **Downloadable Artifacts**: Access to complete test result files
73
+
74
+
### Available Artifacts
75
+
Each test job now produces downloadable artifacts:
76
+
-`unit-test-results`: Unit test TRX files and logs
77
+
-`integration-test-results`: Integration test TRX files and logs
78
+
-`mongodb-test-results`: MongoDB-specific test results
79
+
-`mysql-test-results`: MySQL-specific test results
80
+
-`postgresql-test-results`: PostgreSQL-specific test results
81
+
-`redis-test-results`: Redis-specific test results
82
+
-`sqlserver-test-results`: SQL Server-specific test results
83
+
-`elasticsearch-test-results`: Elasticsearch-specific test results
84
+
-`oracle-test-results`: Oracle-specific test results
85
+
86
+
## Benefits
87
+
88
+
1.**Individual Test Visibility**: See exactly which tests pass or fail
89
+
2.**Debugging Support**: Detailed error messages and stack traces
90
+
3.**Performance Monitoring**: Test execution times for performance analysis
91
+
4.**Historical Data**: Downloadable test results for trend analysis
92
+
5.**CI/CD Integration**: Better integration with GitHub's native test reporting features
93
+
6.**Developer Experience**: Faster identification of test issues in pull requests
94
+
95
+
## File Structure
96
+
97
+
After test execution, the following files are generated:
98
+
```
99
+
test-results/
100
+
├── UnitTests.trx
101
+
├── IntegrationTests.trx
102
+
├── MongoDBTests.trx
103
+
├── MySQLTests.trx
104
+
├── PostgreSQLTests.trx
105
+
├── RedisTests.trx
106
+
├── SQLServerTests.trx
107
+
├── ElasticsearchTests.trx
108
+
└── OracleTests.trx
109
+
```
110
+
111
+
Each TRX file contains detailed XML data about the test execution results that can be consumed by various reporting tools and integrated development environments.
0 commit comments