[XLS]Unit Test Scenario Checklist - Pennsylvania …dhs.pa.gov/cs/groups/webcontent/documents/document/p... · Web viewTitle Unit Test Scenario Checklist Created Date 1/1/1901 4:00:00

<Project Name> - SDM Unit Test Scenario ChecklistLast Update: <Insert Date>

SDM - Unit Test Scenario Checklist Template1

3/10/16



Visual Basic COM+ Components

Name of Component: Name of Developer:

Name of Reviewer:

Unit Test Checklist

N/A Pass

FunctionalityData validations function properlyComponent functions properly (Create, Read, Update, Delete)Component enforces the proper business rulesErrors are raised to the callerProper encoding/decoding of XML strings (XML reserved chars.)Mod files are utilized for common functionsDatabase rollbacks occur when errors are encounteredParameter Objects: direction set in VB matches that of the stored proc

Sign-Off - Date -

Code QA Checklist

N/A Pass

Format and StyleEnsure Comments are present at the file headerEnsure that Comments are present to describe all functionsEnsure that commented/dead code is cleanedEnsure that tabbing/white spaces is used consistently

Sign-Off - Date -

Reviewedby

Developer Comments

Reviewedby

Developer Comments



Coding Standards & PracticesGeneral

VB COM Template structure followedOption Explicit usedProper project references exists; unused references removedEarly binding is used for objects where possibleUse CreateObject to create objects within same project (otherwise New)Functions/Subroutines properly commentedProper variables names usedProper function/subroutine names usedProper filename used for componentError handler routine uses SetAbortEach 'Open' has a 'Close' for Recordset and Connection ObjectsADO objects to use .close prior to set = nothingCorrect use of ObjectContextAvoid instantiating objects that are not used in class/methodPerformance techniques followed where possibleEnsure that explicit Request Object Properties are used (i.e. form)Error Handler routine destroys all open objectsError Handler uses SetAbortEnsure that all methods raise a non-blank errorVisual Basic and other Single-Threaded Apartment (STA) objects (including Scripting.Dictionary) are used only at page scopeVariables are declared within subroutines or functions only (no global variables)



Performance

Ensure correct hard-typing of variablesAvoid multi-variabl Dim statementsAvoid implicit object creation (Dim and New in same statement)Use ByRef parameters properly within private methods

Code passes NuMega Code Review evaluationMemory

Ensure correct use of Object ContextAvoid 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-

Use New rather than CreateObject except when instantiating classes within the same project



Oracle Packages and Stored Procedures

Name of Developer:

Name of Reviewer:

Unit Test Checklist

N/A Pass

FunctionalityStored procedures function properly (Create, Read, Update, Delete)Errors being raised to callerParameter direction in stored proc matches that of VB parameter object

Sign-Off - Date -

Code QA Checklist

N/A Pass

Coding Standards & PracticesStored procedures properly commentedProper filename used for packageProper 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 proceduresVerify SQL with DBAPerformance techniques followed where possible

Sign-Off - Date -

Name of package or Stored Procedure:

Reviewedby

Developer Comments

Reviewedby

Developer Comments



OtherProgram specification document updated


Name of PKG-Date-

Sign-Off-



Visual Basic Executable Components

Name of EXE: Name of Developer:

Name of Reviewer:

Unit Test Checklist

N/A Pass

FunctionalityEnforces the proper business rulesProduces the proper output fileBatch log file updatedExecutable shuts down properly after terminationDatabase rollbacks occur when errors are encounteredProper 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

N/A Pass

Coding Format and StyleEnsure Comments are present at the file headerEnsure that Comments are present to describe all functionsEnsure that commented/dead code is cleanedEnsure that tabbing/white spaces is used consistently

Sign-Off - Date -

Reviewedby

Developer Comments

Reviewedby

Developer Comments



Coding Standards & PracticesOption Explicit usedProper project references exists; unused references removedEarly binding is used for objects where possibleUse CreateObject to create objects within same project (otherwise New)Functions/Subroutines properly commentedProper variables names usedProper function/subroutine names usedProper filename used for componentAll objects explicitly destroyedError handler routine explicitly destroys all objectsError handler routine uses SetAbortEach 'Open' has a 'Close' for Recordset and Connection ObjectsADO objects to use .close prior to set = nothingCode is readable and easy to follow (proper indentation, etc.)Correct use of ObjectContextAvoid instantiating objects that are not used in class/method


Program specification document updated


Name of EXE-Date-

Sign-Off-



Active Server Pages (ASP)

Name of ASP: Name of Developer:

Name of Reviewer:

Unit Test Checklist

N/A Pass

Layout

Verify that Correct page title is displayed below header and in Browser window

Verify that Proper header menus are displayedVerify that Correct menu hyperlinks are highlightedVerify that Status bar values are set with the proper information from SessionVerify that Mandatory fields are indicated with (*)Ensure Proper formatting of data (i.e. SSN, DOB, Address)Verify Image layout and whether proper images are usedEnsure that ALT tags are present for all imagesVerify Button TextVerify Presentation of Page BannerVerify Text Formatting and Spacing

Sign-Off - Date -

Reviewedby

Developer Comments



Field ValidationsVerify Text Field Currency ValidationsVerify Text Field Date ValidationsVerify Text Field Maximum LengthsVerify Text Field Numeric ValidationsVerify Text Field Currency Length and Special Character ValidationVerify that Necessary User Warnings Appear on Validations

Sign-Off - Date - Other Validations

Ensure that no delimiting characters in free-from text fieldsEnsure that SIZE and MAXLENGTH are set for all textbox controls

Sign-Off - Date - Navigation

Verify Action ButtonsVerify All HyperlinksVerify Tab OrderClick 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 dataVerify Delete of Application dataVerify Insert of Application dataVerify Retrieval of application dataVerify Update of application data

Sign-Off - Date -



FunctionalityClient-side (JavaScript) validations function properly Server-side (VBScript) validations function properlyProper error/warning messages are displayedProper 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?


Is the page easy to use read and understand?

Sign-Off - Date -

Code QA Checklist

N/A Pass

Format and StyleEnsure Comments are present at the file headerEnsure that Comments are present to describe all functionsEnsure that commented/dead code is cleanedEnsure that tabbing/white spaces is used consistently

Sign-Off - Date -

Reviewedby

Developer Comments



Coding Standards & PracticesGeneral

Ensure Proper usage of stylesheets (.css)Proper use of #INCLUDE filesASP Template structure followedOption Explicit is UsedFunctions/Subroutines properly commentedProper variables names usedProper function/subroutine names usedProper filename used for ASPAll objects (including Recordsets) explicitly destroyedMaxlength property set on all textbox controlsEach 'Open' has a 'Close' for Recordset and Connection Objects

Code is readable and easy to follow (proper indentation, etc.)Performance techniques followed where possibleEnsure that explicit Request Object properties are used (i.e. .form)

Performance

Avoid multi-variable Dim statements in ASPSign-Off - Date -

OtherProgram specification document updated


Name of ASP-Date-

Sign-Off-

Variables are declared within subroutines or functions only (no global variables)



Visual Basic COM+ Components ExplanationsFunctionality Description/Instruction

Data validations function properly

Component functions properly (Create, Read, Update, Delete)

Component enforces the proper business rulesErrors are raised to the caller

Mod files are utilized for common functions

Database rollbacks occur when errors are encountered

Coding Format and Style Description/Instruction

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 commented and dead code is cleaned and deleted.

Ensure that tabbing/white spaces is used consistently

Test create, read, update and delete functionalities of COM components that interact with the database.

Proper encoding/decoding of XML strings (XML reserved chars.)

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

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.

Proper Indentation in multiples of four spaces should be followed while coding for legibility and flow of script.



Coding Standards & Practices Description/InstructionGeneral

VB COM Template structure followed Please refer to COM+ standards and guidelines to view the template structure

Option Explicit used

Proper project references exists; unused references removed Make sure that old references (i.e. data env) are removed.Early binding is used for objects where possible

Functions/Subroutines properly commentedProper 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.Error handler routine uses SetAbort

Each recordset and Connection object that is open should be closed.

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

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 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.

Use CreateObject to create objects within same project (otherwise New)

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 Set MakeObject = CreateObject(“XYZ”) End SelectEnd 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 .

Each 'Open' has a 'Close' for Recordset and Connection Objects



Correct use of ObjectContext

Avoid instantiating objects that are not used in class/method

Performance technicques followed where possible

Error Handler routine destroys all open objects

Error Handler uses SetAbortEnsure that all methods raise a non-blank error

Performance Description/InstructionEnsure 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.

Do not declare a variable, set it =something (instantiate) and then not use it in method.

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:

m_rstM_RSTRS.Close Set rstRS = Nothing

at the end of your script.

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 function or subroutine, local variable access is faster than global variable access. Use of local variables also tends to make code cleaner, so use them when you can.

Avoid implicit object creation (Dim and New in same statement)

No Use of New in same line as Dim. Converse of early binding. Never define an object and set it to new in the same statement.



Use ByRef parameters properly within private methods

Code passes NuMega Code Review evaluation Make sure that Code is run through NuMega and approved by the Numega lead.Memory Description/InstructionEnsure correct use of Object Context

Avoid instantiating objects that are never used in 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.

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 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".

Use New rather than CreateObject except when instantiating classes within the same project


MakeObject(p_strClass as String) as Object Select Case UCase(p_strClass) Case “XYZ” Set MakeObject= New m_objMyLibrary.XYZ Case Else Set MakeObject = CreateObject(“XYZ”) End SelectEnd 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 .




Oracle Packages and Stored Procedures ExplanationsFunctionality Description/Instruction

Errors being raised to caller

Coding Standards & Practices Description/InstructionStored procedures properly commentedProper filename used for package

Code is readable and easy to follow (proper indentation, etc.)Explain plan has been run on stored proceduresVerify SQL with DBA Verify SQL with DBA for inefficiencies.Performance techniques followed where possible

Other Description/Instruction


Stored procedures function properly (Create, Read, Update, Delete)

Parameter direction in stored proc matches that of VB parameter object

Proper variables names used (i.e. parameters prefixed with 'p_')




Visual Basic Executable Components ExplanationsFunctionality Description/Instruction

Enforces the proper business rulesProduces the proper output fileBatch 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.

Database rollbacks occur when errors are encountered

Coding Format and Style Description/InstructionEnsure Comments are present at the file header


Ensure that commented/dead code is cleaned


Proper encoding/decoding of XML strings (XML reserved chars.)Parameter Objects: direction set in VB matches that of the stored proc





Coding Standards & Practices Description/Instruction

Option Explicit used

Proper project references exists; unused references removed Make sure that old references (i.e. data env) are removed.

Early binding is used for objects where possible

Functions/Subroutines properly commented

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 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.

The following lines of code demonstrate late binding:Dim objExcel as ObjectSet objExcel = CreateObject("Excel.Application")objExcel.Workbooks.Add

The following lines of code demonstrate early binding:

Dim appXL As Excel.ApplicationSet appXL = CreateObject("Excel.Application")appXL.Workbooks.Add

Use CreateObject to create objects within same project (otherwise New)


MakeObject(p_strClass as String) as Object Select Case UCase(p_strClass) Case “XYZ” Set MakeObject= New m_objMyLibrary.XYZ Case Else Set MakeObject = CreateObject(“XYZ”)

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 . 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.



Proper variables names used

Proper function/subroutine names used

Proper filename used for component Ensure that filenames follow project naming standards.

Error handler routine explicitly destroys all objects

Error handler routine uses SetAbort


ADO objects to use .close prior to set = nothing Make sure all ADO objects have a .close before they are set=nothing.Code is readable and easy to follow (proper indentation, etc.)Correct use of ObjectContext

Avoid instantiating objects that are not used in class/method



Refer to COM+ Standards and Guidelines and follow COM+ standards of naming variables.Refer to COM+ Standards and Guidelines and follow COM+ standards of naming variables.








Active Server Pages (ASP) ExplanationsLayout Description/Instruction

Verify that Proper header menus are displayedVerify that Correct menu hyperlinks are highlighted

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 TextVerify Presentation of Page BannerVerify Text Formatting and Spacing

Field Validations Description/InstructionVerify Text Field Currency ValidationsVerify Text Field Date ValidationsVerify Text Field Maximum LengthsVerify Text Field Numeric Validations

Verify that Necessary User Warnings Appear on ValidationsOther Validations Description/Instruction

Ensure that no delimiting characters in free-from text fields

Verify that Correct page title is displayed below header and in Browser window

Verify that Status bar values are set with the proper information from Session

Ensure that every image has a ALT="description" property to it describing the image.

Verify Text Field Currency Length and Special Character Validation

Ensure that SIZE and MAXLENGTH are set for all textbox controls



Navigation Description/InstructionVerify Action Buttons Click all action buttons and ensure that they trigger the corresponding actions.

Verify All Hyperlinks

Verify Tab Order Tab through the form to see if the tab order is logical and user-friendly.

Click on random places on the page and report any unusual behavior.

Page Startup Description/Instruction

Verify Invoking Page from Following page

Verify Invoking page from Prior page

Processing Description/Instruction

Verify Cleanup of Unrelated data

Verify Delete of Application data

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.

Verify Update of application data

Functionality Description/InstructionClient-side (JavaScript) validations function properly Server-side (VBScript) validations function properlyProper error/warning messages are displayed

Check to see if the correct reference tables are pulled up for drop down boxes.

Default action is performed when user clicks <ENTER>

Page displays properly for each mode (Read/Update)Page functions properly (Create, Read, Update, Delete)Does the page correspond to detailed design specs?


Click on all the hyperlinks and make sure that the links takes you the right destination.

Click on Random Places on page and look for unusual behavior

Verify that the pages are in the right sequence and the following page is the page that is supposed to appear.Verify that the pages are in the right sequence and the prior page is the page that the current page should be invoked from.

Make sure that changes in status (programs applied for, etc) triggers cleanup and unrelated data is cleaned up from the database. Make sure that deleting the data from the GUI interface actually deletes it from the database.

Make sure that updated are reflected on subsequent screens and are committed to the database as well.

Proper reference table values are loaded (drop-down boxes, etc.)

Proper encoding/decoding of QueryString data (Netegrity reserved chars.)



Is the page easy to use read and understand?Format and Style Description/Instruction

Ensure Comments are present at the file header


Ensure that commented/dead code is cleaned


Coding Standards & Practices Description/InstructionGeneralEnsure Proper usage of stylesheets (.css)Proper use of #INCLUDE filesASP Template structure followed Please refer to ASP Standards and Guidelines.

Option Explicit is Used

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



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 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.






Maxlength property set on all textbox controls


Performance techniques followed where possible

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

Performance Description/InstructionAvoid multi-variable Dim statements in ASP Only one variable per line; No Dim x,y,z As X.



There should be a MAXLENGTH property set on every text box. You can test this criterion by entering as much data as you can through the front end and then submit the form. This should not cause any errors.



Local variables are those declared within subroutines and functions. Within a function or subroutine, local variable access is faster than global variable access. 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)

[XLS]Unit Test Scenario Checklist - Pennsylvania …dhs.pa.gov/cs/groups/webcontent/documents/document/p... · Web viewTitle Unit Test Scenario Checklist Created Date 1/1/1901 4:00:00

Documents