As per angularsen/UnitsNet#328 (comment)

Having a set of tests to validate that the correct abbreviation notations and symbols are used would be helpful, as we have seen from before that discrepancies tend to creep in over time.

See #328 for the (currently work in progress) guideline, go through the comments and identify what tests to write for the guid

No Unit found is not descriptive at all.

We should at least make that error message more clear for cases like:

• "75kg" instead of "75 kg"

Our assumption for parsing a compound quantity is that there will be a space character between the value and the unit

Describe the bug
As mentioned in #161, for some inputs the output of the disambiguation tool seems nondeterministic. This is undesired behaviour.

To Reproduce
Results for "1mw"

Expected behavior
Always return either "milliwatt" or "megawatt", however not random ones.

Additional information:

• Classifier activated/ sklearn installed: yes

Additional context
As p