Skip to content

Latest commit

 

History

History
61 lines (54 loc) · 3.06 KB

TESTPLAN.md

File metadata and controls

61 lines (54 loc) · 3.06 KB
Raw

Testplan

This testplan can be run from any Configuration: Release, Analyze or Debug... however it probably doesn't make sense to run it from Profile

Basic tests

  • Runs on a 64-bit OS

  • Runs as a 32-bit and 64-bit program

  • Starts and draws the display

  • Help > About works and is correct

    • The version number is correct
    • The build date is accurate

  • Program processes / displays each of the digits:
    1 5 9 D * 8 6 A 2 6 C 4 8 # 0 7 4 2 3 B C # 1 1 1 1

  • No flicker as the keys/frequencies are updated

  • When no tones are present, nothing displays / the output is steady even with some background noise

  • Program detects individual tones

  • Observe the program and each of the threads in Process Monitor and ensure none of the threads consume too much CPU

  • Run DebugView and observe all of the output

  • Test a deep failure. Change the == to != in the following line of audio.cpp:

    dwWaitResult = WaitForSingleObject( ghAudioSamplesReadyEvent, INFINITE );
if ( dwWaitResult == WAIT_OBJECT_0 ) {

    Observe that the message box appears and the program gracefully quits.

  • ALT-F4 ends the program

  • Press ESC and the program exits

  • Double-clicking the upper-left icon on the window frame exits the program

  • Single-clicking the X icon on the right of the window frame exits the program

  • Test the exit code: Start Command Prompt and run the app with: start /wait .\DTMF_Decoder_x64_Debug.exe then check the exit code with echo Exit Code is %errorlevel%

    • Change the default exit code in mvcModel.cpp and ensure the value is reported.
    • Uncomment logTest() in DTMF_Decoder.cpp and make sure it's doing its thing.
      • Uncomment 2 excessively long log tests at the end of log.cpp (one at a time) and verify that they throw asserts.
    • Reverse the tests of every error handler and verify that they work as expected.
    • Ensure runs that end in failure generate a Windiws Error Report. Open the report and ensure all of the
    • Ensure the program runs correctly when used in a Remote Desktop session.
    • Change the DPI from the control panel
      • Test at various DPIs: 96, 120, 144, and 192
      • Test at different color depths
    • Test with multiple monitors (where are the secondary monitor is both to the left and the right of the primary monitor)

Excerpt From The Old New Thing: Practical Development Throughout the Evolution of Windows (Mark Nelson's Library) Raymond Chen https://itunes.apple.com/WebObjects/MZStore.woa/wa/viewBook?id=0 This material may be protected by copyright.

Documentation

  • Check the project's GitHub page and make sure the home page looks good
  • Check the project's open issues on GitHub and make sure they are accurate
  • Check the Doxygen content on UH Unix and make sure it looks good:
    • Check each of the .md files
    • Check a file, down to the source code
      • Ensure the comments in the source code are green