Comments for intellectualcramps

Comment on Serenity for Google TV 1.0.2 by kingargyle

kingargyle — Mon, 01 Apr 2013 20:05:28 +0000

Should be available in the play store by the end of the month. Development versions will start showing up on the project web site soon. I hope to have some subtitle support implemented at least for external players in the next week, and hopefully before the end of the month with the internal player.

Comment on Serenity for Google TV 1.0.2 by Pablo

Pablo — Mon, 01 Apr 2013 19:35:03 +0000

Hello Davis!!! U know when Serenity 1.1.0 (with subtitles support) is out? Im really interesting.
Thansks dude, and good work!!!

Comment on >IDE Agnostic Builds by Matthew S

Matthew S — Mon, 04 Mar 2013 02:51:43 +0000

This is pretty old but I thought I’d share a recent experience. I’m was an Eclipse user for years and about three years ago I decided to switch to Netbeans. Eclipse had just started to feel…well I’m not here to troll – it just didn’t suit me as much any more. I was surprised to find that Netbeans actually runs Maven projects natively. There is no “two sets of config info” – it just works out of the box, no hassle. And since my builds are automated on Jenkins and pushed out to a repository, with automatic versioning, etc – I’ve been very happy. I recently was given the task of mavenizing a plugin/feature/site build so that we could get it built as part of our continuous integration proceses; I used tycho and with almost no configuration, everything just worked. It’s been a real treat!

Comment on Caging Knowledge by Rick

Rick — Wed, 20 Feb 2013 21:32:35 +0000

I seem to go along with almost everything that has been written throughout “Caging Knowledge | intellectualcramps”.
I am grateful for all the actual details.Thanks,Elissa

Comment on Enable Code Coverage for Integration and Unit Tests using Cobertura and Maven by kingargyle

kingargyle — Tue, 16 Oct 2012 21:09:18 +0000

Yes. However, now I would recommend another plugin to check out. Jacoco – http://www.eclemma.org/jacoco/trunk/doc/maven.html

It instruments on the fly. So you can set it up so it does both Integration and Unit tests, and there is no second stage like typically happens with the cobertura plugin. It also integrates well with Sonar.

Comment on Enable Code Coverage for Integration and Unit Tests using Cobertura and Maven by Kevin Douglas Gann

Kevin Douglas Gann — Tue, 16 Oct 2012 19:01:16 +0000

I’ve been researching a way to get the coverage of our integration tests against implemented page objects/components. From what I’ve seen Cobertura doesn’t instrument stuff in the test directory. This is the closest thing I’ve seen. I assume would work for my situation as well?

Comment on Web Service Documentation using WSDLDocTool by Greg

Greg — Wed, 19 Sep 2012 18:47:41 +0000

‘The documents argument takes a comma seperated list of WSDL’s to generate documentation’ should read ‘The documents argument takes a semicolon seperated list of WSDL’s to generate documentation’

Comment on Jacoco, Tycho, and Coverage Reports by kingargyle

kingargyle — Wed, 01 Aug 2012 20:44:21 +0000

You need to use the append configuration option for the jacoco prepare-agent. See http://www.eclemma.org/jacoco/trunk/doc/prepare-agent-mojo.html

That will put everything in one jacoco.exec statement and then you can point the report generator to that common jacoco.exec to generate the XML or HTML reports.

Comment on Jacoco, Tycho, and Coverage Reports by Kathiravan Tamilvanan

Kathiravan Tamilvanan — Tue, 31 Jul 2012 00:33:32 +0000

I have just figured out the issue with the SplitVerifier. Got the coverage to work but the aggregate with the ant-run plugin as you have described is not working for me. I see the reports for each plugin separately under their corresponding test fragments. how do i aggregate them in one report.
Thanks in advance.

Comment on Jacoco, Tycho, and Coverage Reports by kingargyle

kingargyle — Mon, 30 Jul 2012 23:19:38 +0000

Not sure. I would suggest asking on the Jacoco forums and see if they have any information. I know that Jacoco in the past has had problems with Hibernate or things that can do some funky class loader magic. You can always exclude the jibx framework from code coverage itself so it doesn’t get instrumented.