Adjust test ordering in fullscreen_controller_state_ tests.

chrome/browser/ui/fullscreen/fullscreen_controller_state_interactive_browsertest.cc

Index: chrome/browser/ui/fullscreen/fullscreen_controller_state_interactive_browsertest.cc
diff --git a/chrome/browser/ui/fullscreen/fullscreen_controller_state_interactive_browsertest.cc b/chrome/browser/ui/fullscreen/fullscreen_controller_state_interactive_browsertest.cc
index 0664d8e3e411654294a31adc18d86179aae5f377..768354640c17c52865459ef1046162ee3529b766 100644
--- a/chrome/browser/ui/fullscreen/fullscreen_controller_state_interactive_browsertest.cc
+++ b/chrome/browser/ui/fullscreen/fullscreen_controller_state_interactive_browsertest.cc
@@ -99,6 +99,27 @@ Browser* FullscreenControllerStateInteractiveTest::GetBrowser() {
 
 // Tests -----------------------------------------------------------------------
 
+// Soak tests:
+
+// Tests all states with all permutations of multiple events to detect lingering
+// state issues that would bleed over to other states.
+// I.E. for each state test all combinations of events E1, E2, E3.
+//
+// This produces coverage for event sequences that may happen normally but
+// would not be exposed by traversing to each state via TransitionToState().
+// TransitionToState() always takes the same path even when multiple paths
+// exist.
+IN_PROC_BROWSER_TEST_F(FullscreenControllerStateInteractiveTest,
+                       DISABLED_TransitionsForEachState) {
+  // A tab is needed for tab fullscreen.
+  AddTabAtIndex(0, GURL(kAboutBlankURL), PAGE_TRANSITION_TYPED);
+  TestTransitionsForEachState();
+  // Progress of test can be examined via LOG(INFO) << GetAndClearDebugLog();
+}
+
+
+// Individual tests for each pair of state and event:
+
 #define TEST_EVENT_INNER(state, event, reentrant, reentrant_id) \
     IN_PROC_BROWSER_TEST_F(FullscreenControllerStateInteractiveTest, \
                            DISABLED_##state##__##event##reentrant_id) { \
@@ -113,8 +134,6 @@ Browser* FullscreenControllerStateInteractiveTest::GetBrowser() {
     TEST_EVENT_INNER(state, event, false, ); \
     TEST_EVENT_INNER(state, event, true, _Reentrant);
 
-// Individual tests for each pair of state and event:
-
 TEST_EVENT(STATE_NORMAL, TOGGLE_FULLSCREEN);
 TEST_EVENT(STATE_NORMAL, TAB_FULLSCREEN_TRUE);
 TEST_EVENT(STATE_NORMAL, TAB_FULLSCREEN_FALSE);
@@ -211,6 +230,7 @@ TEST_EVENT(STATE_TO_TAB_FULLSCREEN, BUBBLE_ALLOW);
 TEST_EVENT(STATE_TO_TAB_FULLSCREEN, BUBBLE_DENY);
 TEST_EVENT(STATE_TO_TAB_FULLSCREEN, WINDOW_CHANGE);
 
+
 // Specific one-off tests for known issues:
 
 // Used manually to determine what happens on a platform.
@@ -230,21 +250,3 @@ IN_PROC_BROWSER_TEST_F(FullscreenControllerStateInteractiveTest,
   message_loop->Run();
 }
 
-// Soak tests:
-
-// Tests all states with all permutations of multiple events to detect lingering
-// state issues that would bleed over to other states.
-// I.E. for each state test all combinations of events E1, E2, E3.
-//
-// This produces coverage for event sequences that may happen normally but
-// would not be exposed by traversing to each state via TransitionToState().
-// TransitionToState() always takes the same path even when multiple paths
-// exist.
-IN_PROC_BROWSER_TEST_F(FullscreenControllerStateInteractiveTest,
-                       DISABLED_TransitionsForEachState) {
-  // A tab is needed for tab fullscreen.
-  AddTabAtIndex(0, GURL(kAboutBlankURL), PAGE_TRANSITION_TYPED);
-  TestTransitionsForEachState();
-  // Progress of test can be examined via LOG(INFO) << GetAndClearDebugLog();
-}
-