(Project Name) - Test Plan & Procedures

<Project Name> - SDM Unit Test Scenario Checklist
Last Update: <Insert Date>
3/10/16
SDM - Unit Test Scenario Checklist Template

1
Visual Basic COM+ Components
Name of Component: Name of Developer:
Name of Reviewer:
Unit Test Checklist

Reviewed
N/A Pass by
Comments
Developer
Functionality
Data validations function properly
Component functions properly (Create, Read, Update, Delete)
Component enforces the proper business rules
Errors are raised to the caller
Proper encoding/decoding of XML strings (XML reserved chars.)
Mod files are utilized for common functions
Database rollbacks occur when errors are encountered
Parameter Objects: direction set in VB matches that of the stored proc
Sign-Off - Date -
Code QA Checklist
Reviewed
N/A Pass by
Comments
Developer
Format and Style

Ensure Comments are present at the file header
Ensure that Comments are present to describe all functions
Ensure that commented/dead code is cleaned
Ensure that tabbing/white spaces is used consistently
Sign-Off - Date -

2
Coding Standards & Practices

General
VB COM Template structure followed
Option Explicit used
Proper project references exists; unused references removed
Early binding is used for objects where possible
Use CreateObject to create objects within same project (otherwise New)
Functions/Subroutines properly commented
Proper variables names used
Proper function/subroutine names used
Proper filename used for component
Error handler routine uses SetAbort
Each 'Open' has a 'Close' for Recordset and Connection Objects
ADO objects to use .close prior to set = nothing
Correct use of ObjectContext
Avoid instantiating objects that are not used in class/method
Performance techniques followed where possible
Ensure that explicit Request Object Properties are used (i.e. form)
Error Handler routine destroys all open objects
Error Handler uses SetAbort
Ensure that all methods raise a non-blank error
Visual Basic and other Single-Threaded Apartment (STA) objects (including
Scripting.Dictionary) are used only at page scope
Variables are declared within subroutines or functions only (no global variables)

3
Performance
Ensure correct hard-typing of variables
Avoid multi-variabl Dim statements
Avoid implicit object creation (Dim and New in same statement)
Use ByRef parameters properly within private methods
Use New rather than CreateObject except when instantiating classes within the
same project
Code passes NuMega Code Review evaluation
Memory
Ensure correct use of Object Context
Avoid instantiating objects that are never used in method
Ensure that all ADO objects use .close before set = nothing
Sign-Off - Date -
Other
Program specification document updated
Sign-Off - Date -
Final Sign-Off and Approval
Name of COM-
Date-
Sign-Off-

4
Oracle Packages and Stored Procedures
Name of package or Name of Developer:

Stored Procedure:
Name of Reviewer:
Unit Test Checklist

Reviewed
N/A Pass by
Comments
Developer
Functionality
Stored procedures function properly (Create, Read, Update, Delete)
Errors being raised to caller
Parameter direction in stored proc matches that of VB parameter object
Sign-Off - Date -
Code QA Checklist
Reviewed
N/A Pass by
Comments
Developer

Stored procedures properly commented
Proper filename used for package
Proper variables names used (i.e. parameters prefixed with 'p_')
Code is readable and easy to follow (proper indentation, etc.)
Explain plan has been run on stored procedures
Verify SQL with DBA
Sign-Off - Date -

5
Other
Sign-Off - Date -
Name of PKG-
Date-
Sign-Off-

6
Visual Basic Executable Components
Name of EXE: Name of Developer:
Name of Reviewer:
Unit Test Checklist

Reviewed
N/A Pass by
Comments
Developer
Functionality
Enforces the proper business rules
Produces the proper output file
Batch log file updated
Executable shuts down properly after termination
Proper encoding/decoding of XML strings (XML reserved chars.)
Parameter Objects: direction set in VB matches that of the stored proc
Sign-Off - Date -
Code QA Checklist
Reviewed
N/A Pass by
Comments
Developer
Coding Format and Style

Sign-Off - Date -

7
Proper project references exists; unused references removed
Use CreateObject to create objects within same project (otherwise New)
Proper filename used for component
All objects explicitly destroyed
Error handler routine explicitly destroys all objects
ADO objects to use .close prior to set = nothing
Sign-Off - Date -
Other
Sign-Off - Date -
Name of EXE-
Date-
Sign-Off-

8
Active Server Pages (ASP)
Name of ASP: Name of Developer:
Name of Reviewer:
Unit Test Checklist

Reviewed
N/A Pass by
Comments
Developer
Layout
Verify that Correct page title is displayed below header and in Browser window
Verify that Proper header menus are displayed

Verify that Correct menu hyperlinks are highlighted
Verify that Status bar values are set with the proper information from Session
Verify that Mandatory fields are indicated with (*)
Ensure Proper formatting of data (i.e. SSN, DOB, Address)
Verify Image layout and whether proper images are used
Ensure that ALT tags are present for all images
Verify Button Text
Verify Presentation of Page Banner
Verify Text Formatting and Spacing
Sign-Off - Date -

9
Field Validations
Verify Text Field Currency Validations
Verify Text Field Date Validations
Verify Text Field Maximum Lengths
Verify Text Field Numeric Validations
Verify Text Field Currency Length and Special Character Validation
Verify that Necessary User Warnings Appear on Validations
Sign-Off - Date -
Other Validations
Ensure that no delimiting characters in free-from text fields
Ensure that SIZE and MAXLENGTH are set for all textbox controls
Sign-Off - Date -
Navigation
Verify Action Buttons
Verify All Hyperlinks
Verify Tab Order
Click on Random Places on page and look for unusual behaviour
Sign-Off - Date -
Page Startup
Verify Invoking Page from Following page
Verify Invoking page from Prior page
Sign-Off - Date -
Processing
Verify Cleanup of Unrelated data
Verify Delete of Application data
Verify Insert of Application data
Verify Retrieval of application data
Verify Update of application data
Sign-Off - Date -

10
Functionality
Client-side (JavaScript) validations function properly
Server-side (VBScript) validations function properly
Proper error/warning messages are displayed
Proper reference table values are loaded (drop-down boxes, etc.)
Default action is performed when user clicks <ENTER>
Proper encoding/decoding of QueryString data (Netegrity reserved chars.)
Page displays properly for each mode (Read/Update)
Page functions properly (Create, Read, Update, Delete)
Does the page correspond to detailed design specs?
Sign-Off - Date -
Other
Is the page easy to use read and understand?
Sign-Off - Date -
Code QA Checklist
Reviewed
N/A Pass by
Comments
Developer
Format and Style

Sign-Off - Date -

11
General
Ensure Proper usage of stylesheets (.css)
Proper use of #INCLUDE files
ASP Template structure followed
Option Explicit is Used
Proper filename used for ASP
All objects (including Recordsets) explicitly destroyed
Maxlength property set on all textbox controls
Variables are declared within subroutines or functions only (no global variables)

Ensure that explicit Request Object properties are used (i.e. .form)
Performance
Avoid multi-variable Dim statements in ASP
Sign-Off - Date -
Other
Sign-Off - Date -
Name of ASP-
Date-
Sign-Off-

12
Visual Basic COM+ Components Explanations

Functionality Description/Instruction
Data validations function properly
Test create, read, update and delete functionalities of COM components that
Component functions properly (Create, Read, Update, Delete)
interact with the database.
Component enforces the proper business rules
Errors are raised to the caller
Proper encoding/decoding of XML strings (XML reserved
chars.)
Mod files are utilized for common functions
Check the database to see if data has been inserted/updated/deleted and
committed despite of error.
Parameter Objects: direction set in VB matches that of the
stored proc
Coding Format and Style Description/Instruction
Ensure comments are present describing the COM component and the basic
functionality.
All Procedures and functions should begin with a brief comment describing the
functional characteristics of the procedure. This description should not describe
the implementation details, because often these change over time, resulting in
unnecessary comment maintenance work, or worse yet, an erroneous comment.
The code itself and any necessary inline comments will describe the
implementation.
Ensure that commented/dead code is cleaned Ensure that commented and dead code is cleaned and deleted.
Proper Indentation in multiples of four spaces should be followed while coding for
legibility and flow of script.

13
Coding Standards & Practices Description/Instruction
General
VB COM Template structure followed Please refer to COM+ standards and guidelines to view the template structure
Turn on 'OPTION EXPLICIT'. In VB and VBScript you can use a variable without
explicitly declaring it. Turning on this option helps identify undefined variables -
which may well be typos - and helps increase performance. Undeclared local
Option Explicit used variables are slow, because the entire namespace must be searched to see if the
variable exists before it is created. Get rid of them. Make everything explicit. It's
good practice, it may trap typos, and it is faster. Look for <Option Explicit = True>
in the beginning of every ASP or COM.
Proper project references exists; unused references removed Make sure that old references (i.e. data env) are removed.
This reduces late binding.
MakeObject(p_strClass as String) as Object

Select Case UCase(p_strClass)
Case “XYZ”
Set MakeObject= New m_objMyLibrary.XYZ
Case Else
Use CreateObject to create objects within same project
Set MakeObject = CreateObject(“XYZ”)
(otherwise New)
End Select
End Function
Also, this way you can move classes to different or multiple DLLs and only need to
update the Object Factory COM component. In addition, if some object needs to
participate in a transaction only sometimes, it can be controlled by having 2 object
factories, one which requires transaction and other which disables them .

Proper variables names used Please refer to COM+ Standards and Guidelines for naming standards.
Proper function/subroutine names used Please refer to COM+ Standards and Guidelines for naming standards.
Proper filename used for component Please refer to project standards around naming components.
Each 'Open' has a 'Close' for Recordset and Connection
Each recordset and Connection object that is open should be closed.
Objects
ADO objects to use .close prior to set = nothing Make sure all ADO objects have a .close before they are set=nothing.

14
Do not declare a variable, set it =something (instantiate) and then not use it in
method.
Performance technicques followed where possible
Ensure that explicit Request Object Properties are used (i.e.
form)
Any object instances should explicitly destroyed after they are done being used.
For instance, if you have a recordset object, make sure you always call:
Error Handler routine destroys all open objects m_rstM_RSTRS.Close

Set rstRS = Nothing
at the end of your script.

Error Handler uses SetAbort
Ensure that all methods raise a non-blank error
Visual Basic and other Single-Threaded Apartment (STA)
objects (including Scripting.Dictionary) are used only at page
scope
Local variables are those declared within subroutines and functions. Within a
Variables are declared within subroutines or functions only (no function or subroutine, local variable access is faster than global variable access.
global variables) Use of local variables also tends to make code cleaner, so use them when you
can.
Performance Description/Instruction
Ensure correct hard-typing of variables Keyword "As" should be present in most cases: "Dim X As X".
Avoid multi-variable Dim statements Only one variable per line; No Dim x,y,z As X.
Avoid implicit object creation (Dim and New in same No Use of New in same line as Dim. Converse of early binding. Never define an
statement) object and set it to new in the same statement.

15
VB defines parameters by Reference by default. By using the ByVal keyword

when declaring a parameter, the parameter doesn't get transmitted back to the
caller using the network unnecessarily. Also, if the client does not require the data
to be sent back, passing in the parameter as ByVal matches the interface's
Use ByRef parameters properly within private methods
semantics more closely. In other words, except for specific instances where a
function is supposed to actually MODIFY THE VALUE of a variable that is passed
in as a parameter (rather than returning a RESULT based on what the method
does), projects should be passing parameters specifically coded as "ByVal".

Case “XYZ”
Case Else
Use New rather than CreateObject except when instantiating
classes within the same project
End Select
End Function
Code passes NuMega Code Review evaluation Make sure that Code is run through NuMega and approved by the Numega lead.
Memory Description/Instruction
Ensure correct use of Object Context
Avoid instantiating objects that are never used in method
method.
Ensure that all ADO objects use .close before set = nothing Make sure all ADO objects have a .close before they are set=nothing.
Other Description/Instruction
Program specification document updated Please check COM specs to make sure they include new or updated functionality.

16
Oracle Packages and Stored Procedures Explanations

Stored procedures function properly (Create, Read, Update,
Delete)
Errors being raised to caller
Parameter direction in stored proc matches that of VB
parameter object
Stored procedures properly commented
Proper filename used for package
Proper variables names used (i.e. parameters prefixed with
'p_')
Code is readable and easy to follow (proper indentation, etc.) legibility and flow of script.
Explain plan has been run on stored procedures
Verify SQL with DBA Verify SQL with DBA for inefficiencies.

17
Visual Basic Executable Components Explanations

Enforces the proper business rules
Produces the proper output file
Batch log file updated Make sure that the batch log file corresponding to the EXE is updated.
Executable shuts down properly after termination Make sure that the executable shuts down properly after termination.
Proper encoding/decoding of XML strings (XML reserved

chars.)
Parameter Objects: direction set in VB matches that of the
stored proc
Coding Format and Style Description/Instruction
Ensure that Comments are present to describe all functions the implementation details, because often these change over time, resulting in
implementation.

18
variables are slow because the entire namespace must be searched to see if the
good practice, it may trap typos, and it is faster.
Proper project references exists; unused references removed Make sure that old references (i.e. data env) are removed.
The following lines of code demonstrate late binding:

Dim objExcel as Object
Set objExcel = CreateObject("Excel.Application")
objExcel.Workbooks.Add
The following lines of code demonstrate early binding:
Dim appXL As Excel.Application

Set appXL = CreateObject("Excel.Application")
appXL.Workbooks.Add

Case “XYZ”
Case Else
Use CreateObject to create objects within same project
(otherwise New)
Early binding increases performance, reduces syntax errors at run time and
increases code readability.
Refer to COM+ Standards and Guidelines and follow COM+ standards of naming
variables.

19
variables.
variables.
Proper filename used for component Ensure that filenames follow project naming standards.
Error handler routine explicitly destroys all objects m_rstM_RSTRS.Close

Set rstRS = Nothing

Objects
ADO objects to use .close prior to set = nothing Make sure all ADO objects have a .close before they are set=nothing.
method.

20
Active Server Pages (ASP) Explanations

Layout Description/Instruction
Verify that Correct page title is displayed below header and in
Browser window
Verify that Proper header menus are displayed
Verify that Correct menu hyperlinks are highlighted
Verify that Status bar values are set with the proper
information from Session
Verify that Mandatory fields are indicated with (*)
Ensure Proper formatting of data (i.e. SSN, DOB, Address)
Verify Image layout and whether proper images are used
Ensure that every image has a ALT="description" property to it describing the
Ensure that ALT tags are present for all images
image.
Verify Button Text
Verify Presentation of Page Banner
Verify Text Formatting and Spacing
Field Validations Description/Instruction
Verify Text Field Currency Validations
Verify Text Field Date Validations
Verify Text Field Maximum Lengths
Verify Text Field Numeric Validations
Verify Text Field Currency Length and Special Character
Validation
Verify that Necessary User Warnings Appear on Validations
Other Validations Description/Instruction
Ensure that no delimiting characters in free-from text fields
Ensure that SIZE and MAXLENGTH are set for all textbox
controls

21
Navigation Description/Instruction
Verify Action Buttons Click all action buttons and ensure that they trigger the corresponding actions.
Click on all the hyperlinks and make sure that the links takes you the right
Verify All Hyperlinks
destination.
Verify Tab Order Tab through the form to see if the tab order is logical and user-friendly.
Click on Random Places on page and look for unusual
Click on random places on the page and report any unusual behavior.
behavior
Page Startup Description/Instruction
Verify that the pages are in the right sequence and the following page is the page
Verify Invoking Page from Following page
that is supposed to appear.
Verify that the pages are in the right sequence and the prior page is the page that
Verify Invoking page from Prior page
the current page should be invoked from.
Processing Description/Instruction
Make sure that changes in status (programs applied for, etc) triggers cleanup and
Verify Cleanup of Unrelated data
unrelated data is cleaned up from the database.
Make sure that deleting the data from the GUI interface actually deletes it from the
Verify Delete of Application data
database.
Verify Insert of Application data Make sure that inserts through the front-end insert to the database.
Verify Retrieval of application data Make sure that pages retrieve correct data from the database.
Make sure that updated are reflected on subsequent screens and are committed
Verify Update of application data
to the database as well.
Client-side (JavaScript) validations function properly
Server-side (VBScript) validations function properly
Proper error/warning messages are displayed
Proper reference table values are loaded (drop-down boxes,
Check to see if the correct reference tables are pulled up for drop down boxes.
etc.)
Default action is performed when user clicks <ENTER>
Proper encoding/decoding of QueryString data (Netegrity
reserved chars.)
Page displays properly for each mode (Read/Update)
Page functions properly (Create, Read, Update, Delete)
Does the page correspond to detailed design specs?

22
Is the page easy to use read and understand?
Format and Style Description/Instruction
the implementation details, because often these change over time, resulting in
implementation.

General
Ensure Proper usage of stylesheets (.css)
Proper use of #INCLUDE files
ASP Template structure followed Please refer to ASP Standards and Guidelines.
Option Explicit is Used
variables are slow, because the entire namespace must be searched to see if the
good practice, it may trap typos, and it is faster.
Functions/Subroutines properly commented Please Refer to ASP Standards and Guidelines.
Proper variables names used Please Refer to ASP Standards and Guidelines.
Proper function/subroutine names used Please Refer to ASP Standards and Guidelines.
Proper filename used for ASP Ensure that project naming standards are followed.
All objects (including Recordsets) explicitly destroyed m_rstM_RSTRS.Close

Set rstRS = Nothing

23
There should be a MAXLENGTH property set on every text box. You can test this
Maxlength property set on all textbox controls criterion by entering as much data as you can through the front end and then
submit the form. This should not cause any errors.
Objects
Local variables are those declared within subroutines and functions. Within a
Variables are declared within subroutines or functions only (no function or subroutine, local variable access is faster than global variable access.
global variables) Use of local variables also tends to make code cleaner, so use them when you
can.
Ensure that explicit Request Object properties are used (i.e.
.form)
Performance Description/Instruction
Avoid multi-variable Dim statements in ASP Only one variable per line; No Dim x,y,z As X.

24

(Project Name) - Test Plan & Procedures

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

(Project Name) - Test Plan & Procedures

Diunggah oleh

Hak Cipta:

Format Tersedia

<Project Name> - SDM Unit Test Scenario Checklist

Last Update: <Insert Date>

SDM - Unit Test Scenario Checklist Template

Visual Basic COM+ Components

Name of Component: Name of Developer:

Unit Test Checklist

Format and Style

SDM - Unit Test Scenario Checklist Template

Coding Standards & Practices

SDM - Unit Test Scenario Checklist Template

SDM - Unit Test Scenario Checklist Template

Oracle Packages and Stored Procedures

Name of package or Name of Developer:

Unit Test Checklist

Coding Standards & Practices

SDM - Unit Test Scenario Checklist Template

SDM - Unit Test Scenario Checklist Template

Visual Basic Executable Components

Name of EXE: Name of Developer:

Unit Test Checklist

Coding Format and Style

SDM - Unit Test Scenario Checklist Template

SDM - Unit Test Scenario Checklist Template

Active Server Pages (ASP)

Name of ASP: Name of Developer:

Unit Test Checklist

Verify that Proper header menus are displayed

SDM - Unit Test Scenario Checklist Template

SDM - Unit Test Scenario Checklist Template

Format and Style

SDM - Unit Test Scenario Checklist Template

Code is readable and easy to follow (proper indentation, etc.)

SDM - Unit Test Scenario Checklist Template

Visual Basic COM+ Components Explanations

SDM - Unit Test Scenario Checklist Template

This reduces late binding.

MakeObject(p_strClass as String) as Object

Functions/Subroutines properly commented

SDM - Unit Test Scenario Checklist Template

Error Handler routine destroys all open objects m_rstM_RSTRS.Close

at the end of your script.

SDM - Unit Test Scenario Checklist Template

VB defines parameters by Reference by default. By using the ByVal keyword

This reduces late binding.

MakeObject(p_strClass as String) as Object

SDM - Unit Test Scenario Checklist Template

Oracle Packages and Stored Procedures Explanations

SDM - Unit Test Scenario Checklist Template

Visual Basic Executable Components Explanations

Database rollbacks occur when errors are encountered

Proper encoding/decoding of XML strings (XML reserved

SDM - Unit Test Scenario Checklist Template

The following lines of code demonstrate late binding:

Dim appXL As Excel.Application

This reduces late binding.

MakeObject(p_strClass as String) as Object

SDM - Unit Test Scenario Checklist Template

Error handler routine explicitly destroys all objects m_rstM_RSTRS.Close

at the end of your script.

SDM - Unit Test Scenario Checklist Template

Active Server Pages (ASP) Explanations

SDM - Unit Test Scenario Checklist Template

SDM - Unit Test Scenario Checklist Template