Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Clover Lambda Expression Coverage

özhan May 8, 2014

Hi,

As far as i know clover support Java 8.

I am trying to very simple test case but clover couldnt show the coverage for the whole file.

If i remove the forEach lambda block, coverage works fine.

Should i need configure the clover for extra settings?

Environment:

Clover 3.3.0.v.20140331 (build-912), Win64, jdk1.8.0_05, Eclipse Luna 4.4 Build: I20140501-0200

sample code that i use:

public class Main {

	public static void main(String[] args) {
		ArrayList<String> list = new ArrayList<>();
		list.add("foo");

		list.forEach(item -> {
			System.out.println(item);
		});
	}
}

					
				
			
			
			
				
			
			
			
			
			
			
		

1 answer

0 votes
Marek Parfianowicz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 10, 2014

Hi Ozhan,

Could you explain a little bit more what exact problem do you have? I'm asking because I used your code sample and it is being instrumented correctly and an HTML report shows coloured lines as expected.

Oh. I noticed that you're using Eclipse Luna 4.4 - please note that Clover 3.3.0 has been released before Luna 4.4. Thus the latest Eclipse version supported by Clover is Eclipse Kepler 4.3. Maybe this is the problem?

Cheers

özhan May 12, 2014

After i downgrade to Eclipse 4.3, the problem still exist. Coverage works well without lambda expression.

Here is the screencast: http://www.youtube.com/watch?v=SC2DGEU2M_o

--

java version "1.8.0_05"

Java(TM) SE Runtime Environment (build 1.8.0_05-b13)

Java HotSpot(TM) Client VM (build 25.5-b02, mixed mode)

--

Eclipse (clean installation with only clover plugin)

Version: Kepler Service Release 2

Build id: 20140224-0627

--

Clover Plugin

Version: 3.3.0.v20140331000000

Marek Parfianowicz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 12, 2014

The screen cast is awesome, thanks a lot for making it!

It seems that the test optimization does not work in your case - it shall detect change in a source file and include it in the optimized test run.

Could you check and use "Run as..." instead of the "Run optimized ..." and see what happens?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events