Proposal: Test classes (callable class)

[matiechaza]

I was thinking it would be great if we could pass a callable class as the second argument.
In this way the entire test would be encapsulated within classes.

I think it would be great feature! Since the tests would be very clean and we could apply design patterns for the different test classes.

For example. Given the next test:

The following test class can be written:

You could even force these "test classes" to have the given-when-then methods to be printed on the report and not need a description in the test() and it() functions 😍.

[nunomaduro]

Sounds good to me. Can you make a pull request on this?

[owenvoke]

I guess this would involve changing the it() and test() signatures to use callable instead of Closure? 🤔 And then in turn the TestCall, TestCaseFactory, and a few other places. Not sure how much work would be needed, but this would be a really neat feature to have. 👍

[nunomaduro]

@owenvoke Exactly. Same goes for beforeEach, etc.

I think it may be interesting to have something like:

beforeAll(Browser::start());

[matiechaza]

I don't have much time to dedicate to it. But I'm going to try 😃

[matiechaza]

I didn't think about changing the signatures of it() and test().
I think it would be better to create a new function for this feature. This way I wouldn't add one more use case to the it() and test() functions.

Perhaps this new function will organize the data to use the test() function (as the it() currently does).

What do you think?

[nunomaduro]

Why a new functions? I think is fine to it and test to support callables.

[matiechaza]

Because in this new function I could modify the receive class by a class of callable type and send it to the test () function. This way I would not break the signature.

It was my first quick thought I had.

[nunomaduro]

Yeah - I think its fine.

[nunomaduro]

Fell free to make a pull request on this.