Looks like passing tests in official starters could be added to your cicd so you catch the errors earlier 🙂

Didn't check on github if there's already issue for that - there could be

Not qutie sure what is the error you mentioned. maybe a snippet?

return KedroContext(

is missing

env="local",

for example

not sure if this is the only issue, but fixing that got it running - we need to review all other starters

could do PR but I have time for that on friday

actually I maybe can do it now, but I can't figure out why in some projects it has no issue finding the main module to import while being outside

src/

while in others it can't

maybe poetry does some magic behind the scenes

Yes turned out to be poetry

So we have 3 options according to https://docs.pytest.org/en/7.1.x/explanation/goodpractices.html?highlight=src#tests-outside-application-code : • add to documentation instruction to add your package in editable mode

pip install . -e

---> poetry does that for you by default so that's why it was working in my other poetry setup • add instruction that you can run it by going to

src/

and then leveraging

python -m pytest ../tests

(and /or add

tests

to tests path in

pyproject.toml

) • move

tests

dir to

src/tests

- that's what kedro docs page already assumes it to be - see https://docs.kedro.org/en/stable/development/automated_testing.html#run-your-tests So I'd vote for 3rd option, as it requires the least knowledge about

pytest

mechanisms, but improving docs is also a must. What do you think @Nok Lam Chan?

I disgree with 2&3, and thanks for pointing out that documentation, I have no idea why it is written like this. Kedro starters always create tests outside of the

src

because you don't want to ship your test to your user, they don't need this. https://github.com/kedro-org/kedro-starters/tree/main/spaceflights-pandas/%7B%7B%20cookiecutter.repo_name%20%7D%7D

Unless your application code also need to use the test module. Pytest support both https://docs.pytest.org/en/7.1.x/explanation/goodpractices.html#choosing-a-test-layout-import-rules See "tests as part of application code" and "tests outside application code"