The tests are in a response to an issue found when frames get added/removed in quick succession. It was due to the timing of the debounce used in FrameObserver.
This also works to test against possible edge cases and ensures robustness of the feature by going full circle.