Testing - Changing from 3.* python to 2.7

[karthiknadig]

Refs: #16962

• macOS @jrieken
• linux @connor4312
• macOS @chrisdias (Optional)
• windows @rzhao271

Complexity: 3

Create Issue

---

Requirements

1. You will need two versions of python for this 3.* and 2.7.
   1. You can either install from python.org
      OR
   2. You can use pyenv mac/linux or pyenv-win windows. Then use pyenv install 3.9.4 2.7.18 to get the two verisons.
2. Install python extension from here: https://pvsc.blob.core.windows.net/extension-builds/ms-python-insiders.vsix
3. Make sure you have "python.experiments.optInto": ["All"], in your user settings. If you did not have it, add it and reload.

Testing

1. Open an empty folder in VS Code.
2. Add following code to a file named test_example.py:

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!")

3. Start with python version 3.*.
4. You can either configure tests using Python: configure tests... command from the command pallet, or go the test view and configure by using the welcome view, or you can run tests to get a prompt to configure.
5. Select unittest framework.
6. You should see the tests in the test view. Run the tests.
7. Now change python version to python 2.7, it should automatically refresh and allow you to run tests with python 2.7

[jrieken]

Kind of blocked because test discovery doesn't work for me

[karthiknadig]

@jrieken Can you elaborate on where you are stuck?

If you have the test file in the root of the project then your settings should look like this:

{
    "python.testing.unittestArgs": [
        "-v",
        "-s",
        ".",
        "-p",
        "*test*.py"
    ],
    "python.testing.pytestEnabled": false,
    "python.testing.unittestEnabled": true
}

If your test file is in a sub-directory (say mytests) then it should look like this:

{
    "python.testing.unittestArgs": [
        "-v",
        "-s",
        "./mytests",
        "-p",
        "test_*.py"
    ],
    "python.testing.pytestEnabled": false,
    "python.testing.unittestEnabled": true
}

Can you share how the settings looks like?

[jrieken]

This issue #17092. Please update the test item so that this can be tested without python skills

[brettcannon]

@jrieken is it just the file name issue? The instructions originally had a file name suggestion, but I just updated them to flat-out specify a file name. Otherwise is there something else you consider too ambiguous for non-Python users?

[rzhao271]

Specifying the file name to use helped a lot, because

1. I've ran into the issue of accidentally overriding a module before while testing out a Python feature
2. It corresponds to one of the entries in the quick pick while running the configure command.

[jrieken]

Still, not working for me

Screen.Recording.2021-08-25.at.09.59.16.mov

[karthiknadig]

@jrieken You are not using the insider version of the extension. You should see only two options when you configure:

[sandy081]

@chrisdias A friendly reminder to test this Test Plan Item. Since it is optional and if are busy with other stuff please let me know so that I can close this. Thanks.

[chrisdias]

Sorry, I tested this. LGTM, I had similar feedback to @jrieken but it basically worked.