Cannot get unit tests stats due to missing test logs either in derived data or result bundle path about xclogparser HOT 7 OPEN

Hi Daniel!
I tried Xcode 12.4 behaviour for a brand new project and .xcactivitylog files are placed in the derived data.

To customize that dir, you can append -derivedDataPath, like

xcodebuild test -scheme Demo -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 11 Pro,OS=14.4' -resultBundlePath ~/Demo/result -derivedDataPath ~/Demo/DerivedData

and the loot at ~/Demo/DerivedData/{{Project}}/Logs/Build/.

If you call xcodebuild test and your DerivedData contains all products required for the test, indeed the *.xcactivitylog is in a lightweight format. To get a full build log, please try calling xcodebuild clean test... or xcodebuild clean build-for-testing ...

from xclogparser.

Hey Bartosz! Thank you for the response.

I prepared a vanilla Swift iOS app project, cleaned up the derived data and run xcodebuild clean test ..., but still no unit tests coverage information from a parse command (I tired different reporters).

Below some screenshots how the output looks like:

Could you please provide your steps in order to get the unit tests coverage report via xclogparser? 🙏

from xclogparser.

XCLogParser can capture building logs (compilation steps, errors, warnings etc.) but not unit tests results like code coverage. When you run tests in Xcode or xcodebuild the only generated .xcactivitylog file contains a summary of all steps in the build-for-testing phase (you have it generated in the Build dir).

from xclogparser.

XCLogParser can capture building logs (compilation steps, errors, warnings etc.) but not unit tests results like code coverage.

That's interesting. According to the README file:

XCLogParser can give a lot of insights in regards to build times for every module and file in your project, warnings, errors and unit tests results.

Apparently, I miss-understood "unit tests results" phrase then. Maybe we could avoid ambiguity and tweak the documentation to clearly point out what type of unit tests results are available? 😊

from xclogparser.

@ecamacho, do you remember what did we mean by "rests results" in a Readme file?

from xclogparser.

bump on this - I was also under the impression xclogparser can parse unit tests results or maybe XCLogParser expect xcodebuild test generate a .xcactivitylog file at some point? and the newwer Xcode no longer does that?

from xclogparser.

@ecamacho Do you have any knowledge about this issue? Thanks

from xclogparser.