<div dir="ltr">Cool, thanks!<br><br><div class="gmail_quote"><div dir="ltr">On Thu, Sep 22, 2016 at 1:28 PM James Aimonetti <<a href="mailto:james@2600hz.com">james@2600hz.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA256<br>
<br>
<br>
You should check out Thomas Arts' talk from this past Erlang Factory:<br>
<br>
<a href="https://www.youtube.com/watch?v=iW2J7Of8jsE" rel="noreferrer" target="_blank">https://www.youtube.com/watch?v=iW2J7Of8jsE</a><br>
<br>
The ideas should be generally applicable.<br>
<br>
Andrew Berman writes:<br>
<br>
> Hey Pierre,<br>
><br>
> How do you QuickCheck RESTful APIs? I'm a noobie with QuickCheck and using<br>
> it with RESTful APIs would be really useful to me. Do you have any sample<br>
> code or is there a tutorial anywhere?<br>
><br>
> Thanks!<br>
><br>
> On Wed, Sep 21, 2016 at 10:58 PM Pierre Fenoll <<a href="mailto:pierrefenoll@gmail.com" target="_blank">pierrefenoll@gmail.com</a>><br>
> wrote:<br>
><br>
>> Have you tried using PropEr / Quickcheck statem?<br>
>> <a href="http://proper.softlab.ntua.gr/Tutorials/PropEr_testing_of_finite_state_machines.html" rel="noreferrer" target="_blank">http://proper.softlab.ntua.gr/Tutorials/PropEr_testing_of_finite_state_machines.html</a><br>
>> PropEr is free & open source & I use it to quickcheck RESTfull APIs.<br>
>><br>
>><br>
>><br>
>> Cheers,<br>
>> --<br>
>> Pierre Fenoll<br>
>><br>
>> On 22 September 2016 at 05:45, Josh Adams <<a href="mailto:josh.rubyist@gmail.com" target="_blank">josh.rubyist@gmail.com</a>> wrote:<br>
>><br>
>>> So I've been frustrated lately by the fact that Slack's IRC gateway isn't<br>
>>> RFC 2812 compliant (<a href="https://github.com/bitwalker/exirc/issues/51" rel="noreferrer" target="_blank">https://github.com/bitwalker/exirc/issues/51</a>)<br>
>>><br>
>>> In dealing with this I wondered why the crap they needed an engineer to<br>
>>> go through the spec as a result of their server's response to figure out<br>
>>> that this was an issue (they've added it to their bug tracker, so I have<br>
>>> some amount of faith it might get fixed eventually - for now I'll paper<br>
>>> over the issue in the client which reduces the stress on them to actually<br>
>>> fix it though).<br>
>>><br>
>>> Should RFCs / protocols of this nature just come with something like a<br>
>>> quickcheck model for their spec? Is anyone aware of prior art around this<br>
>>> sort of thing aside from Quvic/Volvo that I could draw from if I wanted to<br>
>>> fiddle in this arena?<br>
>>><br>
>>> I'd think that the ideal situation involves an open source quickcheck<br>
>>> implementation to test a given protocol implementation against at least<br>
>>> some of the RFC, and a means to run the tests against potential<br>
>>> servers/clients, with badges potentially showing the percentage of the test<br>
>>> that passes. This would allow economics to drive spec implementers towards<br>
>>> correctness, which would save countless engineer-hours spent figuring out<br>
>>> why the damn clients can't talk to the damn servers for a given spec.<br>
>>><br>
>>> Thoughts? Pipe dream? "Silly child, see A, B, and C for the many people<br>
>>> who are already doing this?"<br>
>>><br>
>>> --<br>
>>> Josh Adams<br>
>>><br>
>>> _______________________________________________<br>
>>> erlang-questions mailing list<br>
>>> <a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
>>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
>>><br>
>>><br>
>> _______________________________________________<br>
>> erlang-questions mailing list<br>
>> <a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
>> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
>><br>
> _______________________________________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br>
<br>
- --<br>
James Aimonetti<br>
<br>
Lead Systems Architect<br>
"If Dialyzer don't care, I don't care"<br>
2600HzPDX | <a href="http://2600hz.com" rel="noreferrer" target="_blank">http://2600hz.com</a><br>
<a href="mailto:sip%3Ajames@2600hz.com" target="_blank">sip:james@2600hz.com</a><br>
tel:415.886.7905<br>
irc:mc_ @ freenode<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2<br>
<br>
iQEcBAEBCAAGBQJX5D73AAoJENTKa+JPXCVg8SwH/jTe/EhqLBQc1b82rptahsuy<br>
SL2dwQjzq6kxfzJquVE05t4yjjhI3GKaHoaeGkPMNF4Wq4Y9ZdWVOrIfyE1fHuxg<br>
EltLgUq6OAjQeCYkQXNOTtcWzt6AJ8ZpKK9z9U7hydJL9NAs1IF6v2D/NjbvJ02H<br>
OAlRLZzhqcN1nm+/yOPPqs9zBac5SR3YHK3bo8A5vlx5M+8jrI3SV6fe5cBXTbIF<br>
CzVKmrlD3EZlGEYaDN1ssFDShv42CZJk4+2bvQnsJDJ4YRe7WqoDOJIhgcg92Tuo<br>
ntiYR8nlMY+qzDWYjOZnpVNNUN5oudLUjmhCuLU5vGwkLB74Y+2YBwxbC7gabec=<br>
=KvP6<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div></div>