You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
This page describes Level 0 testing concepts and techniques.
- Level 0 Testing Overview
- VB6 Source Availability Test
- ASP Source Availability Test
- COM Readiness Test
- VB6 Build Test
Level 0 Testing Overview
Recall that Preparation includes the following steps:
- Create your Migration Project
- Set Build Order (if you have more than one migration unit)
- Author Interface Descriptions
- Author Interop Assemblies (optional)
If all is well, then these steps will run successfully you have reached level 0
quality -- Preparation Complete.
Key Point:
Level 0 Quality
|
The migration environment is ready and contains a
complete, consistent copy of source codebase.
|
If you have a very simple migration project (i.e. a stand-alone VBP) and
you are working in its native habitat (i.e., the machine you normally use
to develop the application) then it is not likely that you will encounter any
Preparation issues. However, if you are working with a copy of large complex
code base in an off-site setting -- as is common for migration services
engagements -- then you may run into some minor problems relating to
unregistered or unlicensed COM components or missing source files.
If you encounter problems you will have to do some trouble shooting as
described here to verify that you have all the right pieces in all the
right places.
VB6 Source Availability Test
The VB6 Source Availability Test verifies that all source code files referenced
by your VB6 migration project are in the locations specified by the VBP files:
| TestPlan | Notes
|
| Steps | Highlight the migration units you wish to validate
and Select [Tools\Analyze Source] from the menu.
|
| Expected Results | The SrcSize field is set to a positive
number equal to the total lines of code referenced
by the VBP. This indicates all code files were
found.
|
| Error Condition | The SrcSize field is set to a negative
number. This indicates that at least one file
could not be found.
|
| Troubleshooting | Display the [Source Metrics] tab to see the detailed
source metrics for the migration unit being checked.
The Cnt_Tot field is a -1 on each missing
file.
|
| Resolution | Obtain a copy of the missing file and place it in
the location consistent with the path indicated
in the VBP.
|
An alternative means of identifying missing source files is to run the
Source Structure report and locate any records with Cnt_Tot=-1.
ASP Source Availability Test
The ASP Source Availability Test verifies that all source code files referenced
by your ASP migration project are locations specified by the include statements:
| TestPlan | Notes
|
| Steps | 1. Verify that VirtualRootPath is set properly in your
migration project.
2. Highlight the migration units you wish to validate
and Select [Tools\Analyze Source] from the menu.
|
| Expected Results | The RefStat field is set to "READY"
This indicates all include files were found.
|
| Error Condition | The RefStat field is set to "NOTFOUND"
This indicates that at least one include file
or COM reference could not be found.
|
| Troubleshooting | Display the [References] tab to see the detailed
references for the migration unit being checked.
The RefStat field is NOTFOUND on each
missing file.
|
| Resolution | Obtain a copy of the missing file and place it in
the location consistent with the path indicated
in the include statement.
|
An alternative means of identifying missing include files is to run the
Source References process and locate any records with
RefStat="NOTFOUND".
COM Readiness Test
The COM Readiness Test verifies that interface description files for
the COM components referenced by your migration project are available:
| TestPlan | Notes
|
| Steps | 1. Highlight the migration units you wish to validate.
2. Run the [Author All Interface Descriptions] process
if you have not done so already.
3. Highlight the migration units you wish to validate
and Select [Tools\Analyze Source] from the main menu.
|
| Expected Results | The RefStat field is set to "READY"
This indicates all COM components were found.
|
| Error Condition | The RefStat field is set to "~IDF". This
indicates that at least one IDF file could not be found.
|
| Troubleshooting | Display the [References] tab to see the detailed
references for the migration unit being checked.
The RefStat field is NOTFOUND on each
missing file. Note that for ASP migration units,
the references list also reports the status of
#include files.
Take a look at the log information in the right-
hand side of the References panel and note any
errors.
|
| Resolution | Obtain a copy of the missing COM component and register
it in the migration environment.
Next select the
[Rebuild Interface Description] from the context menu
for the item in the References panel.
Alternatively, you can create an IDF for a specific
COM component by selecting [Tools/Author Interface
Description(s)...] from the main menu.
|
An alternative means of identifying missing COM reference is to run the
Source References process and locate any records with
RefStat="NOTFOUND".
VB6 Build Test
The VB6 Build Test verifies that the migration environment is consistent with
the VBP and that the referenced code files and COM components are valid per
the requirements of the VB6 compiler. It is a best practice to run this test
on your source codes as a validation step:
| TestPlan | Notes
|
| Steps | Highlight the migration units you wish to validate
and Select [Tools\Build VB6] from the main menu.
|
| Expected Results | The SrcBlds field is set to a "SUCCESS"
This indicates that the VB6 build process was successful.
|
| Error Condition | The SrcBlds field is set to "FAIL"
This indicates that the VB6 build process was failed.
|
| Troubleshooting | Click the [VB6] button on the Toolbar to open the
migration unit in VB6 and trouble shoot the build
there.
|
| Resolution | Typically VB6 build problems in mature codes
relate to incorrect COM registration or license settings
|