Ignore default list of beans created/used by @Autowired


You define a group of beans of certain type in Spring and at the same time you want to define a custom list of these beans. However when using @Autowired to inject this list you end up with the default implementation of the list provided by @Autowired .
Continue reading Ignore default list of beans created/used by @Autowired

Pentaho BA Server: Analysis Report Performance Test – Part 1


Few days ago we were told by the pilot users of our BA Server that for few minutes their performance when creating reports drastically dropped. Our initial guess was that probably it was somehow related to one of the ETL processes running in the background. We started monitoring the database, but we did not see nothing interesting. Hence we decided to get deeper insight into the performance of the BA server itself. My colleague decided to use JMeter but me, I wanted to see whether Selenium engine can get me somewhere.

Continue reading Pentaho BA Server: Analysis Report Performance Test – Part 1

Spock Testing – Spock tutorial

What is Spock?

Spock is a unit testing framework that in great extent utilizes Groovy’s syntax making your tests comprehensible and easy on the eyes. Although it is a Groovy technology you can use it to test your Java classes as well. What is the most important is that Spock makes writing tests fun. And I really mean it.

Why Spock?

I have to admit that even knowing all the benefits of TDD and tests over all I considered writing them as little pain in the neck. How has that changed when I started using Spock?

Continue reading Spock Testing – Spock tutorial

Master Coder Challenge #3 : Number systems converter

About competition

Quite recently Cybercom company announced a Master Coder challange. The competition will be divided into 10 stages, each of them involving a programming task. Despite missing two first assignments I have taken up the gauntlet and completed task #3.

The goal in this stage was to create a number system converter. Converter should be able to handle systems in the range of 2 to 36. For the working application (successfully converting numbers between systems) you would get 200 points. It was possible to get additional 20 points for introducing an exceptional solution. However, it was prohibited to use conditional statements, and conditional expressions. Thus, for every if, else or switch in your code you would be given respectively -5, -10 or -20 points. Numbers should be represented by following characters:
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z
Continue reading Master Coder Challenge #3 : Number systems converter