proposal: adding stubs

[erickzanardo]

Hey,

I have a proposal that was originally sent on the mocktail repo, but after some discussion we decided that it would be better fitted on an external package.

Would this be something that you would be open to be added to this package?

If so I would love to work on a PR adding it.

[shinayser]

OLHA O ERICK AÍ, hahaha!!! E aí mano, beleza? Quanto tempo! 😊

Hey Erick! Correct me if I am wrong: you are propossing to add some classes that provide default implementations, right? Or you want to add some high-order objects (maybe const?) that already provide the implementations for us?

[erickzanardo]

Opa beleza e por ai? :D

The idea is to add some default Stub classes, which are simple mocks that allows us easily check if callbacks were called. In this collection we would have some common cases like VoidStub, StringStub, IntStub, etc.

That way if someone wants to test if a GestureDetector worked for example, they could do something like this:

final stub = VoidStub();
await tester.pumpWidget(GestureDetector(onPressed: stub.onCall, child: Text('tap me'));
await tester.tap(find.text('tap me'));

verify(stub.onCall).called(1);

[shinayser]

Sounds really cool to me! But I wonder if we can go further and also provide some default implementations with some high order const variables, like:

const kVoidStub = VoidStub();
const kStringStub = StringSubt();
const kIntStub = IntStub();

Does it make sense?

[erickzanardo]

Mock doesn't have a const constructor iirc. But even if it does I don't believe that could be add much value, if we provide default instances, then that instance would be "dirty" among tests, for mocks it is better that the user create an instance per test and I don't think we should influence the user on the other direction, wdyt?

[shinayser]

Oh I see. Anyway, feel free to open the PR and I will be glad to approve it :)