Closed karthiknadig closed 6 years ago
How did this trigger? Did you try to run the tests without the testing being configured yet? Did you set the configuration and then write the test file?
I wrote the test file first. then tried to run it. It would bring up this UI:
After finishing the configuration the test tests not detected UI would show up. One thing that i changed is the pattern for test file name from *_test.py
to *_tests.py
.
OK, now I get what's going on. You're getting the notification initially because we can't find any tests until you updated your settings.json
, but we didn't cancel the notification after your update and us noticing that we could now find tests.
@karthiknadig so @qubitron and I are disagreeing on what you mean. 😄 Did you mean that the notification popped up a second time after making the configuration change, or did you leave the notification up while editing your settings and you wanted it automatically dismissed for you?
The pop-up reappeared after dismissing.
@karthiknadig Are you still able to replicate this issue?
I don't see the pop up constantly showing up. But test detection is incorrect. It ran 6 test cases, detected only 3:
OK, so the old issue seems solved, so I'm closing this one. @karthiknadig can you open a new one for the checkbox issue?
Actual behavior
Expected behavior
Pop-up should not show up.
Steps to reproduce:
scratch3.py
:scratch3_tests.py
:class MyTest(unittest.TestCase): def test_0(self): self.assertEqual(1, F(0))
if name == 'main': unittest.main()
start scratch3_tests.MyTest.test_0 scratch3_tests.MyTest.test_1 scratch3_tests.MyTest.test_100 scratch3_tests.MyTest.test_2 scratch3_tests.MyTest.test_neg1 test_0 (scratch3_tests.MyTest) ... ok test_1 (scratch3_tests.MyTest) ... ok test_100 (scratch3_tests.MyTest) ... ok test_2 (scratch3_tests.MyTest) ... ok test_neg1 (scratch3_tests.MyTest) ... ok
Ran 5 tests in 0.001s
OK