tests folder (automated tests??)

[FAReTek1]

@TheCommCraft What is the tests folder for? I assume it is for automated tests? Is there a specific format for these tests? I see a single file test_import.py, which does not do anything when run

I am asking this because I wanted to make some scripts for automated testing

Also, is there a way to add environment variables when running a github action? What I mean is that some automated tests would involve authentication, so that e.g. commenting can be tested - but this requires either a password, session id, or session string. Is there a way to add this to the repository (store on github) - but not make it public?

[FAReTek1]

would something like this be a good idea?

import os
import warnings

import scratchattach as sa

warnings.filterwarnings("ignore", category=sa.LoginDataWarning)

password = os.environ["SCRATCHATTACH-TEST-PW"]

sess = sa.login("scratchattach-tests", password)

assert sess.id is not None
assert sess.username == "scratchattach-tests"
assert sess.xtoken is not None
assert sess.connect_linked_user().id == "157124692" # should user ids be ints?

[TheCommCraft]

id say yes

[TheCommCraft]

But Tim would need to add it as a secret i think

[TheCommCraft]

The test_import function is automatically run by pytest before the workflow deploys a new version of scratchattach. Any functions starting with "test" in the tests folder will have this behaviour.

[FAReTek1]

is it possible to make it also run when making a pr?

[TheCommCraft]

Yes, but I am not sure how