[cdt-test-dev] Sanity on cdt build 1.2.0.44

[Tanya Wolff <twolff@xxxxxxxxxx>]

Recommendation:      Build can be adopted. 

Results: (Only new defects are shown in the table)

Test	Windows 1.2.0.44	Solaris 1.2.0.44	Linux 1.2.0.44
0	(437/438)  1 error	(437/438)  1 error	(437/438)  1 error
1	p	p	p
2.	p	p	p
3	p	p	p
4	p	p	p
5	p	p	p
6	p	p	p
7	p	p	p
8	p	p	p
9	f (breakpoint NPE) 43101, 43122	p	f 43122

#6 The test is for a cpp file, but if you saving a header file, the managed builder isn't invoked... (part of incremental build defect 41826)
#7 --If the dependency tree hasn't been built yet, the indexer hasn't kicked in, and search on class declarations won't return anything (combo of 41826 and 42949). For workaround, save the including code file.
#9 Debugging problems... 43101 had a Null Pointer Exception, and difficulties when debugging with optimization set.
For workaround for the optimization problem, set makefile/build properties to use -O0, or remove option.

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

Sanity Tests: 
0.  The build passes the Automated Integration Suite 
        a. Results are available from http://update.eclipse.org/tools/cdt/updates/builds/1.2/index.html 
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,
Tanya