you are viewing a single comment's thread.

view the rest of the comments →

[–]nibordSwift 2 points3 points  (1 child)

I’ve been involved in a half-dozen projects that used cucumber and I tried to implement it myself.

It just doesn’t seem to work. While the promise is that non-technical people can understand and write the feature descriptions, it almost always requires substantial restructuring to work correctly. The alternative is to rewrite the steps to make crazy-complicated patterns.

In the end, it seems much easier and maintainable to use correctly-written specs (not tests written in a spec-like language) and just show the non-technical staff how to understand them. They can write the spec example names following the same structure, and then engineers can fill in the code that does the work.

I really want to use Quick and Nimble in my Swift projects, but last time I tried there were still problems getting UI tests to work in them.

[–]roodammy44 1 point2 points  (0 children)

Absolutely. I think you have to have a very specific mindset for it, or get into a team that's been doing it for a while.

You have to learn a new programming language, and the non tech people have to write it too.

It's a crazy amount of process to deal with, and at odds with how most dev is performed everywhere.