self passed to class methods in Python 3

The test case provided by @JPFrancoia in issue #20 demonstrates a change in behaviour between Python 2 and 3.

In Python 2, the generated test case is:

import unittest
import upper
from upper import UpperObject

class UpperTest(unittest.TestCase):
    def test_parse(self):
        upperobject_instance = UpperObject()
        self.assertEqual(
            upperobject_instance.parse(to_up='hello world'),
            'HELLO WORLD'
        )

if __name__ == "__main__":
    unittest.main()

While in Python 3, it is generated as:

from typing import Dict
from typing import List
import unittest
import upper
from upper import UpperObject

class UpperTest(unittest.TestCase):
    def test_parse(self):
        self.assertEqual(
            UpperObject.parse(self=<upper.UpperObject object at 0x105b29240>,to_up='hello world'),
            'HELLO WORLD'
        )

if __name__ == "__main__":
    unittest.main()

Notice that self has been passed into UpperObject.parse in the test case generated by Python 3. This should be investigated, as this unit test will not run.

[NextDesign1]

At the moment, you would have to post-process the output so that you instantiate the object first. You could try find & replacing “UpperObject.” with “UpperObject()”, and then “self=<[^>]+>” with nothing.

Another option would be moving the method out of a class. This may or may not be possible with your existing code base. Traditional functions shouldn’t be affected by this bug. See sample/gentests.py and sample/functions.py for an example on how you would set this up.

I’ll take a look at this this afternoon. Hopefully we’ll be able to get this sorted out for you quickly.

[NextDesign1]

Ok, I think I know what the underlying issue is. Python 3 removed unbound methods, which our code was expecting.