Not displaying full status when running large amount of tests

[paulacamargo25]

Testing #21306

Running this tests

First run the test with 100, and everything seems to work, then update the range to 100000. The tests start to run, the wheel appears in the previous 100, when the test ends I see that the previous 100 appear as complete, but the new ones appear as if they were never run.

[eleanorjboyd]

Hi! When you switched to 10,000 did you reload the test UI?

[paulacamargo25]

No, i only run the tests again

[eleanorjboyd]

I am still not able to repro this, these are the steps I followed. Could you provide steps or a video?

1. Open inc_dec_example_repo
2. discover tests with pytest
3. change from @pytest.mark.parametrize("num", range(1, 10)) to @pytest.mark.parametrize("num", range(1, 100))
4. do not click save instead just click the "run" button in the test explorer UI (double arrow at the top to run all tests)
5. I also tried using the gutter with the parameterize test to run it which also did not work in repro the bug
6. I see all the 100 tests with the green checkmark

[eleanorjboyd]

@paulacamargo25 to follow up, do you still experience this issue?

[paulacamargo25]

What i did extra is that i run the first tests. yes sure, im going to try again

[eleanorjboyd]

so like:

1. Open inc_dec_example_repo
2. discover tests with pytest
3. run pytest
4. change from @pytest.mark.parametrize("num", range(1, 10)) to @pytest.mark.parametrize("num", range(1, 100))
5. do not click save instead just click the "run" button in the test explorer UI (double arrow at the top to run all tests)
6. I also tried using the gutter with the parameterize test to run it which also did not work in repro the bug
7. I see all the 100 tests with the green checkmark

I tried these steps and still got it working as expected.

[paulacamargo25]

I was able to reproduce the issue, the problem occurs when you save the file and immediately run the tests afterwards.

Screen.Recording.2023-06-05.at.4.47.02.PM.mov

[eleanorjboyd]

Ok sweet I was able to repro the issue. this seems to be the fix so we can test when this is merged to make sure. Thanks!