Too much redundancy in xx-branch-merge-proposals

[Paul Hummer]

After a significant amount of work in the test, Tim and I have noticed that there is a lot of redundancy in the xx-branch-merge-proposals test. It needs to be re-worked in the next cycle

[Paul Hummer (rockstar)]

The best thing to do in this case is to remove redundant tests, and then modularize the other tests. For instance, the merge queues tests should really be their own set of tests. They may, in fact, require some of the same functionality as branch merge proposals, but that functionality can really be duplicated without having to test its functionality, so it's minimal.

This, in the end, has been what I've decided needs to be done.

[Paul Hummer (rockstar)]

I've pulled out the merge queue stuff into its own test, and removed redundant tests. I have it in a branch currently, and am awaiting its review.

[Diogo Matsubara (matsubara)]

Moving to 2.1.9