{"action":"created","issue":{"url":"https://api.github.com/repos/czan/stateful-check/issues/8","repository_url":"https://api.github.com/repos/czan/stateful-check","labels_url":"https://api.github.com/repos/czan/stateful-check/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/czan/stateful-check/issues/8/comments","events_url":"https://api.github.com/repos/czan/stateful-check/issues/8/events","html_url":"https://github.com/czan/stateful-check/issues/8","id":330841422,"node_id":"MDU6SXNzdWUzMzA4NDE0MjI=","number":8,"title":"Print out failing seed?","user":{"login":"bhb","id":33398,"node_id":"MDQ6VXNlcjMzMzk4","avatar_url":"https://avatars0.githubusercontent.com/u/33398?v=4","gravatar_id":"","url":"https://api.github.com/users/bhb","html_url":"https://github.com/bhb","followers_url":"https://api.github.com/users/bhb/followers","following_url":"https://api.github.com/users/bhb/following{/other_user}","gists_url":"https://api.github.com/users/bhb/gists{/gist_id}","starred_url":"https://api.github.com/users/bhb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bhb/subscriptions","organizations_url":"https://api.github.com/users/bhb/orgs","repos_url":"https://api.github.com/users/bhb/repos","events_url":"https://api.github.com/users/bhb/events{/privacy}","received_events_url":"https://api.github.com/users/bhb/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-06-09T01:24:45Z","updated_at":"2018-06-12T02:39:19Z","closed_at":null,"author_association":"NONE","body":"Thanks a lot for your work on this library, it's very useful. \r\n\r\nOne thing I noticed is that when a test fails, the seed doesn't appear to be printed, so if I want to reproduce the test run (after, say, applying a fix for the bug), my only choice is to run a large number of tests and hope the same sequence is generated.\r\n\r\nIs there a way to do this?"},"comment":{"url":"https://api.github.com/repos/czan/stateful-check/issues/comments/396447286","html_url":"https://github.com/czan/stateful-check/issues/8#issuecomment-396447286","issue_url":"https://api.github.com/repos/czan/stateful-check/issues/8","id":396447286,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NjQ0NzI4Ng==","user":{"login":"czan","id":1835975,"node_id":"MDQ6VXNlcjE4MzU5NzU=","avatar_url":"https://avatars1.githubusercontent.com/u/1835975?v=4","gravatar_id":"","url":"https://api.github.com/users/czan","html_url":"https://github.com/czan","followers_url":"https://api.github.com/users/czan/followers","following_url":"https://api.github.com/users/czan/following{/other_user}","gists_url":"https://api.github.com/users/czan/gists{/gist_id}","starred_url":"https://api.github.com/users/czan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/czan/subscriptions","organizations_url":"https://api.github.com/users/czan/orgs","repos_url":"https://api.github.com/users/czan/repos","events_url":"https://api.github.com/users/czan/events{/privacy}","received_events_url":"https://api.github.com/users/czan/received_events","type":"User","site_admin":false},"created_at":"2018-06-12T02:39:19Z","updated_at":"2018-06-12T02:39:19Z","author_association":"OWNER","body":"> Overall, I agree using a seed has limitations, but it seems somewhat confusing to me that `specification-correct?` takes this param at all. I'm not sure what the use case is for this param. Can you speak more about this?\r\n\r\nHonestly, it's only there because `quick-check` takes a seed as an argument, and I never thought to remove it. I've been thinking about this over the past few days, and I have some thoughts. Unfortunately, when I started typing them out I found that I couldn't even convince myself that they were the best solution.\r\n\r\nI'm going to think about this a bit more, to see if I can think of a way to solve this that also nicely solves the use-cases you mentioned. I think there is potential for mistakes if I provide the seed, but I don't want to have to engineer a more complex solution for your use-cases just to avoid printing the seed. I'd much rather document it as a pitfall, and assume that developers are competent.\r\n\r\nMy two ideas were:\r\n1. To have a function to \"re-run the last test case\".\r\n2. To have an option to generate the test trace as Clojure code, to easily turn it into an example-based test. This would only work if `:command` keys are specified as vars, or something. I haven't worked through all the details.\r\n\r\nIt's probably better to just print the seed, though."}}
{"actor":{"display_login":"czan"}}