Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--source-files not working #501

Open
lfoster0 opened this issue Sep 17, 2021 · 10 comments
Open

--source-files not working #501

lfoster0 opened this issue Sep 17, 2021 · 10 comments

Comments

@lfoster0
Copy link

Hello I'm using Slather 2.7.1 and trying to generate coverage for a specific folder PROJECT_ROOT/Classes/Extensions/ but using --source-files to specify that folder or a specific file in the folder is not working. It generates the coverage report for the entire project each time.

Both of these examples generate coverage for the entire project even though I specify a single folder/file:
slather coverage -x --workspace Project.xcworkspace --scheme iOS --build-directory ./build --source-files "./Project/Classes/Extensions/*" Project.xcodeproj

slather coverage -x --workspace Project.xcworkspace --scheme iOS --build-directory ./build --source-files "./Project/Classes/Extensions/Array+Additions.swift" Project.xcodeproj

There is also this older issue that mentions --source-files is not working:

@lfoster0
Copy link
Author

Additionally running with --verbose doesn't show any errors or offer more insight

@mrbass21
Copy link

mrbass21 commented Nov 10, 2021

Seeing the same thing. I'm using it on a project that has a Tests/ folder and Sources/ folder. Trying to set the source files with the command line switch runs it for the whole project and our test files are showing up as coverage.

Running Slather 2.7.2.

@ykhandelwal913
Copy link

I am seeing the same thing. Anyone has a workaround to include other source/classes files?

@Morkrom
Copy link

Morkrom commented Nov 1, 2022

Observing the same behavior today. I'm also not clear: Assuming the source path is specified, and it's working as expected, would that negate the need to exclude other paths that aren't part of that source path ie pods, etc?

@mrdanb
Copy link

mrdanb commented Jan 5, 2023

I am also seeing the same issue in slather 2.7.3

@ObjectiveCesar
Copy link

Why is this still an issue?

@PowerOfCreation
Copy link

Can confirm, not working with 2.7.4

@jonduenas
Copy link

Anyone have any updates? Workarounds? Trying to ignore our third party dependencies but slather is not respecting this parameter.

@tichise
Copy link

tichise commented Jun 21, 2023

I have the same problem.

@j1nma
Copy link

j1nma commented Oct 26, 2023

Same thing!
🙏 an update or something

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants