As well as the __init__.py file that enables the module, and a reference to the module in an existing CI scripts.
From what I can tell, there are no references to these feature definitions, and they match the equivalent features that live within tests/functional/behave_features. I believe the behave_features directory was a migration destination from an original pytestbdd-driven approach. All references that I can find to the tests/ directory refer directly to the tests/functional/behave_features directory, and so I've concluded that these tests are duplicates.
Here are the locations I see that refer to the tests/functional directory. All locations reference the behave_features specifically.
This PR removes the following directories:
As well as the
__init__.py
file that enables the module, and a reference to the module in an existing CI scripts.From what I can tell, there are no references to these feature definitions, and they match the equivalent features that live within tests/functional/behave_features. I believe the behave_features directory was a migration destination from an original pytestbdd-driven approach. All references that I can find to the tests/ directory refer directly to the tests/functional/behave_features directory, and so I've concluded that these tests are duplicates.
Here are the locations I see that refer to the tests/functional directory. All locations reference the behave_features specifically.
Please comb through this and make sure I've not inadvertently missed some reference to these files that would motivate us to leave them in place.