run specific tests from cli

[tadly]

With unittest it is possible to run specific tests from the cli.
When using ddt this doesn't seem to be possible.

Example:

import unittest
from ddt import data, ddt


class Test(unittest.TestCase):
    def test(self):
        self.assertEqual(1, 1)

@ddt
class TestDDT(unittest.TestCase):
    @data('arg1', 'arg2')
    def test(self, arg='arg1'):
        self.assertEqual(1, 1)

if __name__ == '__main__':
    unittest.main(exit=False)

Running specific unittest:

$  python test.py Test.test
.
----------------------------------------------------------------------
Ran 1 test in 0.000s

OK

Running specific unittest with ddt:

$ python test.py TestDDT.test
E
======================================================================
ERROR: test (unittest.loader._FailedTest)
----------------------------------------------------------------------
AttributeError: type object 'TestDDT' has no attribute 'test'

----------------------------------------------------------------------
Ran 1 test in 0.000s

FAILED (errors=1)

[Arrowana]

Yes, you can.

For instance:

import unittest

from ddt import ddt, data

@ddt
class ThingTest(unittest.TestCase):

	@data(3, 4, 5)
	def test_equal(self, n):
		self.assertEqual(4, n)

When running discovery you get the following test methods:
test_stuff.ThingTest.test_equal_1_3
test_stuff.ThingTest.test_equal_2_4
test_stuff.ThingTest.test_equal_3_5

To run one:
python -m unittest test_stuff.ThingTest.test_equal_2_4

However, I don't know why your command syntax does not work

[wswld]

I can confirm the syntax suggested by @tadly is not supported at the moment, the right way to use it is like shown by @Arrowana. It's a bummer since discovering tests by substring would be most beneficial.

If anyone has a vision how this could be implemented, a pull request is welcome. I will probably investigate it at some point but for now there are more pressing issues with this package.

[tadly]

Just wanted to say that I myself have migrated to pytest so I won't be spending much time on this issue.
But good to see that it has been acknowledged :)

[avkoval]

When running discovery

How to run 'discovery'? I can't find the option into nose how to do that, without it the method names are hidden :-(

[avkoval]

I found one workaround: if I comment out docstring of the test function, I can see the function name: that is the only way I found to discover that - anything else (-v 3, etc) does no help

[wswld]

Greetings. By default it uses the docstring if provided. What are you trying to achieve? We can think of a possible solution together.

…

On 22 May 2019, 23:08 +0300, avkoval ***@***.***>, wrote: I found one workaround: if I comment out docstring of the test function, I can see the function name: that is the only way I found to discover that - anything else (-v 3, etc) does no help — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.