id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5394	Perform CI testing on OMEdit	Francesco Casella	Adeel Asghar	"Every now and then serious issues pop up with OMEdit, such as losing code or crashing unexpectedly while working with the GUI, see, e.g. #5392, #5393. I'm always unsure whether they are existing problems being finally revealed, or rather actual new problems popping up.

For version 2.0.0, we should try hard to set up an automated testing framework for the GUI, that re-enacts pre-recorded command sequences from end-users, for example mimicking the building of new models in a library, and checks if the saved result at the end of the sequence remains the same. This should at least prevent regressions during the compiler development. We can't afford not to have any CI testing on the GUI, which is an essential part for the normal end-user experience.

I can volunteer to provide the sequences, but we need:
- a recording feature in OMEdit
- a testing feature in Hudson/Jenkins to replay the recorded sequences"	enhancement	new	blocker	2.0.0	OMEdit