PerformanceBenchmarkReporter Versions Save

The Unity Performance Benchmark tool enables partners and developers to establish benchmark samples and measurements using the Performance Testing package, then use these benchmark values to compare subsequent performance test results in an html output utilizing graphical visualizations.

1.2.0

3 years ago

Updated .NET Core to 3.1 LTS and updated chart.js lib.

This version is compatible with Unity 2018.x and forward and works with the latest versions of the Unity Performance Testing extension package. This reporter is not longer versioned by branch per Unity version. Please use this master version only.

1.0.1

3 years ago

This release fixes an issue with the date type in the performance testing extension.

1.0.0

4 years ago

This release supports performance test result files generated up through the latest version of the Unity Performance Testing Extension package and includes support for Unity 2019.3. This was support had been requested and now works with this release. All previous versions of the reporter should now be replaced with this version, and the plan is to have all future versions release off the master branch.

2018.1_0.1.2

5 years ago
  1. Addresses a variety of scenarios presenting test configuration metadata across multiple result files. Result could contain all metadata, mismatched metadata, or missing metadata. Adding logic to handle several combinations of these scenarios to the user can see this
  2. Change default sorting order of results on x-axis of charts (and test configuration section) to sort ordinally on result file name. This allows user to affect desired sorting order of results by creating an alphabetic naming scheme with them.
  3. Moved test result/sample group selection logic out of reporter and into the TestRunMetadataProcessor (formerly MetadataValidator)

2018.2_0.1.2

5 years ago
  1. Addresses a variety of scenarios presenting test configuration metadata across multiple result files. Result could contain all metadata, mismatched metadata, or missing metadata. Adding logic to handle several combinations of these scenarios to the user can see this
  2. Change default sorting order of results on x-axis of charts (and test configuration section) to sort ordinally on result file name. This allows user to affect desired sorting order of results by creating an alphabetic naming scheme with them.
  3. Moved test result/sample group selection logic out of reporter and into the TestRunMetadataProcessor (formerly MetadataValidator)

2018.2_0.1.1

5 years ago

2018.1_0.1.1

5 years ago