Home

Refactoring

Josh and Eyal plan to refactor and validate the Strappy code base by June 26th.

• Redesign directory and library structure to separate core EC code from analysis code and project specific code. (Eyal) Notes on planned architecture
• Implement logging in a new simulation module (Josh).
• Setup a new configuration file parser using Configurator (Josh).
• Setup new visualization and data analysis tools (Josh).
• Write unit tests for the core library.

Writing unit tests

We are using HSpec to write and run unit tests for Strappy. For an example, see the beginnings of the test suite for the strappy-core project. For each project, tests are located in the project top level directory in a test/ directory. The single file in that directory should contain only a GHC pragma {-# OPTIONS_GHC -F -pgmF hspec-discover #-}. This pragma instructs the cabal test-suite runner to search for spec code in this and subdirectories. hspec-discover will look at any file whose name ends in Spec.hs and whose modules export a spec :: Spec variable.