1.

Press Control-M (Windows) or Command-M (Mac)

2.

Double-click the tab you want to maximise

3.

all of these answers

4.

Click the Maximise button at the top right of the view

1.

All breakpoints are deleted

2.

none of these answers

3.

All breakpoints will not be fired when debugging and will not cause application execution to suspend

4.

All breakpoints and bookmarks are disabled

1.

Plug-in Development Environment (PDE)

2.

Eclipse Project

3.

Java Development Toold (JDT)

4.

Eclipse .NET

1.

Right-click the selected code and select Add to Snippets

2.

Drag the code into the snippets view

3.

Click Source -> Snippets -> Create Snippet

4.

With the code selected, click the + button in the Snippets view

1.

It expands the comparison between the two files to include whitespace.

2.

It allows you to delete the line of code to which it is connected.

3.

It allows changes from one version of a file to be applied to another version of the file.

4.

It allows you to merge both lines of code together.

1.

Eclipse fills them in with a drop-down menu of available optons.

2.

They are automatically highlighted in code.

3.

They are populated using environment variables.

4.

You populate them through a pop-up windows.

1.

all of these answers

2.

Right-click your project in the Package Explorer and select Team -> Switch To -> New Branch

3.

Click File -> New -> Git -> Branch

4.

Click Source -> Team -> Switch To -> New Branch

1.

to open a file by its name

2.

to search the workbench for a class to open in an editor

3.

to find a string in a text file

4.

to find all places where a certain type is instantiated

1.

the number of errors found in the test

2.

the time it took the test to run

3.

the name of the package containing the test class

4.

the test class name

1.

It sends the currently selected problem to another view.

2.

It indents the currently selected problem.

3.

It opens the Filter menu so you can customise what problems are displayed.

4.

It jumps to the currently selected problem in the Editor.

1.

track the value of a variable throughout the lifetime of the app.

2.

change the name of a variable while debugging.

3.

change the value of a final variable while debugging.

4.

track values of variables when they are out of scope.

1.

The code is the cause of a compiler warning.

2.

The method is unused or causes runtime errors.

3.

The code is within an if statement that is always evaluated as true at runtime.

4.

No code calls the method.

1.

Git

2.

Java

3.

Team Synchronising

4.

Remote Synchronise

1.

Hover ove the variable in the Editor.

2.

Check the Debug view.

3.

Check the Variables view.

4.

Watch the variable in the Expressions view.

1.

Select Use external web browser.

2.

Select Add a new browser and select the desired browser in the External web browsers menu.

3.

Select Use external web browser, click the New or Search button, add your browser, and then select it in the External web browsers menu.

4.

Use the Search button to search for an installed web browser.

1.

Git Staging

2.

History

3.

Synchronize

4.

Git Repositories

1.

a hidden .metadata folder

2.

a hidden .metadata folder and projects imported into the workspace only

3.

only projects imported into the workspace

4.

a hidden .metadata folder and projects created in the workspace

1.

monitor variables that are outside the scope of the current stack frame

2.

set a breakpoint to track a particular instance

3.

inspect the values of an object's fields

4.

edit the value of a variable while the debugger is running your app

1.

tearDown()

2.

setUpClass()

3.

tearDownAfterClass()

4.

setUp()

1.

all of the answers

2.

warnings and errors

3.

code that does not match your formatting settings

4.

threads containing errors

1.

all preferences

2.

none of these answers

3.

the current perspective

4.

preferences for a language (e.g., Java)

1.

Click Window (Eclipse) -> Preferences -> Run/Debug -> Launching, and then select Save required dirty editors before launching.

2.

Click Window (Eclipse) -> Preferences -> Java -> Editor -> Save Actions

3.

Click File -> Save All.

4.

Change the project's run configuration.

1.

In the **Package Explorer**, right-click a class and select **New > JUnit Test Case**.

2.

none of these answers

3.

Create a JUnit Test Case class through the **File** menu.

4.

Create the class manually while in any perspective.

1.

Nothing happens.

2.

The select file is opened in the Editor in its state at the time of the revision.

3.

The revision opens in a **Split Editor** window alongside the current local revision of the file.

4.

A pop-up window showing details about the revision appears.

1.

to switch between preferences within a single workspace

2.

to easily switch between different layouts of views in the Workbenchfor specific tasks

3.

to manage the fact that some views work only in certain perspectives

4.

to debug multiple applications at the same time

1.

You cannot do this in Eclipse.

2.

Select the Editor tab for the XML file and then click the Design tab at the bottom of the editor window.

3.

Double-click the open tab in the Editor.

4.

In the Package Explorer, right-click the file and select Open With > Desgign Editor.

1.

Open the commit in the Git Staging view.

2.

Open the commit in the Git Reflog view.

3.

Double-click a commit in the History view.

4.

Right-click the file in the Package Explorer and select Team > Show in History.

1.

It links the Editor and Navigator, causing the Editor to switch to the file selected in the Package Explorer and vice versa.

2.

It expands Libraries when you are in the Java perspective.

3.

It minimizes the left view

4.

It collapses open folders in the Package Explorer view.

1.

all of these answers

2.

to debug using a different JRE

3.

to customize environment variables

4.

to customize arguments

1.

all of these answers

2.

The scope of the search is too narrow.

3.

The type of search is not appropriate for the language of the code.

4.

There is a typo in the search parameters.

1.

Your project is not using source control.

2.

Your internet connection is down.

3.

Your Git passwordis incorrect.

4.

You need to refresh your project.

1.

all of these answers

2.

a local repository

3.

staged changes

4.

a commit message

1.

view the Design and Source tabs of one XML file at the same time

2.

drag code from one Editor pane into another

3.

split the editor either horizontally or vertically

4.

all of these answers

1.

to remedy an issue where the source code seemsaccurate, but Git is indicating a merge conflict

2.

to remedy syntax errors within the source code, causing the project not to build

3.

to discard any existing build state before building the project, which can remedy issues where the source code seems accurate yet fails to build

4.

to recompile only the source code files that have changed since the last build, which can shorten the build time for long-running builds

1.

Right-click an item in the stack trace and select Terminate/Disconnect All.

2.

all of these answers

3.

Right-click your application and select Terminate.

4.

Right-click a thread and select Terminate and Remove.

1.

Click Run > Debug As > Remote Application.

2.

You cannot do this in Eclipse.

3.

Create and run a configuration under Run > Debug Configurations > Remote Java Application.

4.

Click Run > External Tools.