Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-test-dev] Sanity Test Results for CDT 2.0 M5 RC1 
Hi cdt-test-dev -

Upon investigation, some bugs reproduced only erratically; be warned, 
there are probably stability issues!

For the record the list of bugs I raised are:

47469 Cannot back out of UpdateMgr then use Distribution Zips 
[->Platform/Update]
47526 ManagedMake attempts to build project with just a header
47540 Search fails in unbuilt ManagedBuild project
47541 Search fails in StandardMake project
47544 Outline View does not always refresh
47546 Search dialog cannot find derived class
47548 Exceptions in log file after Debug session
47559 Creating nameless Make Targets
47563 Typos creating/modifying Make Targets
47571 New Class Wizard's resolved location can be blanked

The draft sanity test plan is attached:


The Sanity Test (plus further ad-hoc testing) was executed on WinXP only, 
using IBM's 1.4.1 JRE.

Cheers,

- Brent




Brent Nicolle/Ottawa/IBM@IBMCA 
Sent by: cdt-test-dev-admin@xxxxxxxxxxx
11/25/2003 12:58 PM
Please respond to
cdt-test-dev@xxxxxxxxxxx


To
cdt-test-dev@xxxxxxxxxxx
cc
cdt-dev@xxxxxxxxxxx
Subject
Re: [cdt-test-dev] CDT 2.0 M5 Release Candidate 1 now available






Hi -

Sanity Test passes on WinXP, with a healthy dose of non-major bugs 
(omitted here, not yet raised) and one potential show-stopper (likely not 
CDT's problem):

I had prepared an Eclipse 3.0M5 "ready to go" with its Update Manager 
pointing at the CDT 2.0 build page.  Unfortunately, this CDT build is 
using a distribution zip.  It looks like once I had started using the 
Update Manager (or rather the E3.0 equivalent), Eclipse wasn't going to 
pay attention to new plugins showing up in its install directory.  So I 
couldn't open the C/C++ Perspective despite the fact that the CDT bits 
were correctly unzipped into Eclipse's features/plugins directories.  With 

a fresh install of Eclipse + CDT, I was able to open the C/C++ Perspective 

and get on with my day.  If you have similar trouble getting started, try 
a fresh install of Eclipse 3.0M5.

I'll raise this bug (probably to Eclipse/Update) after a little more 
investigation, by COB.

Cheers,
 
- Brent




Douglas Schaefer/Ottawa/IBM@IBMCA 
Sent by: cdt-test-dev-admin@xxxxxxxxxxx
11/25/2003 09:43 AM
Please respond to
cdt-test-dev@xxxxxxxxxxx


To
cdt-dev@xxxxxxxxxxx, cdt-test-dev@xxxxxxxxxxx
cc

Subject
[cdt-test-dev] CDT 2.0 M5 Release Candidate 1 now available






Hey gang,

I've finally got together a build of CDT 2.0 that people can test. The 
move to eclipse 3.0 has blown up my build scripts for now (mainly due to 
bugs in PDE). So for now, we need to resort back to the old distribution 
zips. The build can be found on the CDT downloads page:

 
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/cdt-home/downloads/main.html?cvsroot=Tools_Project



Please take a crack at these builds to make sure there are no show 
stoppers. If you find one, please send it to this list so we can triage. 
The objective is to release this build to the public so that people can 
start using the CDT with Eclipse 3.0 M5. As such, the quality has to be 
pretty reasonable. I'd like to get the release out by the end of day 
Wednesday.

Cheers,
Doug Schaefer, Senior Software Developer
IBM Rational Software, Ottawa, Ontario, Canada
_______________________________________________
cdt-test-dev mailing list
cdt-test-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-test-dev


_______________________________________________
cdt-test-dev mailing list
cdt-test-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-test-dev
Title: Sanity Test Suite
Sanity Test Suite
Quick execution for build recommendation
 

Change History

Date Author Description
11/06/2003 Brent Nicolle,
Scott Schmidt		 Initial Sanity Tests from 1.2 forwarded to 2.0.      

Table of Contents

A sanity test (or smoke test) suite is intended to be quickly executed, and to cover many areas of functionality that would interfere with other testing.  A sanity pass indicates more thorough testing can continue.

A sanity test covers the following areas:

  1. You can create new CDT projects.
  2. You can import existing projects from other previous CDT releases.
  3. You can build a Standard Make project.
  4. You can build a Managed Make project.
  5. Files are parsed for language highlighting and for the Outline View.
  6. You can edit and save C/C++ files.
  7. You can use the C/C++ Search mechanism.
  8. You can create and run debug configurations.
  9. You can close the session.

1. Create new CDT projects

Description

Make sure a new build allows creation of new projects.

Steps

  1. Create a new Standard Make C++ Project.
  2. Create a new Managed Make C++ Project.
  3. Create a new Standard Make C++ Project from an existing non-CDT C++ project.
2. Importing previous CDT projects

Description

Making sure importing existing projects works.

Steps

  1. Import an existing CDT project (e.g  HelloWorld) from somewhere on disk, using File > Import > Existing Project. 
3. Building a Standard Make project

Description

To build a Standard Make project.

Steps

  1. Ensure that a valid Makefile exists in the project.
  2. Project> initiates a build. (update required)
4. Building a Managed Make project

Description

To have the ability of to build a Managed make project.

Steps

  1. Ensure that the managed C++ make project was created to produce (depending on your host) a Cygwin/Linux/Solaris executable.
  2. Disable window > preferences > workbench > perform build automatically
  3. Use the New Class Wizard for a class "Foo" (accept defaults) to create a Foo.cpp and Foo.h.
  4. In Foo.cpp, type "main" then Ctrl-Space to add  a template for main().  Add a trailing newline, to prevent g++ from warning about files that don't end in newlines.
5. Files are parsed

Description

For the files to be parsed for language highlighting, and for Outline view.

Steps

  1. Open a CPP file in a C++ project.
  2. Verify language highlighting
  3. Verify outline view.
6. Editing and saving C/C++ files

Description

To have the ability to edit and save C/C++ files.-

Steps

  1. Enable Window > Preferences > Workbench Perform build automatically.
  2. Enable  Project properties > C/C++ Make Project > Auto build = " make all "
  3. Open a CPP file, modify something and save.
  4. Verify saving the file causes an automatic build.
7. Using the C/C++ search mechanism

Description

The C/C++ Search engine is used in refactoring.

Steps

  1. From the Search dialog, filed all class Declarations named "*" in Workspace.
8. Debug configurations

Description

This gives the ability to create and run debug configurations.

Steps

  1. Make sure you have built (with -g option) a simple executable.
  2. Create a new Debug configuration (using GDB/Cygwin Debugger)
  3. Set "Break at start of main ( ) ".
  4. Run the configuration.
  5. Step over a statement, or run to break-point.
  6. Run to completion.
9. Closing the session

Description

Closing the session ensures that CDT does not cause zombie processes.  Exiting also causes all log messages to be flushed.  Furthermore, sometimes log messages appear on the command-line console that started Eclipse; this test checks that console.

Steps

  1. If started from the command-line (Unix/Linux), no message were produced on the console.
  2. There are no errors in the .metadata/ .log file.

 

Back to the top