Should `kedro test` and `kedro lint` be deprecated?

Investigate what the alternatives would be for users currently using kedro test and kedro lint. Write up a plan to deprecating kedro lint and kedro test (including how the users can “migrate” to these alternatives) or alternatively summarise why those commands shouldn’t be deprecated.

Also keep in mind that the alternatives should still make it possible to have a linted/testable Kedro template.

[jmholzer]

In technical design (14/09/22) it was concluded that both commands should be deprecated. The following action items were agreed:

1 (#1619 and #1620). Short guides for linting and testing should be written and added to the docs. Depending on the traffic metrics for this part of the docs, a next step of creating either a lint / test starter* (see below) or a plugin will be considered. 2 (#1849). Explore whether the /tests folder and / or the linting configuration (requirements, config files) should be kept or dropped in the starters and / or template.

* @yetudada proposed moving the elements needed to add both commands to a starter project. This may provide significant advantages in ease of maintenance relative to the plugin option.

[yetudada]

This write-up and evaluation is stellar 🎉 An additional benefit is a simpler starter for new users.

If I quickly scan the documentation and starters it would mean that we would be making the following changes (if I haven’t forgotten anything):

• Starters:
  • Remove setup.cfg
  • Edit pyproject.toml
  • Edit src/requirements.txt
• Documentation:
  • Edits to anywhere where setup.cfg is mentioned like in the Project directory structure, the section on Astronomer, and the one on Starters
  • Add new sections on testing and linting, probably under Development or Tools integration

I like the documentation addition because in future, the section on testing could be expanded to cover #1271. I think @deepyaman’s comment is the only thing left to cover, which is how do we make sure that we deliver linted and tested starters to our users without those configuration files being present in the starters.