bin/otobo.Console.pl Dev::UnitTest::Run should check if package parameter is valid

[stefanhaerter]

Currently, if e.g. a package name is misspelled, e.g. 'faq' instead of 'FAQ', all unit tests are run. I think this is at least inconvenient. Instead, it would be nice if the console command checks if a package parameter is passed and if so, if the package names are valid and aborts otherwise.

[bschmalhofer]

Yes, that is a good enhancement.

[stefanhaerter]

Perhaps Text::Levenshtein could be used to implement a feature like "You typed x, but x is not a valid package name - did you mean y?", but I assume that would be no justification for taking it in as a dependency.

[stefanhaerter]

I just learned that Kernel/System/Package.pm provides a sub which will come in pretty handy here:

otobo/Kernel/System/Package.pm

Lines 2682 to 2691 in 8c70deb

	=head2 PackageIsInstalled()
	returns true if the package is already installed
	$PackageObject->PackageIsInstalled(
	String => $PackageString, # Attribute String or Name is required
	Name => $NameOfThePackage,
	);
	=cut

[stefanhaerter]

As Kernel::System::UnitTest::Run() receives the package names as parameter, I am yet unsure if validation needs to take place in the console command or in the backend method, or in both places. Starting to implement it in the console command seems like a good start.

[bschmalhofer]

Regarding fuzzy matching, I think that autocompletion of the parameter would be more useful than "did you mean".