Skip to content

The failed icon of the first fail test doesn't changed to running icon when using unittest framework in "Test" panel #5791

Closed

Description

@xiaofeng0123

Visual Studio Code - Insiders: 1.35.0-insider
python-insider: 2019.5.16887-rc

Repro step:

  1. Input below code:
import unittest
class PassingTests(unittest.TestCase):
    def test_passing(self):
        self.assertEqual(42, 42)
    def test_passing_still(self):
        self.assertEqual("silly walk", "silly walk")
class FailingTests(unittest.TestCase):
    def test_failure(self):
        self.assertEqual(42, -13)
    def test_failure_still(self):
        self.assertEqual("I'm right!", "no, I am!")
    def test_failure_still1(self):
        self.assertEqual("I'm right!", "no, I am!")
  1. Run tests with unittest framework
  2. Select "Test" in "Side" bar
    4.Click "Run All Tests" button
    5.Click "Run Failed Tests" button

Actual Result:
The failed icon of the first fail test doesn't change
unittest_icon

Expect Result:
All icon of failed tests should change

Activity

  1. ghost removed
    triage-neededNeeds assignment to the proper sub-team
    on May 29, 2019
  2. ericsnowcurrently commented on May 30, 2019

    @ericsnowcurrently

    Hi xiaofeng0123. Thanks for letting us know about this. I was able to reproduce the problem (after adding time.sleep(0.2) to each of the tests). We'll work on getting this fixed.

  3. karthiknadig commented on Jul 30, 2021

    @karthiknadig
    Member

    Kartik Raj (@karrtikr) With the latest UI, it only shows progress if the execution takes long. If you add time.sleep(1) before the asserts you will see that it shows progress for each test case as it is run.

  4. brettcannon commented on Aug 3, 2021

    @brettcannon
    Member

    This has been fixed in the next version of the test UI.

  5. locked as resolved and limited conversation to collaborators on Sep 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-testingbugIssue identified by VS Code Team member as probable bugverifiedVerification succeeded

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions