In a constant battle for sweet tests (readable & maintainable) I developed another weapon. Have a look at this tool for acceptance testing: Sweetest. What do you think?
In a constant battle for sweet tests (readable & maintainable) I developed another weapon. Have a look at this tool for acceptance testing: Sweetest. What do you think?
Hey Szczepan. This is interesting, but slightly scary. It reminded me of two very different test tools: Cucumber and TW Studio’s Twist. Can you explain what makes you choose this approach over either of them?
What have you used for parsing/generating the code?
-Ben
Hey BBC!
Cucumber is very cool but I wanted something even simpler, without the layer of translation between text and executable test code. Also cucumber forces ruby and in some cases I want use java for tests. I know too little about Twist to speak up but will have a look at it.
What in your opinion is scary about those kind of tools?
>What have you used for parsing/generating the code?
It’s plain javascript.
Idea sounds very interesting!
Who want experiment in real project ? :-)
Looks interesting, I’ve been looking for this kind of expressing tests since I saw a commercial product that was built on Fitnesse. Now, I may be reading in my own wishes into this but so far it looks really good and I like the idea about being refactor friendly.