Fix filtering test specs by part of their name using CLI --spec arg

[tech-dm-klymenko]

Proposed changes

Issue: #9495
A bugfix for this functionality has been released:

If the --spec value does not point to a particular spec file, it is instead used to filter the spec filenames defined in your configuration.

To run all specs with the word “dialog” in the spec file names, you could use:

wdio wdio.conf.js --spec dialog

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• I have added proper type definitions for new commands (if appropriate)

Further comments

Reviewers: @webdriverio/project-committers

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: tech-dm-klymenko (e669573, 28c7f92, b97986e, d2dbbd7, 4b23b59, 7656e08, 7de2980, 1542ec8, d2026d3, b1c70ec, 3bad262, 27a5f27, 60ba4c6, 7190311, 24b899b, d86cda0, 46e6634, db459ca, a79953a, 9e894db, 1c691da, ff9bfe3, 6dee29c)
• ✅ login: christian-bromann / name: Christian Bromann (51ab2f6)

[erwinheitzman]

Thank you for the contribution, awesome work!

Could you add some tests to verify the behavior? 👍

[christian-bromann]

Thanks for taking a stab at it. I made some comments to hopefully simplify the code. Let me know if you have any questions.

[tech-dm-klymenko]

@christian-bromann @erwinheitzman

Thank you for your comments!

Upon further consideration, I revisited the current approach and made adjustments. From my analysis, the main issues stemmed from two points:

1. The setFilePathToFilterOptions method consistently used a glob pattern search. While effective when specifying the spec path to the --spec, it failed when we pass a keyword as --spec argument.

2. During the initialization stage of the ConfigParser object, the merge method was invoked within its constructor. This, in turn, attempted to obtain paths to the specs through the setFilePathToFilterOptions method. However, at this stage, we lacked a list of specs from the config file, leading to an error.

I fixed issues above and now the --spec option works correctly. I have also included smoke tests to verify this functionality.

Please check my PR one more time

[erwinheitzman]

Added some feedback

[tech-dm-klymenko]

@christian-bromann @erwinheitzman
I made changes according to your comments

[christian-bromann]

@tech-dm-klymenko thanks! It seems that there are some issues in CI 🤔

[tech-dm-klymenko]

@christian-bromann
Could you, please, tell me, do you have any other comments regarding the fix without taking into account the tests? Probably I’ll just add the tests as the separate PR later. And current implementation of tests will be reverted to avoid issues in CI

[christian-bromann]

I think it makes sense to fix the test, it seems like we are very close

[christian-bromann]

I think there is another issue at hand here which is outside of the scope of your PR, I made a suggestion how to work around it.

[christian-bromann]

Awesome, thanks a lot! 👍

[christian-bromann]

Fantastic first contribution 🎉

[tech-dm-klymenko]

Thank you very much for your appreciation! 😊