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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • 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

configuring clover with selenium

Hi ,

Please some body can share configuration of clover with a web app .

after instrumenting the source code how to deploy instrumented  code to a webserver (say tomcat) and run selenium tests against it and find code coverage .

it will really helpfull if some one can provide step by step instructions for a sample web app

1 answer

1 accepted

0 votes
Answer accepted

Please have a look at these guidelines:

 

The exact setup depends on whether you want to collect global code coverage only (i.e. from all tests executed) or do you want to collect per-test code coverage as well (i.e. to be able to track coverage from every single single selenium test).

I recommend to start with the global coverage only as it's easier to set up. Steps:

1. Instrument code with Clover. The best is to have one clover.db as it will be easier to copy (use singleCloverDatabase=true or use absolute path to clover.db to create one database). Also use the 'interval' or 'threaded' flushPolicy.

2. Copy clover.db file to web server. If you have many clover.db files, then you must keep their relative location (e.g. gzip and unzip all of them).

3. Start your application server with -Dclover.initstring=/path/to/clover.db parameter if you have one database or -Dclover.initstring.basedir=/path/to/all/clover.db/folder if you have many databases.

4. Run tests.

5. Stop the server, especially if you did not change flushPolicy (i.e. 'directed' is used).

6. Copy clover.db* files (these are coverage recording files) back to build server (put in the same folder where clover.db is located), run clover:clover to generate reports.

 

If you succeed, then you can configure per-test coverage as a next step. In order to achieve this, you have to run with 'clover.server=true' flag, see the manual linked above for more details.

Thanks Marek . It works fine .

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Jira Cloud Performance Improvements

Hello everyone, I am a product manager in the Jira Cloud team focused on making sure our customers have a delightful experience using our products. Towards that goal, one of the areas which is extr...

163 views 2 8
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