Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UnitTests: consider scripts in Custom/scripts/test and allow complete pathes #512

Closed
bschmalhofer opened this issue Oct 3, 2020 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@bschmalhofer
Copy link
Contributor

Currently test scripts in _ Custom/scripts/test_ can override corresponding test scripts in scripts/test . This is useful when a package overrides core functionality. I propose the enhancement that test scripts in Custom/scripts/test are found and executed even when there is no counterpart in scripts/test . This would allow a cleaner separation between addons and core.

@bschmalhofer bschmalhofer added the enhancement New feature or request label Oct 3, 2020
@bschmalhofer bschmalhofer added this to the Wishlist milestone Oct 3, 2020
@bschmalhofer bschmalhofer changed the title UnitTests: consider test scripts in Custom/scripts/test UnitTests: consider scripts in Custom/scripts/test and allow complete pathes Nov 8, 2021
@bschmalhofer
Copy link
Contributor Author

Enhanced the scope of this issue. It would also be nice if regular pathes to script files and directories could be passed. This should also designed to work with command line expansion. It must be decided how to handle the Custom dir in these cases.

Examples:

  • bin/otobo.Console.pl Dev::UnitTest::Run --test Loader
  • bin/otobo.Console.pl Dev::UnitTest::Run --test script/test/Loader.t
  • bin/otobo.Console.pl Dev::UnitTest::Run --directory Selenium
  • bin/otobo.Console.pl Dev::UnitTest::Run --directory scripts/test/Selenium

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant