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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Clover Lambda Expression Coverage


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?


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.forEach(item -> {


1 answer

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?


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

Here is the screencast:


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

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
Community showcase
Published in Marketplace Apps & Integrations

Learn how to request and manage app requests in the Marketplace

G’day everyone! Super exciting news coming from the Marketplace. We have now fully rolled out the ability for end-users to submit app requests to admins directly from within the product! No longer ...

43 views 1 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you