I practice Test Driven Development almost systematically when I write code. So executing tests and reading their results are more than repetitive tasks.
Repetition could lead to automation... Here I present the first features of a tool that should make my life easier. I call it Gunit64!
When I edit Guile code in Emacs, there are some tools relying on the environment to work (i.e. Emacs extensions like Geiser, Flycheck-Guile). Parts of this environment are project specific while others are shared across projects. So I ended up setting manually my environment usually following these few steps:
$ guix shell guile
$ export GUILE_LOAD_PATH="$PWD:$GUILE_LOAD_PATH$
$ emacs some-script.scm
I did turn it into a script I cast as a spell but still, I wanted to go further. And one day…
For a few months, my system systematically asked me for the password of the wifi network.
Thanks to this topic on the KDE forum, I was able to fix the problem with the command sudo pkcon install libkf5wallet-bin.
Such a relief!
Almost one year since I last added a chapter to the book I am writing to help anyone getting started in their Guile journey.
Previously :
My last post was full of errors ! I guess I got lost in the REPL state and faced ghosts, like variables and procedures no more defined… In this post, I give you a new version of the code without errors. You also get a bonus feature : the failing tests are named in the summary. Enjoy !
In this article, I will show you, step by step, how one can simply install and configure software they use with Guix Home. For the demonstration, I will focus on a single package.
Previously :
In my last serie about building a testing framework à la xUnit left me with a weird feeling. Following Kent Beck's execution, from the book « Test Driven Development by Example », the exercise of thinking the Scheme way harder than I thought. I ended up with a shaky copy of the Python implementation. So I decided to let time passing by and come back to it to see what I can do differently. In the meantime, I watched a video of Andy Balaam where he showed a small illustration of the idea of Lambda Calculus and how it can be leveraged using a Scheme. That inspired me. Let's see how much, step by step…
Previously :
The next item on the todo list: Run multiple tests. As we have written four tests since the beginning of this serie, speaking about suite is going to be handy.
Previously :
The next item on the todo list: Report failed tests. The last chapter let the state of the test suite in a shaky state. Indeed, the last one is still red! According to Kent Beck, the following chapter is like going one step deeper to deal with a more specific – smaller grained – as he said. To ensure our learning base (the tests) is rock solid!
Previously :
The next item on the todo list: Report collected results. So we are going to implement a reporting feature.