id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
18204	Weird results from JoinNodeWayActionTest unit test	GerdP	team	"Follow up of ticket:18189#comment:17
A unit test that tests a method which uses `MainApplication.getMap().mapView` may run into trouble when it doesn't use something like 
{{{
#!java
        // setup a reasonable screen size
        MainApplication.getMap().mapView.setBounds(new Rectangle(1920, 1080));
}}}
before executing code that uses e.g. `NavigatableComponent.getNearestWaySegments()` 
Without the above statement the height and width of the mapView are 0 and class `NavigatableComponent` doesn't seem to care about this.

I've written a patch to log an error when `NavigatableComponent.getNearestWaySegments()` or
`NavigatableComponent.getNearestNodes()` is used with a very small mapView but other methods may also suffer.
I'd prefer to have a reasonable value for width and height when unit tests are executed but I have no idea where this has to be implemented."	defect	new	normal		Unit tests				ris