Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] Sanity results for

Tested CDT
on Eclipse build eclipse-SDK-I20040317
on Windows 2000.

Hi-tee-ti! I wanted to paint this build Green for St-Patrick's day, but it will have to be a very light green.
3 existing issues, 1 new issue, fortunately all of them minor.

Test Results
0 676 tests
(existing issue, partially resolved) 54818: 6 junit tests fails for build
1 Pass
2 Pass
3 Pass
4 Pass
5 Pass
6 Pass
7 Pass
8 (existing issue) 54836: Debug blue source pointer now showing when stepping through code...
9 (existing issue) 54842: 3 CDT nested exceptions after shutting down Eclipse
55149: ScannerConfig messages in log file



Sanity testing assumes your environment is set up with:

a. JDK 1.4.2 on your path ("java -version")
b. g++, nm, c++filt is on your path
c. "gdb -version" = 5.2.1 or 5.3
d. You run Eclipse 3.0.0
e. Use Help > Software Updates > Find and Install... > Search for new... >  Add Update Site:
 f. Download all 3 features: core CDT, Standard Make and Managed Builder.

Sanity Tests:

0.  JUnit Tests
1.  You can create new projects.
a. Create a new (Standard Make) C++ project
b. Create a new (Managed Build) C++ project
2.  You can import existing projects.
a. Import an existing C++ project (eg. HelloWorld) from somewhere on disk.
3.  You can build a Standard Make project.
a. Ensure that a valid Makefile exists in the project.
b. Project > Build initiates a build.
4.  You can build a Managed Make project.
a. Ensure that the Managed C++ Make project was created to produce (depending on your host) a Cygwin/Linux/Solaris Executable.
b. Disable Window > Preferences > Workbench > Perform build automatically
c. Use New Class Wizard for a class "Foo" (accept defaults) to create a Foo.cpp and Foo.h file.
d. In "Foo.cpp", type "main" then Ctrl-Space to add a template for main().  (Add a trailing newline.)
e. Project > Rebuild creates the Makefile and builds an executable.
5.  Files are parsed for language highlighting, and for Outline View.
a. Open a CPP file in a C++ project and verify language and outline view.
6.  You can edit and save C/C++ files.
a. Enable Window > Preferences > Workbench > Perform build automatically
b. Open a CPP file, modify something, and save.
c. Saving the file causes an automatic build.
7.  You can use the C/C++ Search mechanism.
a. Enable indexer for project.
b. From the Search dialog, find all Class Declarations named "*" in Workspace.
8.  You can create and run debug configurations.
a. Make sure you have built (with -g option) a simple executable.
b. Create a new Debug configuration (using GDB/Cygwin Debugger)
c. Set "Break at start of main()".
d. Run the configuration.
e. Step over a statement, or run to a break-point.
f. Run to completion.
9. You can close the session.
a. If started from the command-line (Unix/Linux), no messages were produced on the console.
b. There are no errors in the .metadata/.log file

Back to the top