Differences

This shows you the differences between two versions of the page.

Link to this comparison view

irc:1451516400 [2017/05/27 13:44]
irc:1451516400 [2017/05/27 13:44] (current)
Line 1: Line 1:
 +[01:04:27] *** ChanServ sets mode: +o temporalfox
 +
 +[09:57:36] *** ChanServ sets mode: +o temporalfox
 +
 +[10:09:22] <​aesteve>​ hi everyone :)
 +
 +[10:25:46] <​aesteve>​ temporalfox:​ I was thinking about something in regard of vertx-unit and maybe you have an opinion on this
 +
 +[10:25:58] <​temporalfox>​ hi
 +
 +[10:27:46] <​aesteve>​ 90% of my tests are stimulus-reaction based
 +
 +[10:28:02] <​temporalfox>​ usually that's what happen yes
 +
 +[10:28:12] <​temporalfox>​ you can see such test as a workflow
 +
 +[10:28:39] <​aesteve>​ like : when: "I send a request to the server"​ then "the response body should be {...}"
 +
 +[10:30:27] <​temporalfox>​ sounds like BDD stuff
 +
 +[10:30:32] <​temporalfox>​ Spock
 +
 +[10:30:37] <​aesteve>​ actually yes
 +
 +[10:30:43] <​temporalfox>​ I think now Spock has async capabilities
 +
 +[10:30:51] <​aesteve>​ this also works with eventbus, ...
 +
 +[10:31:18] <​temporalfox>​ (someone told me that)
 +
 +[10:31:28] <​aesteve>​ I was wondering how hard it'd be to integrate that to vertx-unit
 +
 +[10:31:57] <​aesteve>​ would it be as easy as extending VertxUnitRunner ? or maybe way more complex
 +
 +[10:32:28] <​temporalfox>​ http://​spockframework.github.io/​spock/​javadoc/​1.0/​spock/​util/​concurrent/​AsyncConditions.html
 +
 +[10:33:32] <​aesteve>​ conds.evaluate {
 +
 +[10:33:32] <​aesteve> ​     assert result == WorkResult.OK
 +
 +[10:33:32] <​aesteve> ​     // could add more explicit conditions here
 +
 +[10:33:32] <​aesteve> ​   }
 +
 +[10:33:37] <​aesteve>​ that's kinda meh
 +
 +[10:34:37] <​aesteve>​ I'll create a gist for what I have in mind
 +
 +[10:35:08] <​temporalfox>​ yep
 +
 +[10:35:09] <​temporalfox>​ good idea
 +
 +[10:39:03] <​aesteve>​ https://​gist.github.com/​aesteve/​cabe8123023fa66b119e
 +
 +[10:41:36] <​temporalfox>​ I think you should start only with when/then
 +
 +[10:41:40] <​temporalfox>​ and leave setup aside
 +
 +[10:46:24] <​aesteve>​ sounds reasonnable :)
 +
 +[10:47:37] <​aesteve>​ in your opinion what should be the entry point, rewriting a junit runner ?
 +
 +[11:02:11] <​aesteve>​ mmh, maybe it's as simple as overriding https://​github.com/​vert-x3/​vertx-unit/​blob/​master/​src/​main/​java/​io/​vertx/​ext/​unit/​junit/​VertxUnitRunner.java#​L87 actually
 +
 +[11:35:45] *** ChanServ sets mode: +o temporalfox
 +
 +[12:41:47] *** ChanServ sets mode: +o temporalfox
 +
 +[13:33:54] *** ChanServ sets mode: +o temporalfox
 +
 +[14:40:25] *** ChanServ sets mode: +o temporalfox
 +
 +[14:52:17] *** ChanServ sets mode: +o temporalfox