I ended up adding in another method, Menus.getAllMenus(), because I needed it to iterate though all menus for issue #5078.

In order to run the unit tests for the HTML version of removeMenu(), a couple of temporary changes need to be made.

In src/utils/Global.js, set global.brackets.nativeMenus = false. This forces the HTML menus to turn on.

In test/spec/Menu-test.js, find the following code and comment it out:

        if (!brackets.inBrowser) {
            return;
        }

Doing this assures that the HTML menu unit tests are run. Note that the last five unit tests, which look at context menus, will still fail. Regardless, you can confirm that there are no failures in any of the other tests, including the new removeMenu tests.

I ran the unit tests for this with the dark shell and they all still passed. @lkcampbell you should build the dark shell and make sure it behaves as expected.

@JeffryBooher, agreed. I would like to test the functionality on the dark shell before we consider merging this PR. My schedule is a bit hectic this week so I'm not 100% sure I will have the time to do a build. If that is the case, I can test it on the next Sprint and we can merge this PR then.

@JeffryBooher, I did a build of brackets-shell today and removeMenu() is working correctly with the dark shell.