Comments for Erlang, Testing and TDD

Comment on “Weekly” exercise problems on GitHub by htaubert

htaubert — Wed, 02 May 2012 20:02:48 +0000

Hi Gianfranco,

You could also take a look at the cyber-dojo (www.cyber-dojo.com) project by Jon Jagger, which has a rather large selection of languages , including Erlang, built into the framework. Jon is also happy to take in new ideas for excercises, especially if they are language-agnostic.

A great idea nontheless!

–
Henrik

Comment on Erlang EUnit – continuation 1 – Fixtures by Zedric-Bixler

Zedric-Bixler — Fri, 20 Jan 2012 20:44:13 +0000

should be better explained, there are confusing parts

Comment on EUnit – Spawn on Node – Missing Name Problem by gianfrancoalongi

gianfrancoalongi — Tue, 17 Jan 2012 19:56:25 +0000

Nice that you find this helpful.
Actually I would not recommend using {node,NodeName,Tests} for this.

If you really need to test on multiple nodes, give Common Test a try.
CT is very well developed for large scale testing.
In the CT users guide you will find this http://www.erlang.org/doc/apps/common_test/ct_master_chapter.html#id74970

I was just showing that there is a possibility to do it, but alas,
you can also write a webserver in pure Assembly – but I would advice against
doing so.

Comment on EUnit – Spawn on Node – Missing Name Problem by Pedro

Pedro — Mon, 09 Jan 2012 13:06:24 +0000

I found your posts really useful and easy to understand, thanks for them!

I have a question about this problem, though: How can I start testing in different nodes without having to manually start them and load the code? Or better yet, how do I use the {node, NodeName, Tests} fixture?

Thanks!

Comment on Erlang EUnit – continuation 2 – Test Representation by gianfrancoalongi

gianfrancoalongi — Tue, 20 Dec 2011 18:41:13 +0000

Finally got the time in my heart to update this – made it shorter and simpler as well.

Comment on Erlang EUnit – introduction by Cody Rioux

Cody Rioux — Sat, 12 Nov 2011 18:41:19 +0000

Thanks for the quick intro! I’m just getting started with Erlang and I think baking in some TDD skills from the start might really help me out.

Comment on Erlang TDD hand on project – WorkerNet part 8 by itamoeba

itamoeba — Tue, 11 Oct 2011 07:41:27 +0000

Just wanted to say thanks for this. I’ve started converting an application written in Python / PYRO to Erlang and I’m sure your blog will speed up the process, it’s great to see a worked TDD based example as a reference point.

All the best

Steve

Comment on Erlang TDD hands on project – WorkerNet part 1 by Dimitry

Dimitry — Tue, 14 Jun 2011 16:01:22 +0000

That’s really helpfull erlang blog) Especially I like eunit part)

Comment on Erlang EUnit – continuation 2 – Test Representation by gianfrancoalongi

gianfrancoalongi — Mon, 04 Apr 2011 19:30:50 +0000

Per, you are absolutely right!
This shows not only how “tricky” EUnit can be – but also why it’s so important to always start with a failing test! (Something the author of this post did not – ahem) .

Comment on Erlang EUnit – continuation 2 – Test Representation by Per Melin

Per Melin — Sun, 03 Apr 2011 14:23:34 +0000

I’m afraid there’s a bug in several of the tests.

Try changing tupleSTO4/0 so that it should fail. For example:
tupleSTO4() -> ?_test( fun() -> ?assertEqual(1,2) end ).

Run the tests and you’ll notice that it still passes!

?_test returns its argument wrapped in a fun. So when you give it a fun to start with you get a fun that returns a fun, which is the same thing as a test object that can never fail.

Now break nullarySTO1 in the same way so that it fails and you’ll see that the other tests that should call it – nullarySTO2, nullarySTO3, tupleSTO1, tupleSTO2, tupleSTO3, tupleSTO6 and tupleSTO7 – all still pass. It is pretty much the same problem here; a test generator can return one or more funs, but you return funs that return funs, and that is one level too deep.