1
1
mirror of https://github.com/qfpl/applied-fp-course.git synced 2024-11-29 16:55:12 +03:00
applied-fp-course/level04
Sean Chalmers ec1bb07dae Add guidance about handling requests without persistent storage.
There is no persistent storage in the application by the time we're expecting
students to write ``Response`` handling functions. So add some more guidance
that we only expect placeholder values to be used, this wasn't sufficiently
clear. Fixes #3

Updated the latter placeholder values to match the guidance offered, for
consistency.

Updated the configuration ``helloMsg`` value and some of the tests to be a bit
more sensible, even if only a little.
2017-09-11 10:29:56 +10:00
..
bin Fix project restructure 2017-08-14 16:48:34 +10:00
src/FirstApp Add guidance about handling requests without persistent storage. 2017-09-11 10:29:56 +10:00
tests Name changes to Applied name. 2017-09-05 13:53:05 +10:00
appconfig.json Add guidance about handling requests without persistent storage. 2017-09-11 10:29:56 +10:00
changelog.md change changelog files to lowercase 2017-09-01 11:17:26 +10:00
default.nix Add Level 04 2017-08-11 10:40:05 +10:00
level04.cabal Documentation updates. Removed some comments 2017-09-06 10:15:24 +10:00
LICENSE Add Level 04 2017-08-11 10:40:05 +10:00
README.md Wording updates, description adjustments 2017-09-06 10:54:50 +10:00
Setup.hs Add Level 04 2017-08-11 10:40:05 +10:00
shell.nix Add Level 04 2017-08-11 10:40:05 +10:00

Level 04

In this exercise we're going to add some tests to our application. Because types are awesome, and tests are pretty good. But types AND tests is pretty much perfect.

These tests will not be awe inspiring, this exercise is primarily to introduce you to adding tests to your Haskell application. The setup of the Cabal file is already completed for you, but will be covered.

As is to be expected, there are multiple testing frameworks and packages available but we will only cover one here. We will use the HSpec framework, with the hspec-wai package to make our lives a bit easier.

Start in tests/Test.hs.

Aside: Tool Introduction - ghcid

Additionally we'd like to introduce a command line tool that you may find useful for Haskell development; ghcid. This is a very lightweight tool that works for any project with a functioning cabal setup.

If you would like to use it, consult its documentation for how to install it, and then in an spare open terminal window, navigate to the root of the Haskell project and run $ ghcid.

It will then attempt to build your project, if errors are found they will be displayed. But more importantly you can go back to editing files in the project and ghcid will refresh in the background. Providing you with new error messages or All Good if it cannot find any errors.

ghcid provides extremely fast feedback, allowing for a nice development process with constant feedback about your changes. It is very useful in tandem with type holes. Give it a try!