-
Task
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
There was several bugs reported which handled to data loss when an xml file modified by hand and if no data loss, at least it was messed up and user has no information to solve the issue.
It will be nice to have UI tests about the following usecases:
- Opening of an invalid XML file and switch between Design/Source/configuration editor tabs see https://issues.jboss.org/browse/FUSETOOLS-1608 for instance
- Opening a valid Camel context file, go to Source and modify it to be invalid, switch to other tabs
- add yours...
- is duplicated by
-
FUSETOOLS-2601 UI Tests - create a test to ensure user cannot left xml editor with an invalid xml
- Closed