Search Issue Tracker
Fixed in 1.1.0, 1.0.1
Votes
0
Found in [Package]
1.1.0
Issue ID
1344868
Regression
No
[macOS] Code Coverage commands are not found when running Editor in batchmode and providing commands via Terminal
How to reproduce:
1. Extract the attached project
2. Open the Terminal
3. Enter the following command:
<path-to-Unity>Unity.app/Contents/MacOS/Unity -projectPath <path-to-project> -batchmode -runTests -testResults Results.xml -testPlatform playmode -enableCodeCoverage -coverageResultsPath CodeCoverageResults -debugCodeOptimization -coverageOptions generateAdditionalMetrics;generateHtmlReport;generateHtmlReportHistory;generateBadgeReport;assemblyFilters:+Unity.CodeCoverage.*
Expected result: All provided commands run successfully
Actual result: 'generateHtmlReport', 'generateHtmlReportHistory', 'generateBadgeReport', 'assemblyFilters:+Unity.CodeCoverage.*' commands are not found
Reproducible with: 1.1.0 (2019.4.28f1, 2020.3.13f1, 2021.1.13f1, 2021.2.0b1)
Note:
- Commands are recognized on a Windows system
Resolution Notes:
This behaviour is expected. In bash, semicolon is used to separate commands. As a result, running command from description will actually try to run 5 separate commands. To fix this - surround coverageOptions with double quotes. Code Coverage package documentation has been updated with examples that work with MacOS.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 1.1.0, 1.0.1):
This behaviour is expected. In bash, semicolon is used to separate commands. As a result, running command from description will actually try to run 5 separate commands. To fix this - surround coverageOptions with double quotes. We will update Code Coverage package documentation with examples that work with MacOS.