[cdt-dev] Sanity CDT Build 1.2.1 RC3

[James Ciesielski <jciesiel@xxxxxxxxxx>]

Recommendation:    
 Build looks great!

Results:

Test	Linux 1.2.1 RC3	Windows 1.2.1 RC3
0	No JUnit testing results to report	No JUnit testing results to report
1	Pass	Pass
2	Pass	Pass
3	Pass	Pass
4	Pass	Pass
5	Pass	Pass
6	Pass	Pass
7	Pass	Pass
8	Pass	Pass
9	Pass	Pass

Notes: 
None.

Sanity testing assumes your environment is set up with:
  a. JDK 1.3.1_09 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 2.1.2 (with or without the -data argument) 
  e. Use Install/Update Perspective to get to http://update.eclipse.org/tools/cdt/updates/builds/1.2.1RC3

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 


Cheers,
James Ciesielski
IBM Rational Software, Canada