ActiveX Controls Test Plan

VC++ V5.0

06-Jan-97

(Modified from the 06-Sept-96 draft)

Overview

This plan describes basic test coverage for the ActiveX Controls within VC++ V5.0. The ActiveX containers to be tested are:

1. Resource Editor (Dialog)

2. Resource Editor Test Menu Item

3. MFC Test Container

Methodology & Acceptance Criteria

Functionality:

In order to pass for acceptance, the controls must do the following:

1. Controls can be inserted using the resource editor.

2. Property pages can be viewed using the resource editor.

3. Test function within the resource editor can be used to view the control.

4. Controls generate wrappers correctly(via Component Gallery) and compile.

5. Controls can be inserted and executed within the MFC Test Container.

Usability and Performance:

The tests in this document are compatibility tests between ActiveX controls and containers in VC++. It is outside the scope of this plan to test for usability or performance.

Area: Resource Editor Hosting

Ensure that the resource editor can insert, host, test, and compile the controls. This subsumes the first four functionality items listed above.

1. In a single app, insert all controls in one or more dialog boxes, using the Component Gallery to generate the wrapper classes and add the control to the resource editor (Dialog).

2. For each control, scroll through the property pages.

3. Run in Test mode and list through all of the controls.

4. Compile and run the app.

5. Observe for compilation warnings and errors. (Common warnings include first chance exceptions and SetExtent warnings.)

What this suite does not test:

• Programmatic creation/execution of the controls.

• Insertion of controls via context menu in the resource (dialog) editor. In this scenario, wrapper classes for the controls are not generated.

Area: Databinding

Ensure that databinding controls can access SQL Server and Oracle databases and correctly populate the databound controls.

1. Create an app that hosts the databound controls.

2. Connect the Remote Data Control to a SQL Server or Oracle Database. Let the active query include a join.

3. Bind the controls to the Remote Data Control.

4. For List/Combobox styled controls, ensure that the lists populate by setting the ListSource and ListField properties.

5. For single entry style controls like MaskedEdit, RichText and DBGrid, ensure that the MSRDC scrolls and updates the control properly.

6. For Calendar type controls, query against a date field.

What this suite does not test:

• Views, synonyms, stored procedures, and other non tabular data.

• Non-text data.

• Boundary conditions.

MBCS Considerations

The controls are not necessarily localized. This test will not do localization testing.

Notes/Open Issues

• Programmatic testing is minimal and does not exercise all code paths.