Using mabl testing, it was difficult to get set up. Mabl does not allow access to the "window" JavaScript object, which restricted setting up some tests.
I got around it by adding a hidden element, using JavaScript to unhide it, clicking on the button, and the button itself called a function that references ace editor functionality because it has access to ace editor in the document's scope.
Mable doesn't record keyboard events on the ace editor - because it doesn't recognize DIV elements as editable. The test that I created needed to remove all the current text and use a dropdown on the form to add new text into the Ace Editor. So I needed a backdoor access to the ace editor object, which wasn't available within the Mable scope because the window object was not available.