Skip to content

Latest commit

 

History

History
97 lines (72 loc) · 4.31 KB

course3.md

File metadata and controls

97 lines (72 loc) · 4.31 KB
Raw

Course Section 3

Testing non-functional code

Introduction: In the following sections, we are going to explore scenarios that are commonly difficult to test, and look at strategies to make them easier to test.

Functional Harness

System Configuration

Scenario: In this scenario, the code is hard to test because so much of the state that it depends upon is not obvious from the function call.
Because a common cause of this is global variables, that will be our example.
First we are going to look at how to capture that state, and then we are going to look at how to control the state.

In File: exercises/exercise2/tests/ValidateDevelopmentEnvironment.cpp

  • Validate environment
    • Run the test
    • Fix the test

In File: exercises/exercise2/tests/SystemConfigurationTests.cpp

  • Write a Poke test for initialiseSystem()

    • Confirmation: Passing test with no verification

  • Capture the global variable rpm

    • Confirmation: Your approval shows the ending value of rpm

  • Capture all global variables

    • Hint: #define PRINT(x) #x" = " << x
    • Confirmation: Your approval shows the ending values of all 10 global variables

  • Capture all starting state of global variables as well

    • Confirmation: Your approval shows the starting and ending values

  • Write a second test, that does the same as the first test

    • Confirmation: Both tests pass when run separately

  • Make and use a function to set the global variables and use it.

    • Hint: setAllGlobals(....)
    • Confirmation: Tests pass when run together AND individually

  • Make a function to write the code to set the global variables

    • Hint: Like this, but writing out the actual values of the globals: 
      std::string generateCodeToSetGlobals()
{
    return "setAllGlobals(4000, 0.01, 0, 0, 0, 1, 2, 3, true, 3.2);";
}
    • Confirmation: You can copy the C++ code from standard output into your IDE, and it compiles

  • Retro

Adding Logging

Scenario: In this scenario, the code is hard to test because none of the results of the function are returned. Everything that occurs is a side-effect.
Because a common cause of this is calls to web service, that will be our example.
First we are going to look at how to capture this behaviour, and then we are going to look at what to do when you can't call the service in tests.

In File: exercises/exercise2/tests/LoggingTests.cpp

  • Write a Poke test for Services.h's initialiseServices()
    • Confirmation: Passing test with no verification
  • Log all REST calls
    • Confirmation: You can see all 5 calls and results
  • Turn on SECURE
    • Confirmation: Your tests no longer work
  • Make a preprocessor seam to log if testing
    • Confirmation: Tests work, without result codes
  • Allow multiple tests
    • Hint: logger.str("")
    • Confirmation: Tests pass when run together AND individually
  • Retro

Files

  • Retro

Database

  • Retro

Homework

  • Print out the homework sheet and keep it by your desk, to increase your awareness throughout the week.

Homework details