Caltrops - NetHack





	[quote name="E. L. Koba"][quote name="A MYSTERY SHOPPER"][quote name="E. L. Koba"]The cuke's that non-devs write are just going to be totally re-written by devs to match their existing step definitions. Nobody except the devs are ever going to look back at your existing cukes - so really what is the point of writing them.[/quote] Ahhh! This is my experience as well. [quote]If your devs do it right you have a good suite of full-stack integration tests. Which is invaluable.[/quote] This is the part I personally struggle with. If it were up to me, a developer would write maybe a compile-time test (junits; sorry to be so Java-specific) and the automation person would write ALL the programs and shit used to test it. A dev's role at that point is to get the automation resource unstuck. ("Hey, my sort is bad" / "My test takes forever to run, can you help?" / "I don't understand what you did here, can you explain?") Most developers I've worked with are happy for this arrangement because they don't want to do their jobs AND make a lot of automated tests at the same time. (Some do.) If I were in their position I would say, "What are the goddamned automation engineers here for then anyway?" But that might be because I feel professionally guilty at mastering a goddamn text game making language instead of something useful.[/quote] Well, I've never worked with automation engineers. And I do write a lot of automated tests at the same time as writing code. But I'd imagine if anyone could write good cukes and steps it would be someone who spends a lot of time making text games.[/quote]