Code coverage result is not accurate to real coverage in Xcode 7

Question

I am running test cases in application with enabled code coverage data Xcode 7 Beta 2. But I am able to get only few files coverage data while my all test cases are running successfully.

Some files has covered all codes by unit test cases but still showing 3% code coverage.

For example:

This is the result of code coverage, as you can see on the right side, there is an info how many times these lines of code was called during tests. In this case - 0.

But...

here is a place in tests where we can see that this function was called indeed. How many times? oh... at least once. This number is delivered by info on the right side.

So the code above should be marked as called, and not be grayed out:-)

Can anyone explain this? Why does this happen?

Answer 1

IT WORKS.

1. Since Apple released @testable keyword to import your project into test target, you don't have to add your files to both target anymore:

2. So just remove every file from your test target:

3. Wherever you need access to your file from your test target just import your target using: @testable import MyApp

4. Do this for every file in your project.

Then code coverage will be working fine.

Read more from Swift 2 + Xcode 7: Unit Testing Access Made Easy!!!!

If you need to know how to work with code coverage read How to use code coverage in Xcode 7?

As @Gerd Castan mentioned earlier is: "So it appears to me that a tested method shows a coverage of 0 when there exists at least one target where this method is not tested."

Solution is simple. Do not let compiler think that this file is included in more that one target, instead import your module using @testable keyword.