Commits

Anonymous committed 314f0d6

fixed bug in code

Comments (0)

Files changed (1)

_posts/2014-04-11-testing_your_chicken_code.md

 
 You're still here and not bored away by the little introduction. Very good, since this is finally where the fun starts and we will be seeing actual code. CHICKEN is actually a good environment to do testing. Almost every egg is covered by unit-tests and within the community there seems to be a general agreement, that tests are useful. Additionally tests for CHICKEN extensions are encouraged particularly. We have a great continuous integration (CI) setup, that will automatically run the unit-tests of your eggs, even on different platforms and CHICKENS. You can find more information on [tests.call-cc.org](http://tests.call-cc.org/). I'll tell you a little more about this later. For now just be assured that you're in good company.
 
-Let's continue our little journey now by implementing the well known [stack](https://en.wikipedia.org/wiki/Stack_(abstract_data_type) and building a suite of unit-tests for it. This is a fairly simple task and allows us to concentrate on the tests.
+Let's continue our little journey now by implementing the well known [stack](https://en.wikipedia.org/wiki/Stack_(abstract_data_type)) and building a suite of unit-tests for it. This is a fairly simple task and allows us to concentrate on the tests.
 
 #### Prerequisites
 
 test within these boundaries. It contains information about how many tests have passed and how many tests have failed. It prints that summary at the very bottom,
 so that you can't miss a failing test that has flitted across the screen. I've been bit by that many times.
 Finally the last line in our test file should be **(test-exit)**. This will make the test process exit
-with a status code that indicates the status of tests tests. If there have been any tests failing it will return with a non-zero
+with a status code that indicates the status of tests. If there have been any tests failing it will return with a non-zero
 status code, which can be passed as an argument to the procedure and defaults to 1. Zero will be the status code if all tests have passed.
 
 We'll start by adding the procedure that we obviously need at the beginning. We want a way to create an empty stack. I'll start with a test for it.
 This will generate a description like this, which makes the purpose of the tests pretty clear.
 
 <pre>
-(member 3 (list 2 3 4)) .............................................. [<span style="color:green"> PASS</span>]
+(member 3 (list 1 2 3)) .............................................. [<span style="color:green"> PASS</span>]
 </pre>