Randy Lai

I see what's going on now. You were trying to use relative import `from .utilities import BasicSublimeTextViewTestCase`. However, the tests was not imported as module so relative import is not...

Unittesting only imports directories under tests as modules, so you have to put it under `/tests/testsomrthingelse/`. In fact, the top level `__init__.py` is never used.

I may look into the possibility to import `tests` as a module. Edit: it seems that it requires quite some work based on the `unittest`’s `discover` function. I don’t expect...

I am not sure how easy or how hard it would be done. It seems that `unittest.discover` doesn't try to import the starting directory as a module.

If we specify `start_dir = 'PATH TO PACKAGE'` rather than `start_dir = 'PATH TO PACKAGE/tests'`, it should theoretically import `tests` module as a package if a `__init__.py` is found. But...

It would work only if there is a `__init__.py` under `tests` so it will break a lot of current users of UnitTesting.

Hopefully the [next update](https://github.com/SublimeText/UnitTesting/blob/master/unittesting/package.py#L74-L77) will handle it.

There are two issues needed to be solved. St4 requires a key, 2 package control does not support st4 (python 3.8) at this moment.

The latest version of Package Control still doesn't support Python 3.8 packages as far as I can tell.

It works because your package doesn't have any dependencies. Your package will probably fail if it specifies any dependencies.