"Use contexts"

[glaucocustodio]

What are your thoughts on https://evenbetterspecs.github.io/#use-contexts?

[asavageiv]

I used to do this a lot but now less because it makes things less searchable. When I'm copying from a test string like "UsersController create when there is no password returns an error" I have to be very careful about what I copy to find and search the test. The more contexts the harder it is.

[glaucocustodio]

how do you test many use cases then?

[asavageiv]

I have a top level describe for the class, a describe for the method, and then I have `it` statements within that spelling out each case in readable English. It works well with avoiding before and let too

…

On Tue, Aug 13, 2024, 12:55 PM Glauco Custodio ***@***.***> wrote: how do you test many use cases then? — Reply to this email directly, view it on GitHub <#3 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXDJ3OWMTARSN4ULZ4VGZTZRJQDNAVCNFSM6AAAAABMKT4DV2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZSHE4TKMI> . You are receiving this because you commented.Message ID: <evenbetterspecs/evenbetterspecs.github. ***@***.***>

[glaucocustodio]

that's an option too, but we find using context more handy

[d4be4st]

The main issue with using context is that when you have multiple it blocks and you context description exits the screen. When a test fails, and you enter the file you do not have all the information.
Especially if you allow multiple nested contexts.