@@ -34,7 +34,7 @@ import {
34
34
waitForExecutionCompletedSuccessfully ,
35
35
waitForTextOutput
36
36
} from '../notebook/helper' ;
37
- import { initializeWidgetComms , Utils } from './commUtils' ;
37
+ import { hideOutputPanel , initializeWidgetComms , Utils } from './commUtils' ;
38
38
import { WidgetRenderingTimeoutForTests } from './constants' ;
39
39
import { getTextOutputValue } from '../../../kernels/execution/helpers' ;
40
40
import { isWeb } from '../../../platform/common/utils/misc' ;
@@ -128,7 +128,7 @@ suite('Standard IPyWidget Tests @widgets', function () {
128
128
// Widgets get rendered only when the output is in view. If we have a very large notebook
129
129
// and the output is not visible, then it will not get rendered & the tests will fail. The tests inspect the rendered HTML.
130
130
// Solution - maximize available real-estate by hiding the output panels & hiding the input cells.
131
- await commands . executeCommand ( 'workbench.action.closePanel' ) ;
131
+ await hideOutputPanel ( ) ;
132
132
await commands . executeCommand ( 'workbench.action.maximizeEditorHideSidebar' ) ;
133
133
await commands . executeCommand ( 'notebook.cell.collapseAllCellInputs' ) ;
134
134
comms = await initializeWidgetComms ( disposables ) ;
@@ -142,7 +142,7 @@ suite('Standard IPyWidget Tests @widgets', function () {
142
142
await startJupyterServer ( ) ;
143
143
logger . info ( `Start Test (completed) ${ this . currentTest ?. title } ` ) ;
144
144
// With less realestate, the outputs might not get rendered (VS Code optimization to avoid rendering if not in viewport).
145
- await commands . executeCommand ( 'workbench.action.closePanel' ) ;
145
+ await hideOutputPanel ( ) ;
146
146
} ) ;
147
147
teardown ( async function ( ) {
148
148
logger . info ( `Ended Test ${ this . currentTest ?. title } ` ) ;
0 commit comments