MIS 120 Test Planning

Terms Test Case – Set of test inputs, execution conditions and expected results, to determine if a feature is working correctly Test Plan – Document describing scope, approach, resources and schedule of intended test activities. Test Log – Chronologic record of all relevant details about the execution of a test.

Terms Boundary Testing False Negative False Positive Interface Testing Stress Testing Test Case

Component / Unit Test Smallest Scope Performed by developer Run each line of code

Assembly / System / Function Test Increased Scope Performed by tester Verify traceability to design deliverables Functionality Interface (user and system) Longest phase in testing methodology

Product Test Increased Scope Verify traceability to PLRs / LLRs Can include performance test Can be regression test for enhancements to existing system Also know as End-to-End (E2E) Test or Regression Test

User Acceptance Test (UAT) Project-Wide Scope Verify traceability to HLR’s Often conducted by Requirements Analysts and / or Business Sponsors Can take many forms

V Model

Information in a Test Plan Introduction Methods Schedules Resources, etc. Required Resources What you will test Documents produced during testing Risks and Dependencies Testing Results / Goals

Information in a Test Case Test Case ID Unit to test Assumptions Test Data Steps to be executed Expected Results Actual Results Pass / Fail

How to be GOOD at Writing Test Cases Care about testing! Like breaking code Be Organized Write Test Cases Early Read Specs Carefully Understand Business Need Behind the Spec Test the Simple Stuff Test Error Handling Test the Boundaries Automate When Possible

Questions?

TopHat True / False Quiz Set of test inputs, execution conditions and expected results, to determine if a feature is working correctly You’re going to do UAT. Only question is before or after you go live! Test Flow is Unit Test  Function Test  Product Test  UAT A good test plan will include test cases for all boundaries.