Printing test numbers for describe/it

[AbdealiLoKo]

I am not sure if I have missed a config or so ...
But the current output I get is:

MyFirstDescribeSpec
    ✓ first it() within the describe (735ms)
    ✓ second it() within the describe (321ms)
    ✓ third it() within the describe (287ms)
MySecondDescribeSpec
    ✓ first testcase (735ms)
    ✓ second testcase (321ms)

Is it possible to show which number of the testcase. Something like:

1. MyFirstDescribeSpec
    ✓ 1.1 first it() within the describe (735ms)
    ✓ 1.2 second it() within the describe (321ms)
    ✓ 1.3 third it() within the describe (287ms)
2. MySecondDescribeSpec
    ✓ 2.1 first testcase (735ms)
    ✓ 2.2 second testcase (321ms)

And if there are nested describes, we can just make it 1.1.1 and so on

While I know a progress bar is not feasible because of how karma works. If I know approx that my test suite has 100 describes - this would be very useful for me to know the progress so far.

[devansh7061]

I would like to be assigned this issue as a part of Hacktoberfest 2022

[tmcgee123]

@devansh7061 that's great! All you need to do is create a feature branch or fork.

Once you've developed the feature, you'll need to write unit tests to make sure the coverage doesn't drop and all of the CI passes. Then we can safely merge it and I can publish a new package to npm.

For Hacktoberfest, you can just make a change to the documentation as well and submit a PR. There's not a requirement for level of work. This can be a decent sized feature and take some time depending on how quick you can get a test environment setup.

Let me know if you need help configuring your test environment.

[devansh7061]

Cool will get back to you as soon as I'm done implementing this feature Regards Devansh

…

On Tue, Oct 18, 2022, 10:19 PM Tom M ***@***.***> wrote: @devansh7061 <https://github.com/devansh7061> that's great! All you need to do is create a feature branch or fork. Once you've developed the feature, you'll need to write unit tests to make sure the coverage doesn't drop and all of the CI passes. Then we can safely merge it and I can publish a new package to npm. For Hacktoberfest, you can just make a change to the documentation as well and submit a PR. There's not a requirement for level of work. This can be a decent sized feature and take some time depending on how quick you can get a test environment setup. Let me know if you need help configuring your test environment. — Reply to this email directly, view it on GitHub <#97 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATZZACBRFB7TN5PKBV5X643WD3IIRANCNFSM53GGON2Q> . You are receiving this because you were mentioned.Message ID: ***@***.***>