tt> may need to be called before some methods can be tested contributing 22% of total class cost On line 131, Setter method void setContent(Component) may need to be called before some methods can be tested contributing 22% of total class cost On line 131, Setter method void setContent(Component) may need to be called before some methods can be tested contributing 22% of total class cost On line 131, Setter method void setContent(Component) may need to be called before some methods can be tested contributing 22% of total class cost On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 1% of total class cost On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 1% of total class cost On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 1% of total class cost On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 1% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

The code itself is complex, and it will be hard to test all the different paths of execution

There are complicated methods Why is it bad?

Around line 138, method DCharts createPartyWinnerChart() has high complexity contributing 1% of total class cost

Refactor the method by breaking the complex portions into several smaller methods.

Cost: 2,782

Class com.hack23.cia.web.impl.ui.application.views.user.politician.PoliticianView is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 1% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 1% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 1% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 1% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 1% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 301, Label(String) is called contributing 19% of total class cost
On line 127, void setSizeFull() is called contributing 19% of total class cost
On line 360, void setSizeFull() is called contributing 19% of total class cost
On line 512, DCharts() is called contributing 15% of total class cost
On line 431, SimpleDateFormat(String) is called contributing 6% of total class cost
On line 185, void createRoleSummary(VerticalLayout, List, ViewRiksdagenPolitician) is called contributing 5% of total class cost
On line 340, BeanItemContainer(Class, Collection) is called contributing 5% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

The code itself is complex, and it will be hard to test all the different paths of execution

There are complicated methods Why is it bad?

Around line 300, method void createRoleSummary(VerticalLayout, List, ViewRiksdagenPolitician) has high complexity contributing 24% of total class cost
Around line 412, method DCharts createLineChart(String) has high complexity contributing 21% of total class cost

Refactor the method by breaking the complex portions into several smaller methods.

Cost: 2,355

Class com.hack23.cia.web.impl.ui.application.views.common.MainView is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 131, Setter method void setContent(Component) may need to be called before some methods can be tested contributing 46% of total class cost
On line 131, Setter method void setContent(Component) may need to be called before some methods can be tested contributing 46% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 3% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 3% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 62, TextArea(String, String) is called contributing 1% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

Cost: 2,156

Class com.hack23.cia.web.impl.ui.application.views.user.party.PartyView is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 124, void setSizeFull() is called contributing 37% of total class cost
On line 460, DCharts() is called contributing 29% of total class cost
On line 405, SimpleDateFormat(String) is called contributing 11% of total class cost
On line 173, BeanItem(Object) is called contributing 9% of total class cost
On line 127, TabSheet() is called contributing 1% of total class cost
On line 461, DCharts setOptions(Options) is called contributing 1% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

The code itself is complex, and it will be hard to test all the different paths of execution

There are complicated methods Why is it bad?

Around line 387, method DCharts createLineChart(String) has high complexity contributing 40% of total class cost
Around line 123, method void enter(ViewChangeEvent) has high complexity contributing 11% of total class cost

Refactor the method by breaking the complex portions into several smaller methods.

Cost: 2,133

Class com.hack23.cia.web.impl.ui.application.CitizenIntelligenceAgencyUI is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 131, Setter method void setContent(Component) may need to be called before some methods can be tested contributing 35% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 3% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These static initializers will need to be run once, when the class is loaded. Why is it bad?

On line 56, static Logger getLogger(Class) is declared contributing 17% of total class cost

Instead of initializing this state statically, try initializing a fresh copy in each instance. Creating new objects in Java is cheap, and this static state can't be cleaned up between tests.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 87, void setLocale(Locale) is called contributing 7% of total class cost
On line 83, DiscoveryNavigator(UI, SingleComponentContainer) is called contributing 2% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

Cost: 1,790

Class com.hack23.cia.web.impl.ui.application.views.user.common.AbstractUserView is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 119, Grid(Indexed) is called contributing 27% of total class cost
On line 164, Label(String, ContentMode) is called contributing 26% of total class cost
On line 71, void setSizeFull() is called contributing 25% of total class cost
On line 112, void println(Object) is called contributing 6% of total class cost
On line 73, Panel(String) is called contributing 1% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

The code itself is complex, and it will be hard to test all the different paths of execution

There are complicated methods Why is it bad?

Around line 119, method Grid createBasicBeanItemGrid(Indexed, String, Object[], Object[], String, AbstractPageItemRendererClickListener) has high complexity contributing 27% of total class cost

Refactor the method by breaking the complex portions into several smaller methods.

Cost: 1,626

Class com.hack23.cia.web.impl.ui.application.views.common.AbstractPageItemRendererClickListener is hard to test because:

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Static methods are called: Why is it bad?

On line 72, static method UI getCurrent() is called contributing 50% of total class cost
On line 63, static method UI getCurrent() is called contributing 50% of total class cost

Since these static methods are complex, we want to mock them out in the unit test. If they are declared in your code, refactor the methods to be non-static, and inject an instance of the class. Otherwise, you can create a wrapper object.

Cost: 1,625

Class com.hack23.cia.web.impl.ui.application.views.common.PageItemButtonClickListener is hard to test because:

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Static methods are called: Why is it bad?

On line 68, static method UI getCurrent() is called contributing 99% of total class cost

Since these static methods are complex, we want to mock them out in the unit test. If they are declared in your code, refactor the methods to be non-static, and inject an instance of the class. Otherwise, you can create a wrapper object.

Cost: 1,601

Class com.hack23.cia.web.impl.ui.application.views.user.document.DocumentView is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 4% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 4% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 101, void setSizeFull() is called contributing 66% of total class cost
On line 145, BeanItem(Object) is called contributing 16% of total class cost
On line 104, TabSheet() is called contributing 3% of total class cost
On line 124, void addComponent(Component) is called contributing 1% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

The code itself is complex, and it will be hard to test all the different paths of execution

There are complicated methods Why is it bad?

Around line 100, method void enter(ViewChangeEvent) has high complexity contributing 20% of total class cost

Refactor the method by breaking the complex portions into several smaller methods.

Cost: 1,587

Class com.hack23.cia.web.impl.ui.application.views.user.goverment.MinistryView is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 4% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 4% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 89, void setSizeFull() is called contributing 67% of total class cost
On line 115, BeanItem(Object) is called contributing 16% of total class cost
On line 92, TabSheet() is called contributing 3% of total class cost
On line 103, void addComponent(Component) is called contributing 1% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

The code itself is complex, and it will be hard to test all the different paths of execution

There are complicated methods Why is it bad?

Around line 88, method void enter(ViewChangeEvent) has high complexity contributing 20% of total class cost

Refactor the method by breaking the complex portions into several smaller methods.

Cost: 1,587

Class com.hack23.cia.web.impl.ui.application.views.user.committee.CommitteeView is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 4% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 4% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 90, void setSizeFull() is called contributing 67% of total class cost
On line 115, BeanItem(Object) is called contributing 16% of total class cost
On line 93, TabSheet() is called contributing 3% of total class cost
On line 102, void addComponent(Component) is called contributing 1% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

The code itself is complex, and it will be hard to test all the different paths of execution

There are complicated methods Why is it bad?

Around line 89, method void enter(ViewChangeEvent) has high complexity contributing 20% of total class cost

Refactor the method by breaking the complex portions into several smaller methods.

Cost: 1,429

Class com.hack23.cia.web.impl.ui.application.views.user.politician.PoliticianRankingView is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 84, TextArea(String, String) is called contributing 33% of total class cost
On line 158, Link(String, Resource) is called contributing 32% of total class cost
On line 117, BeanItemContainer(Class, Collection) is called contributing 18% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

The code itself is complex, and it will be hard to test all the different paths of execution

There are complicated methods Why is it bad?

Around line 111, method Component createTable() has high complexity contributing 18% of total class cost

Refactor the method by breaking the complex portions into several smaller methods.

Cost: 1,257

Class com.hack23.cia.web.impl.ui.application.views.user.party.PartyRankingView is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 114, Table(String) is called contributing 28% of total class cost
On line 162, TextArea(String, String) is called contributing 26% of total class cost
On line 189, Link(String, Resource) is called contributing 25% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

The code itself is complex, and it will be hard to test all the different paths of execution

There are complicated methods Why is it bad?

Around line 110, method Component createTable() has high complexity contributing 28% of total class cost

Refactor the method by breaking the complex portions into several smaller methods.

Cost: 1,257

Class com.hack23.cia.web.impl.ui.application.views.user.committee.CommitteeRankingView is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 92, Table(String) is called contributing 28% of total class cost
On line 169, TextArea(String, String) is called contributing 26% of total class cost
On line 195, Link(String, Resource) is called contributing 25% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

The code itself is complex, and it will be hard to test all the different paths of execution

There are complicated methods Why is it bad?

Around line 89, method Component createTable() has high complexity contributing 28% of total class cost

Refactor the method by breaking the complex portions into several smaller methods.

Cost: 1,256

Class com.hack23.cia.web.impl.ui.application.views.user.goverment.MinistryRankingView is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 2% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 108, Table(String) is called contributing 28% of total class cost
On line 84, TextArea(String, String) is called contributing 26% of total class cost
On line 179, Link(String, Resource) is called contributing 25% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

The code itself is complex, and it will be hard to test all the different paths of execution

There are complicated methods Why is it bad?

Around line 105, method Component createTable() has high complexity contributing 28% of total class cost

Refactor the method by breaking the complex portions into several smaller methods.

Cost: 1,072

Class com.hack23.cia.web.impl.ui.application.views.user.common.AbstractRankingView is hard to test because:

It is expensive to construct an instance of the class, and every test will need to call a constructor.

Setters will need to be called by tests Why is it bad?

On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 3% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 3% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 3% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 3% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 3% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 3% of total class cost
On line 935, Setter method void setHeight(String) may need to be called before some methods can be tested contributing 3% of total class cost

Setter methods should avoid doing serious work. Instead, the initialized state should be passed to the setter.

These collaborators cannot be mocked, so it is impossible to unit test this class in isolation.

Non-mockable collaborators: Why is it bad?

On line 158, DCharts() is called contributing 38% of total class cost
On line 70, void setSizeFull() is called contributing 37% of total class cost
On line 158, DCharts setOptions(Options) is called contributing 1% of total class cost

This method call can't be mocked out from a unit test because the test cannot control how the object is instantiated. This can be caused by: - the object was created using new, - it was returned by a non-mockable collaborator, or - the method is declared final or private, which prevents overriding in a subclass

http://testabilityexplorer.org