Best way to capture tests for regressions about gopter HOT 6 CLOSED

I'd say that the interface of the "commands" tests could certainly have some improvements.

The there are two core functions that (unluckily) are not public:

Especially the latter should contain everything to create a regression test from a given sequence of commands.
Would it be helpful to make this a public function?
Or maybe all you need is just to make the "action" struct public.

from gopter.

Thanks for the quick response!

I think the actions is pretty close to the process I'm trying to hook into. Although, it would probably be best to just expose a simple method like the following:

func Replay(commands.State,
          commands.SystemUnderTest,
          ...commands.Command) *gopter.PropResult {...}

All that's really necessary is a nice wrapper around the lifecycle of how commands are applied. Think of it like this -- I'm looking for something almost identical to a normal Gopter test, but I want to be able to specify precisely the commands that are generated and I only want to run 1 test case.

from gopter.

Sorry, I was really busy last week and overlooked this.
I created a "devel" branch containing a "command.Replay" function that probably fits your needs (https://github.com/leanovate/gopter/blob/devel/commands/replay.go).
If that is working for you I'll merge it to master

from gopter.

I think what you have there is a working solution, and is very close to what I've been doing myself to solve this problem. I'd be much happier to lean on this feature from the library than my own codebase.

One improvement I could see is a tighter coupling to the workflow run by commands.Prop so that the two cannot diverge in the future. As a consequence of the loose coupling of your current implementation, I don't think shrinking will be applied to regression tests. That's not a major problem, but I'd think it's sub-optimal to not apply shrinking.

I'm also beginning to familiarize myself more with the codebase, and would be happy to start making some contributions of my own on this front soon.

from gopter.

Yes, I see your point.
I did a bit of refactoring. Can you give https://github.com/leanovate/gopter/blob/devel/commands/replay.go
a try.

And yes, for a regression test a shrinker would actually be counter-productive. Its main purpose is trying to find the minimal sequence of commands to fail the system

from gopter.

I merged this version and will close this issue for now.

from gopter.