A SAMPLE TEST PLAN TO TEST A RECORD CHANGE

$\backslash$table$[[$Procedure$,\backslash$table$[[$Address and Maintenance$],["$Record Change Series"$]],$Test Series $2],[$Prepared By:$,,$Date:,Versic,,$],[\backslash$table$[[$Test$],[$Ref$.]],\backslash$table$[[$Condition$],[$Tested$]],$Special Rec,irements,$\backslash$table$[[$Expected$],[$Results$]],\backslash$table$[[$Output$],[$On$]],\backslash$table$[[$Next$],[$Screer$]]],[2\mathrm{.}0,$Change records,,,,,$],[2\mathrm{.}1,\backslash$table$[[$Change existing$],[$record$]],$Key field,,Not allowed,,$],[2\mathrm{.}2,\backslash$table$[[$Change nonexistent$],[$record$]],$Other fields,,$\backslash$table$[["$Invalid key"$],[$message$]],,],[2\mathrm{.}3,\backslash$table$[[$Change deleted$],[$record$]],\backslash$table$[[$Deleted rec$],[$be available$]],$d must,$\backslash$table$[["$Deleted$"],[$message$]],,],[2\mathrm{.}4,\backslash$table$[[$Make second$],[$record$]],$Change $2\mathrm{.}1,$bove,OK if valid,$\backslash$table$[[$Transaction$],[$file$]],$V$45],[2\mathrm{.}5,$Insert record,,,OK if valid,$\backslash$table$[[$Transaction$],[$file$]],$V$45],[2\mathrm{.}6,\backslash$table$[[$Abort during$],[$change$]],$Abort $2\mathrm{.}5,,$No change,$\backslash$table$[[$Transaction$],[$file$]],$V$45]]$

FIGURE $13-5$ When developing a test plan, it is imperative to include the various conditions to be tested, the requirements for each condition tested, and the expected results. Test plans require input from both end users and information systems specialists.