Tests get different fully-dotted names depending on the discovery-method used.

[cleancut]

Tests get different fully-dotted names depending on the discovery-method used.

[CleanCut]

Here's the loading strategies and what they end up with:

DISCOVER (package name [directory]) - Does not include package name
DISCOVER (package.subpkg [directory]) - Does not include package name
DISCOVER (installed package name [directory]) - Does not include package name

DISCOVER (. outside package [current directory]) - Includes package name
DOTTED OBJECT (package.module [file]) -Includes package name
FILE (module filepath [file]) - Includes package name

[CleanCut]

I altered one of the existing loader unit tests to fail for this condition.

The DOTTED OBJECT strategy won't load a package by name, so I can't just switch to that instead. I'm going to have to read the unittest source and see if there's someway to influence it. If there's not, then I'm just going to have to reimplement discovery myself.

On the bright side, that would enable me to implement more features (like treating bare functions as tests if I want to). On the other hand, it's a lot of functionality to rewrite to fix a small (but important) issue.

[CleanCut]

Okay, this is bugging me. A lot. I have tried to solve this problem three different times in three different ways, and hit a dead end on all of them.

The built-in unittest stuff is a mess. Sorry python, but it's true. I'm going to start an experimental branch to start writing my own test discovery. Maybe along the way I'll discover how to fix it without my own discovery.